Skip to main content
mcpSource-backed

Metagraphed MCP Server for Claude

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.

Review first review before installing

Open the source and read safety notes before installing.

Citation facts

Source-backed facts for citing this resource, derived directly from the registry — also available as plain text for AI assistants.

Source URLs
https://api.metagraph.sh/agent-workflows.md, https://github.com/JSONbored/metagraphed, https://metagraph.sh
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.
Author
JSONbored
Submitted by
wondercreatemaster
Claim status
unclaimed
Last verified
2026-07-22

Decision playbook

Review trust signals before you adopt

Signals are present but mixed. Use the checklist below to confirm the source and operational safety for your environment.

Compare context
Selected

0

Current score

63

Baseline

Delta

No baseline selected

No major trust-signal divergence detected in the current selection.

Source and provenance checks

Needs review

Confirm ownership and provenance before trusting install instructions.

  • Source link availableRequired

    Open the canonical repository and verify ownership.

    Done
  • Source provenance statusRequired

    Marked as source-backed.

    Done
  • Metadata reviewed

    No reviewed flag detected in metadata.

    Pending

Safety and privacy checks

Complete

Validate risk disclosures before installation or API wiring.

  • Safety notes presentRequired

    Review the listed safety guidance before running commands.

    Done
  • Privacy notes presentRequired

    Review data handling notes before connecting accounts or secrets.

    Done
  • Trust level risk gateRequired

    Trust level does not block evaluation.

    Done

Package and install checks

Needs review

Check package metadata and artifact integrity signals.

  • Install payload available

    Install or copy payload is available for review.

    Done
  • Package verification flag

    No package verification flag provided.

    Pending
  • Checksum metadata

    No checksum provided for downloaded artifact.

    Pending

Compare-driven decision checks

Needs review

Use compare context to validate trade-offs before adoption.

  • Compare tray has multiple entries

    Add at least one more entry to compare trust differences.

    Pending
  • Baseline comparison available

    No baseline peer selected yet.

    Pending
  • Diverging trust signals identified

    No major trust-signal divergence found.

    Pending

Setup at a glance

CLI install

Copy-ready — paste the snippet to get started.

5 minutes

Adoption plan

Balanced adoption plan

Current risk score 24/100. Use staged verification before broader rollout.

Risk 24

Pre-adoption checks

Validate source and review signals before any execution.

  • Confirm source provenanceRequired

    Source URL/provenance metadata is present.

    Done
  • Confirm metadata review state

    No review metadata found; increase manual validation.

    Pending
  • Verify install payload

    Install/config payload exists and can be inspected.

    Done

Security checks

Confirm safety, privacy, and package integrity signals.

  • Review safety notesRequired

    Safety notes are present.

    Done
  • Review privacy notesRequired

    Privacy notes are present.

    Done
  • Verify package integrity metadata

    No package verification/checksum metadata.

    Pending

Rollout

Adopt in controlled steps based on the selected plan.

  • Run in isolated sandbox firstRequired

    Use a constrained sandbox and observe behavior across multiple tasks.

    Pending
  • Roll out graduallyRequired

    Roll out to a small cohort before wider usage.

    Pending
  • Set monitoring and fallback

    Define rollback path and monitor errors after adoption.

    Pending

Evidence readiness

Evidence readiness matrix · balanced

Missing required evidence: Metadata review. Risk score 31.

Risk 31

Source provenance

Present

Source repository/provenance is listed.

Required in this preset

Metadata review

Missing

Review metadata is missing.

Required in this preset

Safety notes

Present

Safety notes are present.

Required in this preset

Privacy notes

Present

Privacy notes are present.

Optional in this preset

Package integrity

Missing

Package integrity metadata is missing.

Optional in this preset

Install payload

Present

Install payload is available.

Required in this preset

Required gaps: Metadata review

Decision timeline

Decision timeline · balanced

Blocking gaps: Check metadata review status. Risk 28.

Risk 28

triage

Confirm source provenanceRequired

Source/provenance metadata is available.

Done

triage

Check metadata review statusRequired

Review metadata is missing.

Pending

verify

Review safety notesRequired

Safety notes are available.

Done

verify

Review privacy notes

Privacy notes are available.

Done

verify

Validate package integrity metadata

Package integrity metadata is missing.

Pending

rollout

Verify install payload and commandsRequired

Install payload is available.

Done

Blockers: Check metadata review status

Prerequisite readiness

Prerequisite readiness

2 prerequisites to line up before setup.

0/2 ready
Install & runtime1Network & hosting15 minutes

Safety & privacy surface

Safety & privacy surface

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.

Schema details

Install type
cli
Troubleshooting
No
Source repository stats
Scope
Source repo
Skill and platform metadata
Retrieval sources
https://github.com/JSONbored/metagraphedhttps://metagraph.shhttps://api.metagraph.sh/agent.mdhttps://api.metagraph.sh/agent-workflows.mdhttps://registry.modelcontextprotocol.iohttps://www.npmjs.com/package/@jsonbored/metagraphedhttps://pypi.org/project/metagraphed/https://code.claude.com/docs/en/mcp
Collection metadata
Estimated setup
5 minutes
Difficulty
beginner
Tool listing metadata
Full copyable content
{
  "mcpServers": {
    "metagraphed": {
      "url": "https://api.metagraph.sh/mcp",
      "type": "http"
    }
  }
}

About this resource

Overview

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.
  • get_subnet / get_subnet_health / get_subnet_economics / get_subnet_trajectory / get_subnet_metagraph — per-subnet detail, health, economics, trajectory, and metagraph.
  • list_subnet_validators / get_neuron — validator and neuron lookups.
  • get_account / get_account_events / get_account_subnets — account activity across the network.
  • list_subnet_apis / get_api_schema / get_fixture / get_agent_catalog / get_best_rpc_endpoint — API surface, schema, fixtures, catalog, and RPC hints.
  • registry_summary / list_enrichment_targets / find_subnet_opportunities — registry-wide summaries and opportunity boards.
  • semantic_search / ask / find_subnet_for_task / how_do_i_call / verify_integration — guided discovery and integration-verification helpers.

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

JSON config shape used by many HTTP MCP clients:

{
  "mcpServers": {
    "metagraphed": {
      "url": "https://api.metagraph.sh/mcp",
      "type": "http"
    }
  }
}

Source Verification Notes

Verified on 2026-07-22:

  • 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.
  • Website https://metagraph.sh and API origin https://api.metagraph.sh return HTTP 200.
  • Public REST probe GET https://api.metagraph.sh/api/v1/subnets?limit=1 returns HTTP 200 with a JSON { ok, data, … } envelope.
  • Agent docs https://api.metagraph.sh/agent.md and https://api.metagraph.sh/agent-workflows.md return HTTP 200. https://api.metagraph.sh/llms.txt returned HTTP 404 at verification time (README still links it) — prefer agent.md / agent-workflows.md.
  • Official MCP Registry search for metagraphed returns io.github.JSONbored/metagraphed with remote { type: "streamable-http", url: "https://api.metagraph.sh/mcp" }.
  • npm @jsonbored/metagraphed resolves on registry.npmjs.org (latest observed: 0.12.8).
  • PyPI metagraphed resolves (latest observed: 0.4.1).
  • 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.

Source citations

Add this badge to your README

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.

Listed on HeyClaude
[![Listed on HeyClaude](https://heyclau.de/badge/mcp/metagraphed-mcp.svg)](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).

Field

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.

Open dossier

ABMeter MCP exposes experimentation and analytics tooling over streamable HTTP for MCP clients.

Open dossier

Lona trading MCP provides AI-assisted strategy development, backtesting, market data, and portfolio analysis.

Open dossier

Agentic News MCP delivers news discovery and agentic news workflows over streamable HTTP.

Open dossier
Next steps
Trust
Review statusNot reviewedNot reviewedNot reviewedNot reviewed
Package trustPackage not verifiedPackage not verifiedPackage not verifiedPackage not verified
Source provenanceSubmission linkedSource submissionSubmission linkedSource submissionSubmission linkedSource submissionSubmission linkedSource submission
SubmitterDifferswondercreatemasterkiannidevkiannidevkiannidev
Install riskReview firstReview firstReview firstReview first
Notes Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓ Safety ✓ Privacy ✓
Brand
Categorymcpmcpmcpmcp
SourceSource-backedSource-backedSource-backedSource-backed
AuthorJSONboredABMeterLonaAgentic News
Added2026-07-222026-06-172026-06-172026-06-17
Platforms
Harness
Source repo
Safety notesNot 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 notesTool 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
Config
{
  "mcpServers": {
    "metagraphed": {
      "url": "https://api.metagraph.sh/mcp",
      "type": "http"
    }
  }
}
{
  "mcpServers": {
    "abmeter": {
      "url": "https://YOUR_ABMETER_MCP_REMOTE",
      "type": "http"

    }
  }
}
{
  "mcpServers": {
    "agency": {
      "url": "https://YOUR_LONA_MCP_REMOTE",
      "type": "http"

    }
  }
}
{
  "mcpServers": {
    "agentic": {
      "url": "https://YOUR_AGENTIC_NEWS_MCP_REMOTE",
      "type": "http"

    }
  }
}
Citations
ClaimUnclaimedUnclaimedUnclaimedUnclaimed
Open 4 picks in the interactive comparison tool

Related guides

Signals

Loading live community signals…

More like this, weekly

A short, calm digest of reviewed Claude resources. Unsubscribe any time.