Robin Saige we check the tools AI agents call

CoinCryptoRank MCP

io.github.qqdd27/coincryptorank-mcp

Real-time crypto market data, funding rates, arbitrage and trading tools from 60+ exchanges.

— the operator's own registry description reported

Publisher io.github.qqdd27 · first seen 2026-09-01 · endpoint https://coincryptorank.com/api/v1/mcp

allow
verdict
stale-rich-slow-solo
cluster
ok_tools
answers
35
tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V2 has a twin ◐
allow — because answers ●, 35 tools legible (band A) ●, no confirmed drift in 1 probes ●; not yet checked: truth (0 runs)

Cluster stale-rich-slow-solo · distinctiveness 0.585 (moderate). Every figure is a percentile or class within the 15,472-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency632 ms
vs populationslow
protocolbehind
authopen
Can it be used? Q4 · observed
tools35
vs populationhigh
capabilities1
harnessA
Did it hold when checked? Q3–Q4 · derived
identitysolo
servers on its host1
verifiabilityunassessed
duplicate inventoryno
drift events0
answers trueno primary

🔏 Signed receipt rr_0b3058b430c1110f2aed42cc · 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.

Q1Does it answer?alive & usable — 1 probes ●evidence ↓
Q2What is it?retrieval-public ● evidence ↓
Q3Can it be checked?V2 has a twin ◐evidence ↓
Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?stale-rich-slow-solo · 1 on its host (context, not verdict) ◐evidence ↓

● observed · ◐ derived · ○ reported — the verdict synthesizes Q1–Q4; Q5 is context. Methodology →

History observed

Every probe we made, oldest → newest (1 shown, 2026-09-06 → 2026-09-06). 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)
datetypewhat changed
2026-09-06outcomefirst probe: ok_tools

What kind of tools these are derived

Verification only means something relative to a tool's NATURE — an email-sender has no "true answer", a generator has no answer key. Classification evidence: classified from tool names/descriptions/annotations WE OBSERVED. What checking applies to each kind (the full methodology →):

naturetoolsmeaning what checking applies
retrieval-public18serves public factstruth-checkable against a public source — the V-ladder applies in full
action11changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
unclassified6not classifiable from its textTier-1 only until its tools describe themselves

Tools last seen observed

adjust_hedge agent_chat agent_decisions agent_status agent_trigger analyze_pair_liquidity backtest_basis_strategy close_hedged_position close_position get_agent_events get_basis_history get_basis_regime get_basis_signal get_exchange_skills get_funding_arbitrage get_funding_rates get_funding_schedule get_klines get_news get_open_orders get_orderbook get_perp_arbitrage get_portfolio get_positions get_spot_arbitrage get_threat_level get_tickers hedge_status list_agents list_hedge_positions open_hedged_position place_order set_hedge_protection set_sl_tp square_post

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 checktools passingok
name is clear & specific35/35
has a description35/35
description is substantive35/35
parameters are typed35/35
parameters are described9/359/35

35 of 35 tools graded · 35 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-03-26
protocol version
session model
1.0.0
server version coincryptorank

Capabilities: tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-09-06T06:17:01Zok_tools2006322025-03-26

Watch or embed this verdict

verdict badge

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/io.github.qqdd27/coincryptorank-mcp.svg)](https://robinsaige.com/s/io.github.qqdd27/coincryptorank-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

Operator of this server? Everything we hold about it is on this page — free, no account, for anyone. Wrong attribution, stale probe, misclassification? Dispute this record →