Prototype · Preview: every server in the official registry, synced every 30 minutes. Sign in with Google to write reviews.Prototype · updated every 30 min
PopNx MCPMCP servers for people who use AI · explained in plain words

Subgraph Registry MCP

by PaulieB14version 0.4.2i★ 0iRuns on your computerRepository ↗
Registry nameio.github.PaulieB14/subgraph-registry-mcp

How to install

What it does

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

  • Connects Runs on your computer
  • Account or key No key needed
  • Category Other

Why it ranks here

Lists are ordered by a usage score (out of 100) built from these parts

Popularity20/80GitHub stars or weekly downloads: the larger counts 60, the smaller 20
Freshness12/12Full marks for a release or code change within 30 days
Still answering0/8The cloud endpoint answered at the last check
Usage score32/100

Quality: Passed 3/3 basic checks (shown, not used for ordering) · Momentum: No data yet (Used only on the Trending tab)

Install

Pick the AI app you use, then copy the settings.

Let your AI install it with one sentence

Please install Subgraph Registry MCP. Follow https://mcp.popnx.com/i/paulieb14-subgraph-registry-mcp.md, show me the commands and wait for my OK before running them.

Paste it into an AI that can work on your computer (such as Claude Code or Cursor). It reads our steps, shows you the commands and waits for your OK. No key, no sign-up. · See the full text your AI reads

Passed 3/3 checks · Runs on your computer · ✓ Commands checked Nov 13, 2026

First: which AI do you use?

Pick your app and the steps appear below.

Works with Claude, with some setup first

Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone

Let AI install it

Copy this message into a Claude chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Subgraph Registry MCP for Claude on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "subgraph-registry": { "command": "npx", "args": [ "-y", "subgraph-registry-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Subgraph Registry MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open the Claude desktop app’s settings file

    SettingsDeveloperEdit Config

  3. Paste these settings and save the file

    {
      "mcpServers": {
        "subgraph-registry": {
          "command": "npx",
          "args": [
            "-y",
            "subgraph-registry-mcp"
          ]
        }
      }
    }
  4. Quit Claude and open it again

  5. Try it

    Use Subgraph Registry MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude says it is using Subgraph Registry MCP or shows a Subgraph Registry MCP tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

ChatGPT cannot connect Subgraph Registry MCP yet

Subgraph Registry MCP runs on your computer, but ChatGPT can only connect servers that run on the web

What you can do instead

A · Use an app that can connect Subgraph Registry MCP

  • Install Node.js on your computer first (one time) · Only the Claude desktop app (Windows or Mac), not the web or phone
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)
  • Install Node.js on your computer first (one time)

B · Others in Other that work with ChatGPT

Picked from the most used in the same category, only ones that connect by address with no key

Works with Claude Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Claude Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Subgraph Registry MCP for Claude Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): claude mcp add --scope user subgraph-registry -- npx -y subgraph-registry-mcp 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Subgraph Registry MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Open Terminal

    Mac: press Command+Space and type Terminal · Windows: open PowerShell

  3. Paste this command and press Enter

    claude mcp add --scope user subgraph-registry -- npx -y subgraph-registry-mcp
  4. Type /mcp in Claude Code

    You should see Subgraph Registry MCP listed as connected

  5. Try it

    Use Subgraph Registry MCP and tell me what you can do for me, then show me one thing

    ✓ If Claude Code says it is using Subgraph Registry MCP or shows a Subgraph Registry MCP tool in the answer, you are connected

Menu names checked against Anthropic’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with Cursor, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a Cursor chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Subgraph Registry MCP for Cursor on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "mcpServers": { "subgraph-registry": { "command": "npx", "args": [ "-y", "subgraph-registry-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Subgraph Registry MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open Cursor

    Open in Cursor

    Cursor asks you to confirm; click Install

  3. Open the AI chat in Cursor in Agent mode

  4. Try it

    Use Subgraph Registry MCP and tell me what you can do for me, then show me one thing

    ✓ If Cursor says it is using Subgraph Registry MCP or shows a Subgraph Registry MCP tool in the answer, you are connected

Menu names checked against Cursor’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Works with VS Code, with some setup first

Install Node.js on your computer first (one time)

Let AI install it

Copy this message into a VS Code chat. The AI checks your computer, tells you which file it will change, and waits for your OK every time.

Please install the MCP server Subgraph Registry MCP for VS Code on this computer, in this order: 1) Check Node.js with node -v. If it is missing, tell me to install it from https://nodejs.org/en/download; do not install it yourself. 2) Use only this config (already checked by PopNx MCP): { "servers": { "subgraph-registry": { "type": "stdio", "command": "npx", "args": [ "-y", "subgraph-registry-mcp" ] } } } 3) Tell me the full path of the file you will change, or the command you will run, and wait for my OK. 4) No key is needed. 5) Do what we agreed, then check that the Subgraph Registry MCP tools really show up.

This message has no key in it. If a key is needed, the AI will ask you to paste it yourself into the file or the app’s field.

  1. Install Node.js (if you don’t have it)

    Already installed? Check first · Open Terminal, type this command and press Enter

    node -v
    • A version number such as v26.13.1 = installed, skip this step
    • "command not found" (on Windows: "is not recognized") = not installed yet, or installed but Terminal needs to be closed and reopened
    How to open Terminal

    Mac: press ⌘ + Space, type Terminal, press Enter

    Windows: open Start, type Windows PowerShell, then Open

    Not installed: Open the official download page, pick the LTS version and the click-through installer: .pkg on Mac · .msi on Windows. Double-click and follow it to the end. No curl command needed

    Open the Node.js download page ↗

    When it’s done, close Terminal, open it again and run the same command. You should see a version number: node -v

    Install once; it works for everything that needs Node.js

  2. Click this button to open VS Code

    Open in VS Code

    VS Code asks you to confirm; click Install

  3. Open the AI chat in VS Code in Agent mode

  4. Try it

    Use Subgraph Registry MCP and tell me what you can do for me, then show me one thing

    ✓ If VS Code says it is using Subgraph Registry MCP or shows a Subgraph Registry MCP tool in the answer, you are connected

Menu names checked against VS Code’s help page on Nov 11, 2026 · your screen may differ slightly by app version

Other apps that use MCP, such as Windsurf, Zed or Gemini CLI, each add servers differently. See how in the app list.

See every app that uses MCP →

JSON settings are under “For developers” below

Stuck? Ask people who use Subgraph Registry MCP💬 Discussion →
For developers: Terminal commands and JSON settings

Installed on your computer

Claude Code

claude mcp add --scope user subgraph-registry -- npx -y subgraph-registry-mcp

Claude Desktop (claude_desktop_config.json)

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

Cursor (~/.cursor/mcp.json)

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

VS Code (mcp.json)

{
  "servers": {
    "subgraph-registry": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "subgraph-registry-mcp"
      ]
    }
  }
}

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

At a glance

Downloads per weeki
756/wk
Connection
Runs on your computer
Latest versioni
0.4.2
Categoryi
Other
Published to registryi
May 2, 2026
Code last changedi
Nov 16, 2026
Maker
PaulieB14
Packages
npm: subgraph-registry-mcp
Registry status
Active

Which apps can use it

Based on how this server connects and on each app’s own docs, checked Nov 10, 2026.

Run on your computer in

ClaudeGooseLM StudioMsty StudioCherry StudioCursorVS Code + GitHub CopilotVisual StudioWindsurf (Devin Desktop)ZedKiroClineContinueJetBrains AI AssistantClaude CodeCodex CLIGemini CLIOpenCodenodecodeWarpLibreChatRaycast

All apps, with pros and cons →

Related guides

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 19, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account PaulieB14, which owns the repo

  • ✓ Pass

    Still maintained

    Code last changed 3 days ago

  • ✓ Pass

    Has a licence

    Uses MIT

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Published vulnerabilities (OSV.dev)

No entries on OSV.dev for subgraph-registry-mcp@0.4.2

Checks only this package version, not every dependency · checked Nov 15, 2026

What we check → · JSON

Makers: ask for a re-check or report wrong info
For makers: add a badge to your README

If you made this, paste this code into your README. The badge links back to this page.

[![Featured on PopNx MCP](https://mcp.popnx.com/badge/paulieb14-subgraph-registry-mcp.svg)](https://mcp.popnx.com/en/servers/paulieb14-subgraph-registry-mcp)

Discussion

Ask, share a tip or report that it does not work. Sorted by what people marked helpful.

No posts yet. Be the first to ask or share.

Posts here are written by users, not the PopNx team.

Sign in to post

User reviews

No reviews yet

Sign in to write a review

Compared with others in Otheri

  • More stars than 0% of the other 20693 servers in this category
  • Published to the registry more recently than 5% of the other 20693 servers in this category
  • Basic checks equal to or better than 99% of the other 20693 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is Subgraph Registry MCP safe?

It passed 3 of 3 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

The registry does not list a required key, though some servers ask you to sign in on first use.

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed 3 days ago, and the latest version (0.4.2) reached the registry 7 months ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: World Monitor, openstatus, Oh My Posh Validator, Strata, Jitsu

Similar alternatives

Same category, other makers, commands already checked. Official ones first, then by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

World Monitor

Real-time global intelligence on conflict, markets, energy, trade, shipping and cyber. 100 tools.

by koala73Widely used★ 90.9KUpdated 3 days ago

Runs in the cloud✓ service owner · worldmonitor.app

openstatus

Manage monitors, status pages, incidents and maintenances in your openstatus workspace.

by openstatusHQWidely used★ 9.3KUpdated 2 months ago

Runs in the cloud✓ service owner · openstatus.dev

Oh My Posh Validator

Validate oh-my-posh configurations and segment snippets against the official schema.

by JanDeDobbeleerWidely used★ 23.8K Stars for the whole repoUpdated 30 days ago

Runs in the cloud✓ service owner · ohmyposh.dev

Strata

MCP server for progressive tool usage at any scale (see https://klavis.ai)

by Klavis-AIGrowing★ 5.8KUpdated 14 months ago

Runs in the cloudRepo archived✓ klavis.ai

Jitsu

Manage Jitsu data pipelines: destinations, streams, connections, functions, live events.

by jitsucomWidely used★ 5.1KUpdated 4 months ago

Runs in the cloud✓ service owner · jitsu.com
Compared with similar ones
This one
Subgraph Registry MCP
World MonitoropenstatusOh My Posh ValidatorStrataJitsu
Runs whereInstalls on your computerRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to installRuns in the cloud, nothing to install
Needs a keyNoNoNoNoNoNo
Add with + in ClaudeNoNoNoNoNoNo
Basic checks3/34/44/44/41/44/4
LicenseMITAGPL-3.0AGPL-3.0MITApache-2.0MIT
PriceNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registryNo cost listed in the registry

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.6"]}}}

Inspect tools/list: Node 0.13.6 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.

  1. Discover explicitly. Tool-call parameters below work with published 0.13.6:
   {"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.

  1. 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.

  1. 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.
  2. Execute only when wanted and authorized, using an advertised execution tool and reviewed fields. Bearer format: Authorization: Bearer . 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.6 adds

npm test now passes a test/*.test.mjs glob. Node 22 rejects node --test test/ (a bare directory), which also broke the scheduled-update test gate on its first dry run. No runtime behaviour changed.

What 0.13.5 adds

query_for_goal fixes found by the weekly health check:

  • No chain is hidden by snapshot signals. Zero active allocations or denied indexing rewards only *rank* a deployment lower; they never exclude it (Arc is queryable without rewards). Unserved deployments are planned after served ones, annotated snapshot_note, and with validate_schema:true a deployment the gateway rejects ("no allocations", validation failure) is skipped and the next-ranked one is tried.
  • "pools containing WETH/ETH/USDC…" maps to a token0/token1 filter (where: {or: [...]}) using per-chain addresses for the major tokens (WETH, WBTC, USDC, USDT, DAI, ...). Unknown symbols are reported as unmet, not silently dropped; pass an address instead.
  • More spam signals (never delete rows): TVL-per-transaction and volume-to-TVL sanity, implausible totalSupply, an absolute TVL cap. If every row is flagged, another deployment is tried, otherwise rows are ordered by volumeUSD and reported with all_flagged.
  • Keyless plans are no longer id-only for Uniswap v3/v4-family swaps, pools and positions: they come from a bundled schema-family catalog (labelled field_source: "bundled_family_catalog", not live-validated) with newest-first/TVL ordering. A key with validate_schema:true still confirms fields live.
  • The scheduled registry update now also re-pins the literal npx package in src/index.js and README, so the pinned config example matches the release.
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.6.

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 (401 otherwise). See HTTP transport security. Stdio (the default) is unchanged.

0.13.0 made query_for_goal skip deployments that time out, have failing indexers or are more than 2 hours behind, and fall back to the next deployment that fits the goal. Skips are reported in goal_mapping.skipped_deployments, and recommend_subgraph also drops recently failed deployments. Token and pool results carry token_quality spam flags (spam_handling, trusted_tokens); flagged rows move last by default and are never removed. A chain named late in a long goal is no longer ignored. The bundled registry database is unchanged.

0.12.0 added goal-specific query_for_goal planning (entity mapping, confidence, unmet/filters_not_applied, alternatives, optional validate_schema) and human-handoff bring-your-own-key onboarding. It also ships the discovery fixes merged after 0.11.0: chain-only inference, empty-result diagnostics, strict search validation and structured next_action hints. The bundled registry database is unchanged from 0.11.0. A mounted connector keeps its own pinned runtime until it is updated. See the discovery audit.

The Problem

Agents querying The Graph need to discover and select the right subgraph before they can query data. Search results include snapshot query volume, classification, entities and starter queries to reduce extra discovery steps. Live schema relevance, health and successful execution still require separate checks when needed.

What It Does

  1. Builds a snapshot from active published subgraphs in the configured Graph Network meta-subgraph; it does not enumerate all private/Studio deployments
  2. Attempts to fetch schema metadata for indexed deployments; missing data remains a coverage limitation
  3. Extracts contract addresses from each manifest's dataSources and templates — agents can answer "which subgraph indexes contract 0x… on chain X?"
  4. Stores a starter GraphQL query from parsed schema metadata where available; it is an example, not a live validation or a goal-specific answer
  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 keyed gateway and optional paid x402 routes — the MCP never signs payments or auto-pays; see the explicit payment-approval warning below
  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)

Contract lookup, measured freshness, and goal-to-starter workflow

Released in 0.11.0, the Node MCP server (stdio and SSE) implements three complementary tools. Health is advertised only when a Studio key is configured; the other two are keyless preparation/discovery tools. Existing search/recommend/detail calls remain discovery-only; they never probe or execute. No crawler/database migration or Python API change is required.

find_by_contract(address, chain?, limit=3)

JavaScript examples use a host-provided mcp.call(name, args) adapter. For the actual MCP SDK Client.callTool({name, arguments}) flow, see scripts/audit-discovery.mjs.

await mcp.call("find_by_contract", {

address: "0x1F98431c8aD98523631AE4a59f267346ea31F984", chain: "ethereum", // normalized to mainnet; omit to search all networks limit: 3, // integer 1–20 });

Matches exact, case-insensitive EVM addresses from crawled manifests, checking each manifest record's network (falling back to the deployment network). Ranks allocated, non-denied snapshot deployments by reliability then 30-day volume; de-duplicates before limiting. get_top_subgraph_deployments keeps its existing (contract_address, chain) interface and uses the same implementation.

Results include matched manifest records, starters, and schema_entities for the whole deployment. Current registry data does not map a contract to particular entities/fields, so coverage.contract_to_entity_mapping is explicitly null. Dynamic template instances and substreams may be missing. No match is not proof that no subgraph indexes the contract; allocation/reliability remain snapshot signals.

check_subgraph_health(id | subgraph_id | ipfs_hash | deployment_id)

Explicitly opts into one Studio-key gateway request for:

{ _meta { deployment hasIndexingErrors block { number timestamp } } }

Known subgraph IDs are pinned to the crawled deployment. Returns freshness.live with measured observed_at (Unix seconds), indexed block/timestamp, indexing-error flag, HTTP status, and one of serving, indexing_errors, metadata_unavailable, or query_failed. A successful metadata query does not prove chain-head sync; synced_to_chain_head remains null. Unsupported metadata is unknown, not fabricated.

Search, recommendation, detail, contract results, and JSON-LD manifests expose cached freshness without making calls. Before a probe, live is null. Observations are process-local (maximum 500), become stale: true after 300 seconds, and disappear on restart. There is no background check or new reliability-score interpretation. registry_updated_at is the upstream metadata update, not a crawl/health timestamp. This credential-only tool is not advertised on keyless servers.

query_for_goal(goal, chain?, first?, execute=false, validate_schema=false)

Since 0.12.0: goal-specific planning. Earlier releases return the first recommendation's stored starter instead.

// Keyless and local: no network call.

const prepared = await mcp.call("query_for_goal", { goal: "Uniswap V4 pool IDs on Arc", chain: "arc", first: 3, }); // prepared.query -> { _meta {…} pools(first: 3) { id } } // prepared.goal_mapping -> entity "Pool", confidence "medium", rationale, // unmet, alternatives // prepared.onboarding -> human-handoff key setup (keyless servers only)

// With the operator's own key: one scoped schema check + one query. cons

Only the beginning is shown; read the rest in the repo