MCP Server

Connect your AI agent or coding assistant to hlist.cc through the Model Context Protocol. Three tools, one endpoint, no API key required.

Endpoint

POST https://hlist.cc/api/mcp
Content-Type: application/json

Transport: Streamable HTTP (JSON-RPC 2.0, stateless). CORS-enabled for browser agents.

Tools

ToolArgsReturns
search_ai_tools query (required), category (optional) Top 10 matches: name, slug, description, pricing, China accessibility, website, live GitHub stars
get_tool slug (required) Full record for one tool: all metadata + 4-language URLs + vote/comment API endpoints
list_categories — All categories with tool counts

Quick test (curl)

# List available tools
curl -X POST https://hlist.cc/api/mcp \
  -H "Content-Type: application/json" \
  -d {"jsonrpc":"2.0","id":1,"method":"tools/list"}

# Search for video AI tools
curl -X POST https://hlist.cc/api/mcp \
  -H "Content-Type: application/json" \
  -d {"jsonrpc":"2.0","id":2,"method":"tools/call","params":{"name":"search_ai_tools","arguments":{"query":"video generator","category":"video"}}}

# Get one tool by slug
curl -X POST https://hlist.cc/api/mcp \
  -H "Content-Type: application/json" \
  -d {"jsonrpc":"2.0","id":3,"method":"tools/call","params":{"name":"get_tool","arguments":{"slug":"sora"}}}

What makes this different

  • China-accessibility data — the field no other AI-tools MCP exposes: ok / unstable / blocked / unknown for each tool from mainland China.
  • Live GitHub stats — stars/forks/push fetched at build time, not a stale snapshot.
  • 4-language metadata — every tool carries EN/zh/ja/ko page URLs.
  • No key, no rate-limit wall — public endpoint, designed for agent use.

Agent configuration

Add to your MCP client config:

{
  "mcpServers": {
    "hlist": {
      "url": "https://hlist.cc/api/mcp",
      "transport": "streamable-http"
    }
  }
}

Other data exits