For teams using external agents and MCP servers: inspect measured evidence, watch changes, and keep a record of what your team accepted. Unknown evidence stays explicit.
Have a client configuration? Extract and check its public endpoints locally. Maintaining integrations for clients? Explore the agency pilot.
Runtime observation: 2026-10-20T23:34:06.587639+00:00 · State: live
Watch availability, tools and parameter schemas, authentication access, endpoint changes and lifecycle notices. Only complete observed schemas are compared. OAuth scope and consent-screen changes are not currently measured.
Sign in to watch this MCP serverSign-in required. Agent and MCP watches share the existing Free / Pro / Enterprise budget. Manage watches.
{
"auth": "anonymous",
"availability": "live",
"endpoint": "https://mcp.coinrithm.com/mcp",
"legal_identity": null,
"lifecycle": null,
"observed_at": "2026-10-20T23:34:06.587639+00:00",
"registry_status": null,
"subject": {
"id": "io.github.coinrithm/mcp-trading",
"kind": "mcp"
},
"tools": {
"names": [
"cancel_spot_order",
"close_futures_position",
"crypto_price",
"discover_pm_markets",
"export_agent_ledger",
"export_run_evidence",
"futures_quote",
"get_agent_ledger",
"get_arena_agent",
"get_arena_leaderboard",
"get_candles",
"get_crypto_movers",
"get_equity_curve",
"get_market_context",
"get_my_trades",
"get_news",
"get_performance",
"get_portfolio",
"get_positions",
"get_wallet",
"instrument_markets",
"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_expiring",
"pm_data_orderbook",
"pm_data_overview",
"pm_data_price_history",
"pm_data_resolved",
"pm_data_sources",
"pm_data_sources_health",
"pm_data_surprises",
"pm_data_volume_history",
"pm_data_whale_wallet",
"pm_data_whale_wallets",
"pm_data_whales",
"pm_quote",
"report_pm_opportunity",
"resolve_symbol",
"set_futures_sl_tp",
"spot_quote",
"tradfi_references",
"whoami"
],
"names_truncated": false,
"sha256": "ac926a4386f62cdd7ef7b1114f80246a1a87068cc5855bb8a5611e7756f56d61"
},
"tools_complete": true,
"tools_observed_at": "2026-10-20T23:34:06.587639+00:00",
"version": null
}Keep an accepted snapshot in agents.lock.json. CI compares it with current evidence and returns allow, review or block with reasons, before/after data and policy hashes.
Default gaps require review. Configure stricter handling explicitly. A lock records your acceptance; it is not a supplier attestation.
API referenceVerified domain owners can publish up to five exact-match sandbox fixtures and opt in to a test run. Results include fixture version, latency, output hashes and comparable regressions. Cost remains unknown when unobserved.
Run with POST /api/v1/dependencies/task-checks?domain=… while signed in. Read the schema and example in the integration guide.
Domain control, a declared business identifier and an active name-matched company record are separate evidence. Zero verified records means zero recorded proof.
Current coverage and measurement date · Verify your domainVerify issuer signatures, subject and credential freshness using the public key document. Keep its task evidence categories separate from Agenstry measurements.
A valid SEAL does not establish domain ownership, legal identity, key possession or execution permission.
Credential verification API · Issuer documentationSmithery endpoint migration · Agent monitoring · Methodology