Subgraph Registry

Discover published subgraphs on The Graph Network by chain, protocol, entity or contract, then prepare a bounded GraphQL starter.

The bundled snapshot contains 15,452 classified subgraph records. It is not a live directory of every subgraph: Studio-only deployments, dynamic contracts and later updates may be absent. Availability must be checked separately from ranking.

Start here: agents and MCP users

Share the canonical SKILL.md for the complete agent workflow.

1. Connect a pinned, published release (Node 20 is CI-tested):

   {"mcpServers":{"subgraph-registry":{"command":"npx","args":["-y","subgraph-registry-mcp@0.13.2"]}}}
   

   Inspect tools/list: Node 0.13.2 exposes 10 tools without a key, or 19 total with a Studio key. A hosted connector can mount a different subset or corpus; installing npm does not update or restart it.

2. Discover explicitly. Tool-call parameters below work with published 0.13.2:

   {"name":"search_subgraphs","arguments":{"query":"uniswap v3","network":"ethereum","limit":3}}
   

   For newer networks, an explicit discovery opt-in can include zero-allocation snapshot records without probing them:

   {"name":"search_subgraphs","arguments":{"network":"arc","include_unserved":true,"limit":3}}
   

   arc is mainnet; arc-testnet is distinct. Neither missing rewards/curation nor zero allocations proves unqueryability. Denied/testnet opt-ins remain separate.

3. Prepare locally, if the tool is advertised:

   {"name":"query_for_goal","arguments":{"goal":"Uniswap v3 pools on Ethereum","first":2,"execute":false}}
   

   Inspect the selected deployment, query, goal_mapping and validation labels. Releases before 0.12.0 return a stored starter that may not answer the goal; older connectors can use recommendation/detail instead.

4. Bring your own Studio key — set up by a human. This server never ships or shares a key. Studio keys belong to a Studio account managed by a person, so agents should hand this step to their operator rather than sign up or mint keys. The operator creates a key at Studio API Keys, stores it via the host's secret manager or environment as THE_GRAPH_STUDIO_API_KEY and restarts the server; never paste it in chat, source, tool arguments or logs. Official pricing currently advertises 100,000 free queries/month; verify the account's plan and remaining allowance. It is not a new quota per key; Studio development endpoints have separate limits. See host configuration.

5. Execute only when wanted and authorized, using an advertised execution tool and reviewed fields. Bearer format: Authorization: Bearer <STUDIO_API_KEY>. Read GraphQL errors and partial data even on HTTP 200. On missing credentials/quota, stop and resolve that issue; never silently switch to x402.

What 0.13.2 adds

npm/ClawHub 0.13.2 hardens installation and network behaviour: dependencies are pinned to exact versions, semantic search uses only the bundled model (never a download; if it is missing the tool answers with keyword search and says so), and a missing registry.db is an error unless SUBGRAPH_REGISTRY_ALLOW_DB_DOWNLOAD=1 is set. Generated config examples use the literal pinned package subgraph-registry-mcp@0.13.2.

0.13.1 secured the optional HTTP/SSE transport. It binds 127.0.0.1 by default and refuses a non-loopback bind unless SUBGRAPH_REGISTRY_HTTP_TOKEN is set; then every route except /health needs Authorization: Bearer <token> (401 otherwise). See [HTTP transport security

... View full README on GitHub