Subgraph Registry MCP logo

Subgraph Registry MCP

Discover, classify, rank, and query 15,330 subgraphs from The Graph Network.

Install Subgraph Registry MCP

Pick your client, then add it in one click or paste the config.

STDIONode.js
~/Library/Application Support/Claude/claude_desktop_config.json
claude_desktop_config.json
{
  "mcpServers": {
    "subgraph-registry-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "subgraph-registry-mcp"
      ]
    }
  }
}

Settings → Developer → Edit Config, merge this into mcpServers, then fully quit and reopen Claude Desktop.

Automated check passed— started and listed 8 tools correctly (6d ago).

Overview

The subgraph-registry-mcp MCP server indexes classified subgraphs from The Graph Network and helps agents identify suitable deployments before querying data. It combines keyword and 384-dimensional semantic search with domain, protocol, schema, contract, network, and reliability metadata. Results include generated starter GraphQL queries and x402 or legacy query URLs. Reach for it when an agent needs to find a relevant subgraph by use case, chain, protocol, schema, or contract address.

Use cases

  • Find subgraphs for a natural-language data goal
  • Compare deployments by chain, domain, or protocol
  • Locate subgraphs indexing a contract address
  • Start GraphQL requests from generated schema-aware queries

Key features

  • Keyword and semantic subgraph search
  • Domain, protocol, schema, and contract classification
  • Reliability scoring from on-chain signals
  • Schema evolution tracking
  • Generated GraphQL starter queries
  • x402 and legacy query URLs

Tools8

What Subgraph Registry MCP lets your agent do. Expand a tool for its parameters.

Verified live~2.6k tokens of context

Security & health

What it can reach and how reliably it runs — from our own checks, not the maintainer’s claims.

ActiveLast checked 2d ago

Recent health check succeeded.

12/14 checks healthy over the last 90d

What it can do

From the 8 tools this server returned when we ran it.

Runs commands · 3Handles credentials · 1Makes network requests · 4Read-only tools · 5
Network at startup3 connections
Files written at startupNone
Install scriptsNone
npm provenanceNot published
Package age236 days
Maintainers1

Observed 2026-11-02 in an isolated sandbox. A description of reach, not a security audit.

Supply-chain signal

No high-severity advisories surfaced by our automated scan.

Critical 0High 0Medium 0Low 0

Scanned 17h ago via OSV.dev · subgraph-registry-mcp (npm)

Adoption & maintenance

Factual signals from GitHub, npm, and our automated checks — not a rating.

npm downloads1.7kPackage downloads in the last 30 days.
Last commit2d agoMost recent push to the default branch.
Availability100%Our rolling endpoint + install checks that succeeded.
Install checkPassedOur sandbox started it and listed its tools.
Tools exposed8Callable tools this server registers over MCP.

How Subgraph Registry MCP works

What subgraph-registry-mcp does

The subgraph-registry-mcp MCP server gives agents a structured index of active subgraphs on The Graph Network. The registry contains 15,330 pre-computed records with domain classifications, protocol type detection, schema fingerprints, canonical entity mappings, contract addresses, and composite reliability scores.

It is intended for the discovery step that comes before data retrieval. Instead of starting with an unknown GraphQL endpoint, an agent can search for a use case such as DEX trades, identify candidate deployments, inspect their metadata, and use the generated starter query as a basis for a data request.

The index covers domains including DeFi, NFTs, infrastructure, identity, analytics, DAO, gaming, and social applications. It also organizes records by networks such as Ethereum, Base, BSC, Arbitrum, Polygon, Optimism, and Avalanche, plus protocol categories including DEX, lending, staking, bridges, NFT marketplaces, and governance.

How it works

The registry crawls active subgraphs from The Graph Network’s meta-subgraph and fetches each deployment’s GraphQL schema. It extracts contract addresses from manifest data sources and templates, then parses schemas to identify entities and fields. For each subgraph, it generates a starter GraphQL query using an actual top-level entity, available fields, and an appropriate ordering field.

The subgraph-registry-mcp server supports both term-based and semantic discovery. search_subgraphs ranks matches by matched query terms and then reliability. semantic_search_subgraphs uses 384-dimensional embeddings and cosine similarity, which can surface conceptually related results even when the wording differs.

Reliability is a 0-to-1 composite based on query fees, 30-day query volume, community curation, and indexer allocation. These signals are log-scaled and capped, and denied or deprecated subgraphs receive a penalty. Search results include age and maturity information; term-based search can place young matches in a separate emerging list, while semantic search ranks by similarity rather than reliability.

Tools and capabilities

  • search_subgraphs for term-based discovery with reliability-aware ranking.
  • semantic_search_subgraphs for embedding-based discovery.
  • recommend_subgraph for recommendations based on a stated goal.
  • get_schema_changes for schema evolution information, including stability days surfaced on results.
  • Contract-address discovery across chains using extracted manifest data.
  • Generated GraphQL starter queries based on each deployment’s parsed schema.
  • x402 and legacy query URLs returned with results.

The response includes a pricing manifest with the asset, Base network identifier, recipient, payment scheme, and EIP-3009 transfer method. A Studio key can be used through the legacy query URL.

Limitations and notes

The reliability score measures usage and traction rather than code quality. Because its inputs are cumulative, newer subgraphs can receive low scores even when they are functional. The registry exposes age and maturity labels to make that distinction visible, and semantic search is described as age-neutral because it ranks by similarity.

It also does not establish that every indexed subgraph is currently queryable or that generated starter queries cover every schema edge case.

Reviews

No reviews yet — be the first to share how it worked for you.

Frequently Asked Questions about Subgraph Registry MCP

subgraph-registry-mcp is an MCP server that connects agents to a classified index of subgraphs on The Graph Network. Its main tools include search_subgraphs, semantic_search_subgraphs, recommend_subgraph, and get_schema_changes, with results that expose schemas, reliability data, generated starter queries, and query URLs.

It ranks keyword results by matched query terms and then reliability, while semantic search ranks by cosine similarity from 384-dimensional embeddings. Reliability combines query fees, 30-day volume, curation, and indexer allocation, with age and maturity information included to qualify newer results.

Yes, the registry extracts contract addresses from subgraph manifest data sources and templates. Agents can use that indexed information to identify which subgraphs index a specified contract on a given chain.

Yes, results include x402 and legacy query URLs. The x402 route is described as costing $0.01 USDC on Base per query without an API key, while the legacy route can be used with a Studio key.

It identifies the project as an MCP server and describes REST, SQLite, OpenAPI, and JSON-LD outputs, but gives no supported installation procedure.

Related MCP servers

Add a badge to your READMEShow it’s listed — live SVG, Markdown or HTML.

AllMCPs Directory Badge

Full Badge Customizer

Showcase your server listing on GitHub or your project documentation. Embed this dynamic SVG badge to highlight official listing status and live engagement.

Badge Style:
Live Dynamic SVG PreviewSubgraph Registry MCP AllMCPs Directory Badge
Markdown (GitHub README)
[![AllMCPs](https://allmcps.com/api/badge/subgraph-registry-mcp?style=directory)](https://allmcps.com/mcp/subgraph-registry-mcp)
HTML Embed
<a href="https://allmcps.com/mcp/subgraph-registry-mcp"><img src="https://allmcps.com/api/badge/subgraph-registry-mcp?style=directory" alt="Subgraph Registry MCP on AllMCPs" /></a>