HokAI

AI tool directory MCP server, live since July 2026. Tools, agents, models, companies, services.

Should I use this

Quality & Safety

B
Description quality
90%
Schema completeness
43%
Naming quality
95%
Poisoning risk
60%
Permission match
100%
Protocol compliance
100%

Findings (3)

  • HIGHTool poisoning patterns detected
  • MEDIUMTool description contains URL to non-standard domainin submit_listing
  • LOWTool description contains role marker that could confuse chat modelsin get_listing_info

Based on automated analysis of tool definitions and protocol compliance.

Context Cost

~442Tokens (tool definitions)
~377 BTypical response size
Minimal attention impact (0.35% of 128k context)

This is the approximate number of tokens consumed each time the server's tools are loaded into a model's context. Higher counts reduce the attention available for other tasks.

Install

One-Click Install

Add this to your `claude_desktop_config.json` file:

{
  "mcpServers": {
    "hokai": {
      "url": "https://hokai.io/mcp"
    }
  }
}

Remote endpoints

https://hokai.io/mcpstreamable-http

What it can do

Tool inventory

Tools (4)

🟢 Read-only🟡 Write🔴 Delete⚪ Unknown
🟢get_tools_tree

Fetch Hokai tools-tree JSON.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "get_tools_treeArguments"
}
🟡get_listing_info

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 submit_listing, or to answer "how do I get my AI tool listed on HokAI?".

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "get_listing_infoArguments"
}
🟡submit_listing(tool_url, email, company, note)

Start a HokAI directory listing for an AI tool, model, agent, MCP server, skill or AI service. Returns a payment link: a PERSON must open it and pay the one-time fee. Nothing is charged by this call, and the submission is reviewed by a human (full refund if the product is not a fit). Paying never affects rankings. Only call this when the product's owner or their team asked for it, and use their real work email: 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)

Input Schema

{
  "type": "object",
  "properties": {
    "tool_url": {
      "title": "Tool Url",
      "type": "string"
    },
    "email": {
      "title": "Email",
      "type": "string"
    },
    "company": {
      "default": "",
      "title": "Company",
      "type": "string"
    },
    "note": {
      "default": "",
      "title": "Note",
      "type": "string"
    }
  },
  "required": [
    "tool_url",
    "email"
  ],
  "title": "submit_listingArguments"
}
🟢scanner_status

Simple health check for the MCP server.

Input Schema

{
  "type": "object",
  "properties": {},
  "title": "scanner_statusArguments"
}

Recommended Prompts

retrieve_data
Get details about [item] from HokAI
Expected tools: get_tools_tree
fetch_info
Fetch [information type] using HokAI
Expected tools: get_tools_tree

Community

Rate this Server

Evidence

Recent observations

verifiedversion not recorded4 tools
verifiedversion not recorded4 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools
verifiedversion not recorded2 tools