_ registry / mcp streamable-http · checked 19h ago

mcpnav-search

https://mcpnav.net

Registry code: 41a0c7e3c90af342

api record

MCPNav is a searchable directory of 20,000+ MCP servers. Use search_servers to find servers for a task, get_server to fetch install commands and a copy-paste client config, list_categories to browse. Human-readable listings live at https://mcpnav.net.

endpoint
https://mcpnav.net/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is mcpnav-search live?
Yes — it answered the hub's last check (checked 19h ago). It answered 100% of checks over the last 30 days.
Is mcpnav-search free to use?
Yes — the hub reached it with no key and no payment.
What tools does mcpnav-search have?
3 tools: get_server, search_servers, list_categories.
Is mcpnav-search safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
201ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 3 tools
1 open 2 never probed 1 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • list_categories open 19h ago

    List all MCPNav directory categories with server counts and browse URLs.

    mcp-tool

    {
  "type": "object",
  "properties": {}
}
    arguments 4 lines
  • get_server unknown 19h ago

    Get one MCP server's full record: description, transports, install commands and a copy-paste client (mcpServers) config. Get slugs from search_servers.

    mcp-tool

    {
  "type": "object",
  "required": [
    "slug"
  ],
  "properties": {
    "slug": {
      "type": "string",
      "description": "Directory slug, e.g. 'filesystem'"
    }
  }
}
    arguments 12 lines
  • search_servers unknown 19h ago

    Search the MCPNav directory of 20,000+ MCP servers by keyword, with an optional category filter. Returns ranked matches with slugs, categories, publishers, transports and listing URLs.

    mcp-tool

    {
  "type": "object",
  "properties": {
    "limit": {
      "type": "integer",
      "maximum": 25,
      "minimum": 1,
      "description": "Max results to return (default 10, max 25)"
    },
    "query": {
      "type": "string",
      "description": "Free-text query, e.g. 'postgres', 'web scraping', 'slack'"
    },
    "category": {
      "type": "string",
      "description": "Optional category slug, e.g. 'databases'. See list_categories."
    }
  }
}
    arguments 19 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 41a0c7e3c90af342.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/41a0c7e3c90af342/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/41a0c7e3c90af342/badge.svg)](https://brick.blue/agent/41a0c7e3c90af342?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.