Six record types that link to each other, a matcher that reads all of them, and an MCP endpoint agents can call. This page says when each part went live, so the claim can be checked.
By Damien, Founder and editor
Last updated 11 October 2026
A record on HokAI is one of six things: a tool, an agent, a skill, a model, a company or a service. They are not six lists. An agent record names the models it runs on and the skills it plugs into. A skill record, which is where MCP servers and connectors live, names the agents that can call it. A model record names its maker, and the company record lists everything that maker ships. A guide links the records it discusses, and each record lists the guides that discuss it.
That is what lets a reader move from a question to a decision without leaving the evidence behind: from the guide to the record, from the record to the company, from the company to the model, and from any of them to the alternatives.
Smart Match is the product. You describe your work, it asks a few short questions, and it returns up to three picks with the reason each one is on the list. It reasons over every active record of every type, so a skill or a model can be the right answer when a visitor arrived thinking they needed a tool. No vendor can pay to appear in the picks or to move up in them.
The directory is also available to agents directly. The HokAI MCP server at hokai.io/mcp has been live since July 2026 and has been listed in the official Model Context Protocol registry as io.hokai/hokai since 29 July 2026. An agent that speaks MCP can search the directory and read a record the same way a reader does, which is how the graph above ends up inside other people’s assistants. Our record of what MCP is and how to connect one is in the docs.
Dates are the month each section first served pages on hokai.io. The MCP Registry date is the day the listing was verified. Nothing here is a plan: a line is added when the thing is live.
A record carries one visible checked date, and it moves only when a person or a source-checking routine has compared the record to the vendor’s own pages. A rewrite for clarity does not move it. Each record also shows its last dated changes, and the weekly page collects every dated change across the directory: releases, pricing moves, new features and deprecations, each with its source.