Public Streamable-HTTP MCP server for the Metagraphed Bittensor subnet integration registry — discover subnets, check health and economics, read metagraph data, and look up accounts or API surfaces without wallets or signing.
Not an official OpenTensor/Bittensor project, not a wallet/validator/credential tool, and not an alpha/price dashboard — matching Metagraphed's own README framing., Registry MCP tools are read-only by design: no transaction building and no extrinsic submission, so there is no wallet-signing risk from the documented MCP surface., Returned subnet/API metadata can still influence generated configs or integration code — review outputs before pointing production traffic at a third-party subnet API., As of 2026-07-22, bare unauthenticated POSTs to https://api.metagraph.sh/mcp returned HTTP 401 with a Bearer WWW-Authenticate challenge (OAuth protected-resource metadata published)., Documented install remains `claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp`; MCP clients that support OAuth/DCR may complete auth. Use the public REST API for keyless HTTP probes.
Privacy notes
Tool arguments and responses (subnet queries, hotkeys, account lookups, search text) leave your machine and are processed by Metagraphed's hosted API at api.metagraph.sh., Do not paste private keys, mnemonics, coldkey/hotkey secrets, or validator credentials into prompts or MCP tool arguments — this server is not a signing or wallet surface., MCP client logs and chat transcripts may retain registry query results outside Metagraphed's own retention controls.
5 safety and 3 privacy notes across 4 risk areas. Review closely: credentials & tokens, third-party handling.
4 areas
SafetyCredentials & tokensNot an official OpenTensor/Bittensor project, not a wallet/validator/credential tool, and not an alpha/price dashboard — matching Metagraphed's own README framing.
SafetyGeneralRegistry MCP tools are read-only by design: no transaction building and no extrinsic submission, so there is no wallet-signing risk from the documented MCP surface.
SafetyThird-party handlingReturned subnet/API metadata can still influence generated configs or integration code — review outputs before pointing production traffic at a third-party subnet API.
SafetyCredentials & tokensAs of 2026-07-22, bare unauthenticated POSTs to https://api.metagraph.sh/mcp returned HTTP 401 with a Bearer WWW-Authenticate challenge (OAuth protected-resource metadata published).
SafetyCredentials & tokensDocumented install remains `claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp`; MCP clients that support OAuth/DCR may complete auth. Use the public REST API for keyless HTTP probes.
PrivacyExecution & processesTool arguments and responses (subnet queries, hotkeys, account lookups, search text) leave your machine and are processed by Metagraphed's hosted API at api.metagraph.sh.
PrivacyCredentials & tokensDo not paste private keys, mnemonics, coldkey/hotkey secrets, or validator credentials into prompts or MCP tool arguments — this server is not a signing or wallet surface.
PrivacyExecution & processesMCP client logs and chat transcripts may retain registry query results outside Metagraphed's own retention controls.
Safety notes
Not an official OpenTensor/Bittensor project, not a wallet/validator/credential tool, and not an alpha/price dashboard — matching Metagraphed's own README framing.
Registry MCP tools are read-only by design: no transaction building and no extrinsic submission, so there is no wallet-signing risk from the documented MCP surface.
Returned subnet/API metadata can still influence generated configs or integration code — review outputs before pointing production traffic at a third-party subnet API.
As of 2026-07-22, bare unauthenticated POSTs to https://api.metagraph.sh/mcp returned HTTP 401 with a Bearer WWW-Authenticate challenge (OAuth protected-resource metadata published).
Documented install remains `claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp`; MCP clients that support OAuth/DCR may complete auth. Use the public REST API for keyless HTTP probes.
Privacy notes
Tool arguments and responses (subnet queries, hotkeys, account lookups, search text) leave your machine and are processed by Metagraphed's hosted API at api.metagraph.sh.
Do not paste private keys, mnemonics, coldkey/hotkey secrets, or validator credentials into prompts or MCP tool arguments — this server is not a signing or wallet surface.
MCP client logs and chat transcripts may retain registry query results outside Metagraphed's own retention controls.
Prerequisites
An MCP client with Streamable-HTTP / remote HTTP MCP support (Claude Code, Cursor, or similar).
Optional: npm `@jsonbored/metagraphed` or PyPI `metagraphed` if you want the typed REST/GraphQL client instead of MCP.
Metagraphed (metagraph.sh) is a live operational and
integration registry for Bittensor subnets. It exposes a public
Streamable-HTTP MCP server at https://api.metagraph.sh/mcp so Claude can
discover subnets, check health and economics, read metagraph rows, look up
accounts/neurons, and pull API/schema/integration helpers.
Listed in the official MCP Registry as
io.github.JSONbored/metagraphed with a streamable-http remote. Typed
clients are also published as npm @jsonbored/metagraphed and PyPI
metagraphed. The backend is licensed AGPL-3.0.
This is not an official OpenTensor/Bittensor project, not a
wallet/validator/credential tool, and not an alpha/price dashboard.
Key capabilities
Documented MCP tools from the upstream README tool list (26 named tools):
search_subnets / list_subnets / find_subnets_by_capability — discover subnets by text or capability.
Upstream README prose may describe a broader tool surface beyond this named list; treat the list above as the documented primary MCP tool set.
Installation
Claude Code:
claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp
Cursor / other Streamable-HTTP clients: add an MCP server with URL
https://api.metagraph.sh/mcp and transport streamable-http (or the client's
equivalent remote HTTP MCP setting).
GitHub repo https://github.com/JSONbored/metagraphed returns HTTP 200; README documents the install command, Streamable-HTTP transport, AGPL-3.0 license, and the 26-tool list above.
Bare POST https://api.metagraph.sh/mcp without an OAuth bearer token returned HTTP 401 with WWW-Authenticate: Bearer and protected-resource metadata at https://api.metagraph.sh/.well-known/oauth-protected-resource/mcp. Documented client install remains claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp; use REST for keyless HTTP probes.
Duplicate Check
No existing content/mcp/ entry documents Metagraphed, metagraph.sh, or
api.metagraph.sh/mcp (repo search over content/ found no prior match).
Editorial Disclosure
Community listing by wondercreatemaster from Metagraphed's public README,
agent docs, MCP Registry metadata, npm/PyPI package pages, and live HTTP
checks performed on 2026-07-22. Not affiliated with OpenTensor.
Show that Metagraphed MCP Server for Claude is listed on HeyClaude. Paste this Markdown into your README — it renders the badge and links back to this page.
[](https://heyclau.de/entry/mcp/metagraphed-mcp)
How it compares
Metagraphed MCP Server for Claude side by side with 3 alternatives on trust, install, platform support, and disclosed safety notes — all from reviewed registry metadata.
1 trust signal differ across this comparison (Submitter).
Public Streamable-HTTP MCP server for the Metagraphed Bittensor subnet integration registry — discover subnets, check health and economics, read metagraph data, and look up accounts or API surfaces without wallets or signing.
✓Not an official OpenTensor/Bittensor project, not a wallet/validator/credential tool, and not an alpha/price dashboard — matching Metagraphed's own README framing.
Registry MCP tools are read-only by design: no transaction building and no extrinsic submission, so there is no wallet-signing risk from the documented MCP surface.
Returned subnet/API metadata can still influence generated configs or integration code — review outputs before pointing production traffic at a third-party subnet API.
As of 2026-07-22, bare unauthenticated POSTs to https://api.metagraph.sh/mcp returned HTTP 401 with a Bearer WWW-Authenticate challenge (OAuth protected-resource metadata published).
Documented install remains `claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp`; MCP clients that support OAuth/DCR may complete auth. Use the public REST API for keyless HTTP probes.
✓Remote MCP tools may trigger live API writes—confirm least-privilege credentials.
Treat Authorization headers and API keys as secrets; never commit them to repositories.
✓Remote MCP tools may trigger live API writes—confirm least-privilege credentials.
Treat Authorization headers and API keys as secrets; never commit them to repositories.
✓Remote MCP tools may trigger live API writes—confirm least-privilege credentials.
Treat Authorization headers and API keys as secrets; never commit them to repositories.
Privacy notes
✓Tool arguments and responses (subnet queries, hotkeys, account lookups, search text) leave your machine and are processed by Metagraphed's hosted API at api.metagraph.sh.
Do not paste private keys, mnemonics, coldkey/hotkey secrets, or validator credentials into prompts or MCP tool arguments — this server is not a signing or wallet surface.
MCP client logs and chat transcripts may retain registry query results outside Metagraphed's own retention controls.
✓Queries, tool payloads, and responses enter MCP client context and vendor infrastructure logs.
Review data residency and retention policies before connecting production accounts.
✓Queries, tool payloads, and responses enter MCP client context and vendor infrastructure logs.
Review data residency and retention policies before connecting production accounts.
✓Queries, tool payloads, and responses enter MCP client context and vendor infrastructure logs.
Review data residency and retention policies before connecting production accounts.
Prerequisites
An MCP client with Streamable-HTTP / remote HTTP MCP support (Claude Code, Cursor, or similar).
Optional: npm `@jsonbored/metagraphed` or PyPI `metagraphed` if you want the typed REST/GraphQL client instead of MCP.
MCP client with streamable HTTP transport support.
Vendor account or API credentials when registry metadata marks Authorization headers as required.
Security review of tool write scope before production use.
MCP client with streamable HTTP transport support.
Vendor account or API credentials when registry metadata marks Authorization headers as required.
Security review of tool write scope before production use.
MCP client with streamable HTTP transport support.
Vendor account or API credentials when registry metadata marks Authorization headers as required.
Security review of tool write scope before production use.
Install
claude mcp add --transport http metagraphed https://api.metagraph.sh/mcp
claude mcp add --transport http abmeter YOUR_ABMETER_MCP_REMOTE
claude mcp add --transport http lona-trading YOUR_LONA_MCP_REMOTE
claude mcp add --transport http agentic-news YOUR_AGENTIC_NEWS_MCP_REMOTE