Should my agent depend on the MCP server ai.shumi/mcp?

Verdict: allow — mid-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

mcp

ai.shumi/mcp

Crypto market intelligence: prices, funding rates, narratives, regime, and delta-neutral research.

— the operator's own registry description reported

Publisher ai.shumi · first seen 2026-08-12 · endpoint https://mcp.shumi.ai/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-solo — safe to depend on

Cluster mid-solo · distinctiveness 0.214 (typical). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency204 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools31

vs populationmid

capabilities2

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_f7546be1ea56081161beaaf3 · ed25519 · key rs-rcpt-2026-08 — this rating is tamper-evident; an agent gets the full signature from check_server and can verify it against the published key.

Tools last seen

ask_shumi get_basket get_category get_coin_historical get_coin_risk get_coin_sentiment get_funding_alerts get_funding_momentum get_futures_signals get_global_market get_holders get_market_crossing get_market_health get_market_sentiment get_narrative get_pair_suggestions get_prices get_regime get_rwa_asset get_signal get_signal_quality get_transcripts get_wallets list_categories list_narratives list_rwa_assets lookup_coin resolve_coin scan_coins scan_trends search_web

Harness readiness observed

Can an agent's harness pick this tool and call it correctly? Graded on the three things an agent reads — name, description, typed parameters. Band A — an agent can pick and call these reliably.

legibility check	tools passing	ok
name is clear & specific	31/31	✓
has a description	31/31	✓
description is substantive	31/31	✓
parameters are typed	31/31	✓
parameters are described	31/31	✓

31 of 31 tools graded · 31 with a captured input schema. RS-008, Tier-1 — no domain knowledge, applies to any tool. “Alive” is not the same as “usable”.

Truth checks observed

Not in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.1.3

server version shumi

Capabilities: resources tools

Drift

No confirmed drift on record. Baseline set 2026-08-14; changes appear here after human review.

History observed

Every probe we made, oldest → newest (1 shown, 2026-08-14 → 2026-08-14). Green answered · amber answered-but-walled · red no useful answer. A gap in our cadence is a gap in coverage, not evidence about the server.

changelog (1 events)

date	type	what changed
2026-08-14	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:57:39Z	ok_tools	200	204	2025-06-18

Watch or embed this verdict

Operators: put the live verdict in your README — it updates with every census, links back here, and is a dated observation, never a warranty:

[![Robin Saige verdict](https://robinsaige.com/badge/ai.shumi/mcp.svg)](https://robinsaige.com/s/ai.shumi/mcp)

Depend on it? Subscribe to its change feed — outcome changes and confirmed drift, no account needed. Building on it? The full dossier as JSON — verdict, rating, truth checks, history — stable enough to gate CI on.

← overview