Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Cipher — Bittensor Subnet Screener

REMOTE · MCP.BROBOTAPP.COM

Real-time Bittensor subnet screener: prices, momentum, flow, whale signals, TAO forecast via MCP.

+4 this week 61 Trust /100

Last scanned (14 hours ago)

Scores higher than 45% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Crypto and Web3

Trust breakdown (7 categories)

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 Security46
Transport & Reachability100
Schema Quality & AI Usability63
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 482 tokens (~60/item across 8 items; 8 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (11)

  • TLS certificate
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (2)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

  • 19 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

  • 17 Nov 26 +41
    • Injection markers: unverified → pass ▲ security
    • Transport: fail → pass ▲ security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 8 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Endpoint reachability: not serving MCP → reachable ▲ functional
    • Tool coverage: unverified → 100 ▲ functional
    • Stability: unverified → 0.23 ▲ functional
    • MCP protocol: unverified → pass ▲ functional
  • 16 Nov 26 −40
    • Endpoint reachability: reachable → not serving MCP ▼ security
    • Tool safety: pass → unverified ▼ security
    • Stability: 0.17 → unverified ▼ security
    • Transport: pass → fail ▼ security
    • Authorization: Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. security
    • Capabilities: pass → unverified ▼ functional
    • Tool coverage: 100 → unverified ▼ functional
    • First check of Schema quality: unverified functional
  • 15 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.

  • 13 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

  • 11 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 55

    First indexed and scored.

Diagnostics

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 Nov 2026 · Probed https://mcp.brobotapp.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=brobotapp.com CN=YE2,O=Let's Encrypt,C=US 27 Sept 2026 26 Dec 2026 ECDSA 256 ECDSA-SHA384 57f4945fb37d4a35b3c72b4012cb4499d25
SANs: *.brobotapp.com, brobotapp.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.brobotapp.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
brobotapp.com. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
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

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.brobotapp.com/mcp Verified 200
http (plaintext) http://mcp.brobotapp.com/mcp Inconclusive 406
MCP tools · 8 exposed · ~414 tokens

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 →

Tool Tokens
alphagap_flow ~63

AlphaGap momentum snapshot: flow_score (momentum+whale+volume), whale_signal ('accumulating'/'distributing'), whale_ratio, composite, dev, eval scores. High flow = strong momentum.

NameTypeReqDescription
netuidintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

screener_top ~61

Top subnets by Cipher heat score. n up to 50. category filters by tag (e.g. 'inference', 'training', 'agents', 'finance', 'tools').

NameTypeReqDescription
category–––
ninteger––
NameTypeReqDescription
resultarrayyes–

No examples provided.

search_subnets ~35

Search subnets by name substring. limit max 25.

NameTypeReqDescription
limitinteger––
qstringyes–
NameTypeReqDescription
resultarrayyes–

No examples provided.

subnet_bars ~41

Recent OHLC bars for a subnet (newest last). limit max 500.

NameTypeReqDescription
limitinteger––
netuidintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

subnet_detail ~49

Full detail for one subnet: price, 1d/1w/1m change, volume, liquidity, identity tags, research conviction, watchlist.

NameTypeReqDescription
netuidintegeryes–

Structured output declared, but exposes no named fields.

No examples provided.

tao_forecast ~43

7-day TAO price forecast (median + p10/p90 bands) from the local Ephemeris-clone forecaster (Chronos-2).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

tao_price ~32

Current TAO USD price + 24h change (from the screener's tao_price_usd table).

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

trader_state ~90

Live AA subnet-trader summary (read-only): current equity + 24h trend, circuit-breaker status, position count, and recent-decision count. A free visibility summary — the FULL stream (positions, decisions, per-subnet detail) is the paid x402 endpoint /api/premium/trader-stream. NEVER writes or controls the trader — a data window.

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the Cipher — Bittensor Subnet Screener MCP server?

Cipher — Bittensor Subnet Screener is a hosted endpoint at https://mcp.brobotapp.com/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 · mcp.brobotapp.com

# add to Claude Code
claude mcp add --transport http com-brobotapp-cipher 'https://mcp.brobotapp.com/mcp'
Common questions

What is the Cipher — Bittensor Subnet Screener MCP server?

Cipher — Bittensor Subnet Screener is an MCP server listed in the public MCP registry as com.brobotapp/cipher. Real-time Bittensor subnet screener: prices, momentum, flow, whale signals, TAO forecast via MCP. This page covers its hosted endpoint (https://mcp.brobotapp.com/mcp).

Is the Cipher — Bittensor Subnet Screener MCP server safe to use?

Cipher — Bittensor Subnet Screener scores 61 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.

What tools does the Cipher — Bittensor Subnet Screener MCP server expose?

Cipher — Bittensor Subnet Screener exposes 8 tools: screener_top, subnet_detail, subnet_bars, alphagap_flow, search_subnets, and 3 more. Their descriptions and schemas cost roughly 414 tokens of context every time the server is loaded.

Does the Cipher — Bittensor Subnet Screener MCP server require authentication?

No. We connected to Cipher — Bittensor Subnet Screener without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Cipher — Bittensor Subnet Screener MCP server still maintained?

Cipher — Bittensor Subnet Screener is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the Cipher — Bittensor Subnet Screener MCP server?

VerifyMCP ran 11 checks on Cipher — Bittensor Subnet Screener, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about Cipher — Bittensor Subnet Screener: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.