# Reported issues for metagraphed — Bittensor subnet operational registry Pod holds 16 of 57 problems reported by people outside the maintainer team. Issues filed by the project's own owners, members and collaborators are excluded entirely — a maintainer's release checklist is not a warning to a prospective user. Back to [metagraphed — Bittensor subnet operational registry](/mcp/metagraphed-bittensor-subnet-operational-registry). ## Most discussed ### Enrich SN93 Bitcast — add SSE stream Part of #427. **Subnet 93 — Bitcast** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN93's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — veri [Read the thread](https://github.com/JSONbored/metagraphed/issues/7624) · 2026-07-22 · closed · outside contributor · 4 comments ### Enrich SN99 Leoma — add SSE stream Part of #427. **Subnet 99 — Leoma** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN99's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — verify [Read the thread](https://github.com/JSONbored/metagraphed/issues/7622) · 2026-07-22 · closed · outside contributor · 3 comments ### Enrich SN103 Djinn — add OpenAPI/Swagger spec + SSE stream Part of #427. **Subnet 103 — Djinn** is missing from the registry: **OpenAPI/Swagger spec, SSE stream**. Research whether the subnet exposes these, find the real public link(s), and submit them. ### Find it Search for the subnet's official OpenAPI/Swagger spec, SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN103's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain i [Read the thread](https://github.com/JSONbored/metagraphed/issues/7619) · 2026-07-22 · closed · outside contributor · 3 comments ### Enrich SN56 Gradients — add SSE stream Part of #427. **Subnet 56 — Gradients** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN56's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — ve [Read the thread](https://github.com/JSONbored/metagraphed/issues/7617) · 2026-07-22 · closed · outside contributor · 3 comments ### Enrich SN51 lium\.io — add SSE stream Part of #427. **Subnet 51 — lium\.io** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN51's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — ver [Read the thread](https://github.com/JSONbored/metagraphed/issues/7615) · 2026-07-22 · closed · outside contributor · 2 comments ### Enrich SN94 Bitsota — add SSE stream Part of #427. **Subnet 94 — Bitsota** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN94's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — veri [Read the thread](https://github.com/JSONbored/metagraphed/issues/7614) · 2026-07-22 · closed · outside contributor · 3 comments ### Enrich SN74 Gittensor — add SSE stream Part of #427. **Subnet 74 — Gittensor** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN74's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — ve [Read the thread](https://github.com/JSONbored/metagraphed/issues/7610) · 2026-07-22 · closed · outside contributor · 3 comments ### [Security todo] Enable prevent_self_review on pypi-production environment ## Security todo The pypi-production environment lists JSONbored as its sole required reviewer with prevent_self_review: false, meaning the same actor can request and approve their own PyPI publish. Enforce prevent_self_review and ideally add a second reviewer so a single compromised account cannot self-approve a malicious release. ## Context - Severity: High - Category: publish_release_integrity - Confidence: Observ [Read the thread](https://github.com/JSONbored/metagraphed/issues/3082) · 2026-07-04 · closed · external user · 2 comments ## Most recent ### Permission to add MCP Queen operational badge for io.github.JSONbored/metagraphed Hi — MCP Queen’s current public probe for **io.github.JSONbored/metagraphed** reports an operational **A (94/100)** with **220 discovered tools**: https://mcpqueen.com/s/io.github.JSONbored/metagraphed We are asking before making any repository change. If you would like the live badge in your README, reply **PR welcome** and we will submit a one-line pull request in your existing badge area. We will not open a PR without explicit permission. Proposed line: `[![MCP Queen operational grade](htt [Read the thread](https://github.com/JSONbored/metagraphed/issues/9683) · 2026-08-06 · closed · external user · 1 comment ### Enrich SN78 Vocence — add SSE stream Part of #427. **Subnet 78 — Vocence** is missing from the registry: **SSE stream**. Research whether the subnet exposes this, find the real public link(s), and submit them. ### Find it Search for the subnet's official SSE stream (project site / GitHub / docs / Bittensor). Confirm each link is real, public, no-auth, and genuinely SN78's — cross-reference the subnet name + Bittensor. ⚠️ Many subnets simply don't expose a public API yet, and on-chain identity links are often **stale/dead** — veri [Read the thread](https://github.com/JSONbored/metagraphed/issues/8673) · 2026-07-29 · closed · outside contributor · 1 comment ### fix(mcp): get_validator_nominators would violate its own outputSchema once wired to Postgres ## Context Auditing the MCP tool surface for the \`tryPostgresTier(...) ?? builder(...)\` data-shape pattern (the same class of bug flagged during #5277's review): \`workers/data-api.mjs\`'s \`/api/v1/validators/{hotkey}/nominators\` route wraps its response as \`json({ data: buildValidatorNominators(...), generatedAt })\` — a \`{data, generatedAt}\` envelope, not the flat nominators object. \`get_validator_nominators\`'s own documented \`outputSchema\` (in \`TOOL_OUTPUT_SCHEMAS\`) requires to [Read the thread](https://github.com/JSONbored/metagraphed/issues/5285) · 2026-07-14 · closed · outside contributor · 1 comment ### [Security todo] Require status checks to pass before merging to main ## Security todo Branch protection settings could not be verified. Confirm that the validate.yml jobs (test, checks, python) are configured as required status checks in branch protection so malicious or broken code cannot merge around CI. ## Context - Severity: Medium - Category: branch_merge_protection - Confidence: Unverified - Threat: compromised contributor / ci_cd compromise ## Evidence settings.branch_protect [Read the thread](https://github.com/JSONbored/metagraphed/issues/3087) · 2026-07-04 · closed · external user · 1 comment ### [Security todo] Require pull-request reviews and dismiss stale reviews on main ## Security todo Branch protection settings could not be verified (403 Forbidden). A maintainer should confirm in Settings -> Branches -> main that 'Require a pull request before merging' is enabled with at least 1-2 approving reviews, 'Dismiss stale PR approvals when new commits are pushed' is on, and 'Require review from CODEOWNERS' is checked. Without this, a compromised contributor can merge malicious code directly [Read the thread](https://github.com/JSONbored/metagraphed/issues/3079) · 2026-07-04 · closed · external user · 1 comment ### feat(mcp): add get_economics_trends tool (REST parity for GET /api/v1/economics/trends) ## Problem `GET /api/v1/economics/trends` (#1307) exposes the network-wide economics time series — per-UTC-day rollups of total stake, alpha price (weighted + median), validator/miner counts, and mean emission share — but there is no matching MCP tool. ## Proposed solution Add **`get_economics_trends`** mirroring the REST route: | REST | MCP | | --- | --- | | `GET /api/v1/economics/trends` | `get_economics_trends` | ### Parameters | param | values | default | | --- | --- | --- | | `window` [Read the thread](https://github.com/JSONbored/metagraphed/issues/2425) · 2026-06-30 · closed · outside contributor · 0 comments ### feat(mcp): add get_chain_fees tool (REST parity for GET /api/v1/chain/fees) ## Problem `GET /api/v1/chain/fees` (#1988) exposes fee/tip market analytics — a per-UTC-day fee series plus a windowed top-fee-payer list — but there is no matching MCP tool. Agents using the metagraphed MCP surface cannot query chain fee economics without falling back to raw REST. ## Proposed solution Add **`get_chain_fees`** to the MCP server, mirroring the REST route: | REST | MCP | | --- | --- | | `GET /api/v1/chain/fees` | `get_chain_fees` | ### Parameters (parity) | param | REST | M [Read the thread](https://github.com/JSONbored/metagraphed/issues/2423) · 2026-06-30 · closed · outside contributor · 0 comments ### Add module-scoped chain calls filter ## Summary Add an optional `call_module` filter to the chain calls analytics endpoint so explorer clients can drill into the busiest functions within a selected pallet. ## Scope - Extend `GET /api/v1/chain/calls` with `?call_module=`. - Keep the response shape stable while scoping `total_extrinsics` and `share` to the selected module when the filter is present. - Update the public contract artifacts and add focused route/loader coverage. [Read the thread](https://github.com/JSONbored/metagraphed/issues/2419) · 2026-06-30 · closed · outside contributor · 0 comments The remaining reports are on [the project's issue tracker](https://github.com/JSONbored/metagraphed/issues).