Standalone MCP directory — 61862 servers across 36145 domains, each exposing a remote (streamable-http) endpoint and health-probed via a JSON-RPC initialize handshake.

Add your server

Aggregated from the official MCP Registry, Smithery and other public registries, plus our own crawling and operator submissions. Every server is de-duplicated by endpoint, health-probed via a live JSON-RPC initialize handshake, and statically scanned for malware & prompt-injection patterns in its advertised tools before listing — yielding 61862 indexed servers, of which 53021 answered within the last 6 h.

Indexed
61862 servers
36145 domains
+4109 new this week
Healthy
53021 servers
31253 domains
initialize handshake < 6 h
Conformant
35921 servers
19177 domains
tools/list verified · ~1350ms p95
x402-capable
30 servers
26 domains
accepts x402 payment

Top rated

by quality score · health · trust signals
# Tool Grade Score
1 Homo Universalis — HU-DIAMOND v1.1 Cryptographic Verifier & AST Kintsugi MCP Server A 10.000
2 FlowState Hosted A 10.000
3 Verified x402 Catalog A 10.000
4 True Value Rankings A 10.000
5 X402-Broker Universal MCP Gateway & Multi-Agent Swarm Router A 10.000
6 GraphQL operation count, query discarded A 9.998
7 Paper Search (arXiv + Semantic Scholar + OpenAlex) A 9.994
8 BNF production count, body discarded A 9.994
9 multibase z-prefix, value discarded A 9.994
10 Liters to US gallons A 9.994
11 Slugs to kilograms, number discarded A 9.992
12 Sponsored Agent Placement A 9.991
13 UUID v7 unix-ms layout, value discarded A 9.991
14 Train-Case segment count, text discarded A 9.991
15 Utility 87 A 9.991
16 Utility 43 A 9.991
17 Asia/Sakhalin clock A 9.991
18 GitHub topic slug charset, value discarded A 9.989
19 Utility 18 A 9.989
20 pyproject.toml table count, body discarded A 9.989

All MCP servers

Continuously aggregated · refreshed daily.

/api/v1/mcp/stats

Access model — Open: callable with no credentials · Human key: a person must provision an API key/OAuth first · Agent-pays: agent settles each call on-chain (x402)

“Agent Knowledge Network” is shared by 2 different URLs

All exact-name matches are shown; ranked results follow.

“Arcology Knowledge Node” is shared by 2 different URLs

All exact-name matches are shown; ranked results follow.

“CliDeck MCP — Network Knowledge” is shared by 3 different URLs

All exact-name matches are shown; ranked results follow.

“Fodda Knowledge Graphs” is shared by 2 different URLs

All exact-name matches are shown; ranked results follow.

“FoxNose Knowledge” is shared by 2 different URLs

All exact-name matches are shown; ranked results follow.
  • Hybrid search, schema introspection and record read/write over FoxNose collections

  • Managed knowledge for AI agents: hybrid search, auto-embeddings and live schema introspection over your own collections, behind one endpoint. Agents usually fail at the knowledge layer, not the model. The usual setup is a vector database, an embedding pipeline, a sync job and a hand-written MCP server that drifts out of step with all three. FoxNose replaces that with one managed service that speaks REST and MCP over the same data and the same schema. ## Tools | Tool | What it does | | --- | --- | | `discover_resources` | Lists the collections the key can reach, with their schemas | | `describe_resource` | Returns the live JSON Schema for one collection | | `search_records` | Hybrid search: vector similarity, full text and structured filters in one query | | `query_records` | Filtered, sorted, paginated listing | | `get_record` | Fetches a single record | | `create_record` | Creates a record (requires a key with create grants) | | `update_record` | Updates a record (requires a key with update grants) | Because the agent reads the schema at runtime, you do not describe your data shape in the prompt, and a schema change does not silently break the agent. ## Connecting Create a Flux API key in the dashboard, issue a bearer token bound to it, and paste the token when you add this server. Scopes follow the key: a collection the key cannot read over REST is not reachable over MCP either, so a read-only key is a read-only agent. If the key can read more than one Flux API, set the optional API prefix field. With a single API the prefix is selected automatically. The write tools appear in `tools/list` only when the presented key grants create and update on the selected API. A read-only key sees five tools instead of seven. ## Links - [Documentation](https://foxnose.net/docs/mcp) - [Connect Claude](https://foxnose.net/docs/guides/connect-claude-mcp) - [Connect ChatGPT](https://foxnose.net/docs/guides/connect-chatgpt-mcp) - [Pricing](https://foxnose.net/pricing) — free tier, no card Run by [FoxNose](https://foxnose.net).

“PulseWatch public knowledge” is shared by 2 different URLs

All exact-name matches are shown; ranked results follow.

“Soracom Knowledge” is shared by 2 different URLs

All exact-name matches are shown; ranked results follow.

“VineVerse — Bible Knowledge Graph” is shared by 3 different URLs

All exact-name matches are shown; ranked results follow.