HokAI
REMOTE · HOKAI.IO
AI tool directory MCP server, live since July 2026. Tools, agents, models, companies, services.
Available components
Last scanned (21 hours ago)
Scores higher than 61% of remote servers
Reachable. Last reached 21 Nov 2026.
Category AI and Machine Learning
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability66
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1313 tokens (~145/item across 9 items; 9 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage67
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 0% of tool parameters carry a description.Fail
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 9 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Checks we ran (12)
- TLS certificate
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 16 Nov 26 0
- Tool “buy_guide_spot” rewrote its description, which is the text the model reads security
- Tool “vendor_catalog” rewrote its description, which is the text the model reads security
- 11 Nov 26 −1
- Stability: 0.97 → pass security
- Tool “get_listing_info” rewrote its description, which is the text the model reads security
- Tool “submit_listing” rewrote its description, which is the text the model reads security
- Schema quality: pass → fail ▼ functional
- New tool “buy_guide_spot” functional
- New tool “buy_leads” functional
- New tool “buy_listing” functional
- New tool “order_status” functional
- New tool “vendor_catalog” functional
- 10 Nov 26 0
- Stability: pass → 0.97 functional
- 9 Nov 26 0
- Stability: 0.97 → pass security
- 8 Nov 26 0
- Stability: pass → 0.97 functional
- 6 Nov 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 3 Nov 26 0
- Tool “get_listing_info” rewrote its description, which is the text the model reads security
- Tool “submit_listing” rewrote its description, which is the text the model reads security
- 2 Nov 26 0
- Server version: 1.27.1 → 1.0.1 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Nov 2026 · Probed https://hokai.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=hokai.io | CN=YE2,O=Let's Encrypt,C=US | 4 Nov 2026 | 2 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6c7a12d61d85440e70882950970ae4e1806 |
| SANs: hokai.io, www.hokai.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of hokai.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| io. | DS published | 38690 | 8 | Verified |
| hokai.io. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://hokai.io/mcp | Verified | 200 | |
| http (plaintext) | http://hokai.io/mcp | HTTPS enforced | 301 | https://hokai.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
buy_guide_spot ~439
Buy a labelled Sponsored spot for a product in one Hokai guide. Returns checkout_url, a Stripe card payment page. The dates are held for 30 minutes while it is open; the first payment wins. Rule to pass on to the vendor: guide spots are pay first. The entry is written by hand and goes live within 48 hours of payment, or on the start date if that is later. If the guide does not suit the product, Hokai moves the spot to a guide that does. Refunds are not automatic: ask damien@hokai.io. Give the product EITHER as product_slug (+ product_type) when it already has a Hokai page, OR as product_name + product_url when it does not (its page is then written free and the earliest start is a week out). Args: email: a work email for the vendor guide: the guide's slug, from vendor_catalog (guides[].slug) product_slug: the product's Hokai slug, e.g. "notion-ai" (optional) product_type: tools, agents, skills, models, companies or services product_name: the product's name, when it has no Hokai page (optional) product_url: the product's website, when it has no Hokai page (optional) starts_on: YYYY-MM-DD (optional; default is the guide's next free day) months: 12 (the only term since 2026-11-15; any other value becomes 12) company: company name (optional) agent: your agent's name (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| company | string | – | – |
| string | yes | – | |
| guide | string | yes | – |
| months | integer | – | – |
| product_name | string | – | – |
| product_slug | string | – | – |
| product_type | string | – | – |
| product_url | string | – | – |
| starts_on | string | – | – |
No output schema declared.
No examples provided.
buy_leads ~213
Buy 1 to 20 Hokai buyer leads. A lead is a person who told Smart Match the job, the tools they use and often the budget, then agreed to hear from vendors (three vendors per buyer at most). Returns checkout_url, a Stripe card payment page. Rule to pass on to the vendor: leads are delivered as buyers who fit come in. There is no stock cap: the balance never expires and one lead is used each time a buyer's brief is opened. Every purchase includes a year of Premium. Refunds are not automatic: ask damien@hokai.io. Args: email: a work email for the vendor quantity: 1 to 20 company: company name (optional) agent: your agent's name (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| company | string | – | – |
| string | yes | – | |
| quantity | integer | yes | – |
No output schema declared.
No examples provided.
buy_listing ~250
Buy a Hokai listing for an AI tool, model, agent, MCP server, skill or AI service. Returns checkout_url, a Stripe card payment page for the one-time fee: a person, or an agent that can pay, completes it. Nothing is charged by this call. A person then researches the product and writes its page. Paying never affects rankings. Refunds are not automatic: ask damien@hokai.io. Only call this when the product's owner or their team asked for it, and use their real work email: the vendor account is created for it on payment and Hokai emails it when the page goes live. Args: tool_url: the product's own website, e.g. https://example.com email: a work email for the vendor company: company name (optional) note: anything the editors should know (optional) agent: your agent's name (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| agent | string | – | – |
| company | string | – | – |
| string | yes | – | |
| note | string | – | – |
| tool_url | string | yes | – |
No output schema declared.
No examples provided.
get_listing_info ~64
How an AI product gets listed on Hokai: today's one-time price, what a listing includes, and the free badge route. Use this before buy_listing, or to answer "how do I get my AI tool listed on Hokai?".
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_tools_tree ~19
Fetch Hokai tools-tree JSON.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
order_status ~51
Has a checkout from buy_listing, buy_guide_spot or buy_leads been paid? Pass the session_id that came back with the checkout_url.
| Name | Type | Req | Description |
|---|---|---|---|
| session_id | string | yes | – |
No output schema declared.
No examples provided.
scanner_status ~19
Simple health check for the MCP server.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
submit_listing ~149
Older name for buy_listing, kept so existing agents keep working. Starts a Hokai listing and returns a payment link (checkout_url, also given as payment_url). Nothing is charged by this call. Refunds are not automatic: ask damien@hokai.io. Args: tool_url: the product's own website, e.g. https://example.com email: a work email for the vendor company: company name (optional) note: anything the editors should know (optional)
| Name | Type | Req | Description |
|---|---|---|---|
| company | string | – | – |
| string | yes | – | |
| note | string | – | – |
| tool_url | string | yes | – |
No output schema declared.
No examples provided.
vendor_catalog ~109
What an AI vendor can buy on Hokai, with live prices and limits: a listing (Get listed), a labelled Sponsored spot in a guide (Guide spots) and buyer leads (Leads). Includes every guide open for booking with its slug, its next free date and its expected reach for the next 12 months (a projection, not a promise). Call this before buy_listing, buy_guide_spot or buy_leads.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the HokAI MCP server?
HokAI is a hosted endpoint at https://hokai.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · hokai.io
claude mcp add --transport http io-hokai-hokai 'https://hokai.io/mcp'
What is the HokAI MCP server?
HokAI is an MCP server listed in the public MCP registry as io.hokai/hokai. AI tool directory MCP server, live since July 2026. Tools, agents, models, companies, services. This page covers its hosted endpoint (https://hokai.io/mcp).
Is the HokAI MCP server safe to use?
HokAI scores 74 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the HokAI MCP server expose?
HokAI exposes 9 tools: get_tools_tree, vendor_catalog, get_listing_info, buy_listing, submit_listing, and 4 more. Their descriptions and schemas cost roughly 1,313 tokens of context every time the server is loaded.
Does the HokAI MCP server require authentication?
No. We connected to HokAI without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the HokAI MCP server still maintained?
HokAI is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the HokAI MCP server?
VerifyMCP ran 12 checks on HokAI, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about HokAI: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.