io.github.JSONbored/metagraphed

MCPcommunitylive
v1.3.0io.github.JSONboredUnknownUpdated 3mo agoGitHub

Live operational + integration registry for Bittensor subnets: APIs, schemas, health.

Endpoint healthlive
checked 2 days ago · 2577ms
100% of the last 5 checks reached this endpoint
Works in
ClaudeCursorCopilotChatGPTGemini

Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.

Automatically indexed from public sources. Not yet verified by the developer on Forge.Claim this listing →
3mo agoLast update
Package
Authorio.github.JSONbored
LicenseUnknown
Version1.3.0
Sourcemcp-registry
Trust Status
B
60/100Good
✓Listed in Forge index+10/10
—Publisher identity verified+0/30
→ Publisher: run `forge publish` from the repo to claim ownership
—Domain verification+0/10
→ Not currently available for this listing type — the domain-verification check only runs for npm-backed packages today, so this row cannot be earned here yet regardless of what's hosted at the domain.
✓Prompt-injection scan · clean+30/30
✓Obfuscation / exfil scan · clean+20/20
Paste into Claude Code, Cursor, or any AI assistant to fix all gaps
StatusCommunity-indexed
PublisherUnverified
SignatureUnsigned
Domain—
Provenance—
DependenciesNot audited
Tool surface15 tools · none privileged
Security scan✓ CleanvHEAD · 3mo agoHow well does this scan work?
EvalsNone
IndexedJun 14, 2026

Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.

Tools

15 tools · none privileged
Statically extracted from the published packagevHEAD · 3mo ago

Read out of the source npm actually ships, at scan time. The package was never executed. Tools registered dynamically at runtime, or hidden inside bundled or minified code, can be missed — so this is a floor on the tool surface, not a complete census of it.

metagraphedNo description published

This tool published no description. Forge does not invent one.

search_subnetsNo description published

This tool published no description. Forge does not invent one.

find_subnets_by_capabilityNo description published

This tool published no description. Forge does not invent one.

get_subnetNo description published

This tool published no description. Forge does not invent one.

get_subnet_healthNo description published

This tool published no description. Forge does not invent one.

list_subnet_apisNo description published

This tool published no description. Forge does not invent one.

get_api_schemaNo description published

This tool published no description. Forge does not invent one.

get_fixtureNo description published

This tool published no description. Forge does not invent one.

get_agent_catalogNo description published

This tool published no description. Forge does not invent one.

get_best_rpc_endpointNo description published

This tool published no description. Forge does not invent one.

registry_summaryNo description published

This tool published no description. Forge does not invent one.

semantic_searchNo description published

This tool published no description. Forge does not invent one.

askNo description published

This tool published no description. Forge does not invent one.

find_subnet_for_taskNo description published

This tool published no description. Forge does not invent one.

how_do_i_callNo description published

This tool published no description. Forge does not invent one.

0 of 15 tools published a description.

Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.

About

Live operational + integration registry for Bittensor subnets: APIs, schemas, health.

Keywords
mcp
Alternatives
Comparing tool surfaces…

No dependency coverage

This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.