Should my agent depend on the MCP server io.github.CoinRithm/mcp-trading?

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

CoinRithm Agent Trading

io.github.CoinRithm/mcp-trading

Keyless prediction-market data across 12 venues plus paper-trading of crypto spot, futures, and PM.

— the operator's own registry description reported

Publisher io.github.CoinRithm · first seen 2026-08-12 · endpoint https://mcp.coinrithm.com/mcp

allow

verdict

rich-slow-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-slow-solo — safe to depend on

Cluster rich-slow-solo · distinctiveness 0.501 (moderate). 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

latency437 ms

vs populationslow

protocolcurrent

authopen

Use — can it use it?

tools37

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

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

cancel_spot_order close_futures_position discover_pm_markets export_agent_ledger export_run_evidence futures_quote get_agent_ledger get_arena_agent get_arena_leaderboard get_candles get_equity_curve get_market_context get_my_trades get_performance get_portfolio get_positions get_wallet list_open_orders open_futures_position open_pm_position place_spot_order pm_data_calibration pm_data_canonical pm_data_disagreements pm_data_event pm_data_events pm_data_overview pm_data_sources pm_data_sources_health pm_data_volume_history pm_data_whales pm_quote report_pm_opportunity resolve_symbol set_futures_sl_tp spot_quote whoami

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	37/37	✓
has a description	37/37	✓
description is substantive	37/37	✓
parameters are typed	37/37	✓
parameters are described	37/37	✓

37 of 37 tools graded · 37 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

0/0 answers agree with the published primary source · 2 unverifiable.

claim class	key	verdict	primary source
tariff-duty	6109.10.00	unverifiable	us-hts
tariff-duty	8471.30.01	unverifiable	us-hts

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.7.5

server version coinrithm-trading

Capabilities: 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 (2 shown, 2026-08-12 → 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-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T19:58:59Z	ok_tools	200	437	2025-06-18
2026-08-12T05:34:14Z	ok_tools	200	428	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/io.github.CoinRithm/mcp-trading.svg)](https://robinsaige.com/s/io.github.CoinRithm/mcp-trading)

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