MCP.Market

Subgraph Registry MCP server

by PaulieB14·io.github.PaulieB14/subgraph-registry-mcp·v0.4.2

Discover and query 15,500+ classified subgraphs on The Graph Network

A92/100grade A
What users say
No reviews yet
Be the first
Safety scan
A92/100

full report

Adoption
Growing

0 stars649 downloads/wk

Reviews

Write one

Nobody has reviewed Subgraph Registry yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Subgraph Registry tools (4)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • get_subgraph_detail

    Get full classification detail for a specific subgraph by its subgraph ID or IPFS hash. Returns domain, protocol type, canonical entities, all entity names with field counts, reliability score, signal data, query URL, and step-by-step query instructions.

  • list_registry_stats

    Get an overview of the subgraph registry: total count, available domains, networks, and protocol types with counts. Use this to understand what data is available before searching.

  • recommend_subgraph

    Given a natural-language goal like 'find DEX trades on Arbitrum' or 'get lending liquidation data', returns the best matching subgraphs with reliability scores and query URLs. Automatically infers domain and protocol type from the goal. Each result includes a query_url — replace [api-key] with your Graph API key to query live data.

  • search_subgraphs

    Search and filter the classified subgraph registry (15,500+ subgraphs). Filter by domain (defi, nfts, dao, gaming, identity, infrastructure, social, analytics), network (mainnet, arbitrum-one, base, matic, bsc, optimism, avalanche), protocol_type (dex, lending, bridge, staking, options, perpetuals, nft-marketplace, yield-aggregator, governance, name-service), canonical entity type (liquidity_pool,

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan2 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 2 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
Overall 92/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Subgraph Registry compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
92/100
higher than 95% of 48,255 servers
Tools
4
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
Downloads a week
649
more than 91% of 12,191 servers with a package

What its tools let an agent do: 4 read

Install Subgraph Registry in Claude Code, Cursor or VS Code

Runs npx -y subgraph-registry-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add subgraph-registry-mcp -- npx -y subgraph-registry-mcp
Add to Cursor

What the publisher says

From the Subgraph Registry repository's README, as published. We do not edit it. Read it on GitHub

Subgraph Registry

Agent-friendly semantic classification of all subgraphs on The Graph Network.

Pre-computed index of 15,330 subgraphs with domain classification, protocol type detection, schema fingerprinting, canonical entity mapping, and composite reliability scoring.

What's new in 0.8.0 — three agent-discovery upgrades:

- Semantic search via 384-dim embeddings (semanticsearchsubgraphs)

- Schema evolution tracking with stability days surfaced on every result (getschemachanges)

- OpenAPI 3.1 spec auto-generated for MCP tools + REST routes, served at /.well-known/openapi.json

The Problem

Agents querying The Graph need to discover and select the right subgraph before they can query data. Today this requires 3-4 tool calls (search, check volumes, fetch schema, infer structure) before any real work happens. This registry flips that: agents start with structured knowledge, not a blank slate.

What It Does

  1. Crawls all active subgraphs from the Graph Network meta-subgraph
  2. Fetches the GraphQL schema for every deployment
  3. Extracts contract addresses from each manifest's dataSources and templates — agents can answer "which subgraph indexes contract 0x… on chain X?"
  4. Generates a per-subgraph starter GraphQL query from the parsed schema (real top entity, real fields, sensible orderBy) — no more generic boilerplate that doesn't compile against most subgraphs
  5. Classifies each subgraph by domain, protocol type, canonical entities, and schema family
  6. Scores reliability using on-chain signals (query fees, volume, curation, stake)
  7. Returns x402 + legacy query URLs — agents can pay $0.01 USDC on Base per query (no API key) or use a Studio key
  8. Publishes as SQLite database + REST API + MCP server + per-subgraph JSON-LD at /.well-known/subgraph/{id}.jsonld for ecosystem crawlers
  9. Generates visual dashboards and bot-readable category files (auto-updated with each sync)

Querying with x402 (no API key)

Every result includes queryurlx402 alongside the legacy queryurl. The Graph's public x402 gateway (live since 2026-05-08) accepts $0.01 USDC on Base** per query with zero signup.

// An x402-native agent — discovery to data in two calls
const { recommendations } = await mcp.call("recommend_subgraph", {
  goal: "find DEX trades on Arbitrum",
});
const top = recommendations[0];

// POST your GraphQL query. The first call returns HTTP 402 with a
// base64 `payment-required` header; the x402 client signs the
// EIP-3009 USDC transfer on Base and retries automatically.
const data = await x402Fetch(top.query_url_x402, {
  method: "POST",
  body: JSON.stringify({ query: "{ swaps(first: 5) { id amountUSD } }" }),
});

Pricing manifest returned per subgraph:

{
  "amount_usd": 0.01,
  "asset": "USDC",
  "asset_contract": "0x833589fCD6eDb6E08f4c7C32D4f71b54bdA02913",
  "chain": "base",
  "network": "eip155:8453",
  "pay_to": "0x79DC34E41B2b591078d3dE222C43EcaaBD52FcCB",
  "scheme": "exact",
  "asset_transfer_method": "eip3009"
}

Client libraries: @graphprotocol/client-x402, x402-fetch, or any generic x402 wrapper.

Registry at a Glance

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Subgraph Registry: common questions

Is Subgraph Registry MCP server safe?
Yes, by our scan: it is graded A (92/100). Read the Subgraph Registry safety report
How do I install Subgraph Registry?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Subgraph Registry need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Subgraph Registry maintained?
The last commit was 39 days ago (2026-09-26). The latest release is v0.4.2.
What can I use instead of Subgraph Registry?
Servers from other publishers that do the same job: MCP Registry Server MCP server.
How does Subgraph Registry compare with other MCP servers?
safety score 92/100 (higher than 95% of 48,255 servers); tools 4 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Subgraph Registry

Same job from other publishers: the closest match first, then the best rated.

  • MCP Registry Server
    Publish and discover MCP servers via the official MCP Registry. Powered by HAPI MCP server.
    A

More from PaulieB14 →