ToolNav AI MCP server

Which servers in the official MCP registry are ToolNav AI's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to ToolNav AI

Whose server it is

Registry nameai.toolnav/directoryverified in the MCP registry

The registry name sits under toolnav.ai. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19

Stateanswerschecked 2026-10-19
Tools3
Server calls itselfToolNav AI
Server version1.0.0
Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 87 ms.

Measured dailydaily checks: 2, the first on 2026-10-19

Answeredmeasuring2 of the 7 daily checks it takes to print a share
Median first answer986 ms
Space in an agent's context≈ 337 tokensthe definitions of all its tools (3), which an agent carries on every turn
Tool definitionsB · 83 of 100

Parameters without a description: in 3 of 3

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The state of vendors' MCP servers: method and numbers →

Tools it offers3 tools · read 2026-10-19

search_tools
Search published AI tools by keyword and optional category. Matches name, description or tags. Use list_categories for valid category values. Returns source and official website URLs.
get_tool
Get a published tool by its exact slug, including available FAQs and source URLs. Returns found=false if unavailable.
list_categories
List category values present in published tool listings. Pass a returned slug to search_tools.category.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "directory": {
      "type": "http",
      "url": "https://toolnav.ai/api/mcp"
    }
  }
}

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.