Koskamo

metagraphed MCP

A Model Context Protocol server that allows AI agents to query the metagraphed operational registry for Bittensor subnets. It provides tools for discovering subnets, checking their health status, retrieving API schemas, and accessing integration documentation via bounded discovery and invocation bridges.

Visit Metagraphed

Endpoint and access

OAuth sign-in: the first time you connect, your client opens the vendor's own authorization prompt in a browser.

metagraphed MCP logo, by MetagraphedCommunity listingStreamable HTTPOAuth sign-inEndpoint checked 2026-11-06Published by Metagraphed
MCP endpoint (Streamable HTTP)
https://api.metagraph.sh/mcp
Vendor documentation

Checks and signals

Each line is separate evidence, not a trust score.

  • Passed Endpoint answered the live check ·
  • Availability 1 of 1 checks passed in 30 days

What you can do with it

  • Search for Bittensor subnets by name or capability
  • Check the live health and uptime of subnet APIs
  • Retrieve API schemas and documentation for subnets
  • Discover callable services and their endpoints

Source and maintenance

Community listingRegistry 1.3.0
mcp-registry: io.github.JSONbored/metagraphed@1.3.0Source repositoryProject website
Maintenance checked

Tools

Reported by the attributed source; not independently observed by Koskamo.

No tool definitions available.

90-day uptime

A lightweight connection check about every six hours, sampled on hosts with many listings. It shows the server answered, not that its tools work.

Too few checks for a percentage yet (2 of 2 answered).

  1. 2026-11-06: 1 of 1 checks answered
  2. 2026-11-07: 1 of 1 checks answered

30-day availability

Aggregated from read-only remote checks; this is not a tool-execution or security guarantee.

Successful checks
1 of 1 (100%)
Average latency
613 ms
95th percentile latency
613 ms

Maintenance history

Public check and source-refresh events. Editorial and ownership records remain private.

  • · probe · passed · 613 ms · metadata changed · refuses unauthenticated initialize (HTTP 401)

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers the remote server. Use --scope project to write .mcp.json for the repo.
Claude Code configuration
claude mcp add --transport http metagraphed-mcp https://api.metagraph.sh/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).
Codex configuration
codex mcp add metagraphed-mcp --url https://api.metagraph.sh/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable metagraphed-mcp in your MCP settings.
Cursor configuration
{
  "mcpServers": {
    "metagraphed-mcp": {
      "url": "https://api.metagraph.sh/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure).
Cline configuration
{
  "mcpServers": {
    "metagraphed-mcp": {
      "type": "streamableHttp",
      "url": "https://api.metagraph.sh/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start metagraphed-mcp and inspect its tools.
VS Code configuration
{
  "servers": {
    "metagraphed-mcp": {
      "type": "http",
      "url": "https://api.metagraph.sh/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.
Gemini CLI configuration
gemini mcp add --transport http metagraphed-mcp https://api.metagraph.sh/mcp

Claude Desktop

Open Claude Settings > Connectors > Add custom connector, enter this server URL and enable it for the conversation. This is a manual remote-connector handoff, not a desktop JSON configuration.
Claude Desktop configuration
https://api.metagraph.sh/mcp

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.
Windsurf configuration
{
  "mcpServers": {
    "metagraphed-mcp": {
      "serverUrl": "https://api.metagraph.sh/mcp"
    }
  }
}

Let your agent find its tools

Find servers like metagraphed MCP from your agent. Add Koskamo once to search the index for endpoints, access requirements, and client setup. Public discovery needs no key.

Connect Koskamo Explore workflows
See all 8,807