Should my agent depend on the MCP server io.github.rezearcher/tech-risk?

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

tech risk

io.github.rezearcher/tech-risk

x402 MCP for agents: crypto prices, funding, DeFi yields, Polymarket, Base RPC + MCP security.

— the operator's own registry description reported

Publisher io.github.rezearcher · first seen 2026-08-12 · endpoint https://x402-data-api.sigrunner.workers.dev/mcp

allow

verdict

mid-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — mid-shared — safe to depend on

Cluster mid-shared · distinctiveness 0.221 (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

latency295 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools22

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identityshared

servers on its host1

servers on its domain2

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

chain_balance chain_block_number chain_block_number_preview chain_gas_price chain_gas_price_preview chain_token_balance chain_token_security chain_token_security_preview chain_tx chain_wallet crypto_funding crypto_funding_preview crypto_prices crypto_prices_preview defi_yields defi_yields_preview enrich_domain enrich_tech_risk pm_markets pm_markets_preview scan_mcp_preview scan_mcp_server

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

22 of 22 tools graded · 22 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.0

server version x402-data-api

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-14T20:00:10Z	ok_tools	200	295	2025-06-18
2026-08-12T05:35:22Z	ok_tools	200	250	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.rezearcher/tech-risk.svg)](https://robinsaige.com/s/io.github.rezearcher/tech-risk)

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