metagraphed — Bittensor subnet operational registry
REMOTE · API.METAGRAPH.SH · SCANNED SEP 21
Live operational + integration registry for Bittensor subnets: APIs, schemas, health.
Available components
Recent critical change
Authorization (2 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security66
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (write_subnet_surface). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 96879 tokens (~136/item across 708 items; 243 tools + 465 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- Stability check failed: schema churn in the 30 days we've observed: 0 tool removals, 1 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety83
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 1 of 3 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "get_chain_transfer_pairs" implies "transfer" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Partial
- An AI judge read all 245 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the metagraphed — Bittensor subnet operational registry MCP server?
metagraphed — Bittensor subnet operational registry is a hosted endpoint at https://api.metagraph.sh/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.metagraph.sh
claude mcp add --transport http jsonbored-metagraphed 'https://api.metagraph.sh/mcp'
{
"mcpServers": {
"jsonbored-metagraphed": {
"url": "https://api.metagraph.sh/mcp"
}
}
} {
"servers": {
"jsonbored-metagraphed": {
"type": "http",
"url": "https://api.metagraph.sh/mcp"
}
}
} [mcp_servers.jsonbored-metagraphed] url = "https://api.metagraph.sh/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"jsonbored-metagraphed": {
"type": "remote",
"url": "https://api.metagraph.sh/mcp",
"enabled": true
}
}
} openclaw mcp add jsonbored-metagraphed --url 'https://api.metagraph.sh/mcp' --transport streamable-http
mcp_servers:
jsonbored-metagraphed:
url: "https://api.metagraph.sh/mcp" {
"McpServers": {
"jsonbored-metagraphed": {
"Transport": "http",
"Url": "https://api.metagraph.sh/mcp"
}
}
} assistant mcp add jsonbored-metagraphed -t streamable-http -u 'https://api.metagraph.sh/mcp'
{
"mcpServers": {
"jsonbored-metagraphed": {
"type": "http",
"url": "https://api.metagraph.sh/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 20 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 19 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 18 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 17 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 16 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 15 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
- 14 Sept 26 0
- This server's schema is too large to store in full, so we cannot compare its tools day to day functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://api.metagraph.sh/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=metagraph.sh | CN=WE1,O=Google Trust Services,C=US | 8 Aug 2026 | 6 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 2b67e5cc8b0e91ad0eefcb0e8c97b14a |
| SANs: metagraph.sh, api.metagraph.sh, *.api.metagraph.sh | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of api.metagraph.sh. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| sh. | present | 55297 | 8 | Verified |
| metagraph.sh. | present | 2371 | 13 | Verified |
| api.metagraph.sh. | Verified address RRset verified with the apex keys |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.metagraph.sh/mcp | Verified | 200 | |
| http (plaintext) | http://api.metagraph.sh/mcp | HTTPS enforced | 301 | https://api.metagraph.sh/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
write_subnet_surface ~788
No description provided.
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| content_type | string | – | – |
| context | string | yes | – |
| conversation_id | string | – | – |
| credential | – | – | – |
| method | string | yes | – |
| path | string | yes | – |
| query | object | – | – |
| surface_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| body | – | – | – |
| content_type | – | – | – |
| credential_deprecation | string | – | – |
| credential_source | string | – | – |
| degraded | object | – | – |
| latency_ms | – | – | – |
| parse_error | – | – | – |
| status_code | integer | yes | – |
| surface_id | string | yes | – |
| truncated | boolean | yes | – |
| url | string | yes | – |
No examples provided.
What is the metagraphed — Bittensor subnet operational registry MCP server?
metagraphed — Bittensor subnet operational registry is an MCP server listed in the public MCP registry as io.github.JSONbored/metagraphed. Live operational + integration registry for Bittensor subnets: APIs, schemas, health. This page covers its hosted endpoint (https://api.metagraph.sh/mcp).
Is the metagraphed — Bittensor subnet operational registry MCP server safe to use?
metagraphed — Bittensor subnet operational registry scores 83 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
Does the metagraphed — Bittensor subnet operational registry MCP server require authentication?
No. We connected to metagraphed — Bittensor subnet operational registry without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the metagraphed — Bittensor subnet operational registry MCP server still maintained?
metagraphed — Bittensor subnet operational registry is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.