Live operational + integration registry for Bittensor subnets: APIs, schemas, health.
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.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
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 publishedThis tool published no description. Forge does not invent one.
search_subnetsNo description publishedThis tool published no description. Forge does not invent one.
find_subnets_by_capabilityNo description publishedThis tool published no description. Forge does not invent one.
get_subnetNo description publishedThis tool published no description. Forge does not invent one.
get_subnet_healthNo description publishedThis tool published no description. Forge does not invent one.
list_subnet_apisNo description publishedThis tool published no description. Forge does not invent one.
get_api_schemaNo description publishedThis tool published no description. Forge does not invent one.
get_fixtureNo description publishedThis tool published no description. Forge does not invent one.
get_agent_catalogNo description publishedThis tool published no description. Forge does not invent one.
get_best_rpc_endpointNo description publishedThis tool published no description. Forge does not invent one.
registry_summaryNo description publishedThis tool published no description. Forge does not invent one.
semantic_searchNo description publishedThis tool published no description. Forge does not invent one.
askNo description publishedThis tool published no description. Forge does not invent one.
find_subnet_for_taskNo description publishedThis tool published no description. Forge does not invent one.
how_do_i_callNo description publishedThis 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.
Live operational + integration registry for Bittensor subnets: APIs, schemas, health.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
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.