Should my agent depend on the MCP server com.hergertsynthora/synthora-x402?

Verdict: allow — stale-mid-solo — safe to depend on As of 2026-09-06T06:21:45Z: a dated observation with receipts, not a warranty.

SYNTHORA x402 Intelligence Mesh

com.hergertsynthora/synthora-x402

Calibrated intelligence via x402 (USDC Base). ERC-8004 #84581: 272 payments, 49 wallets.

— the operator's own registry description reported

Publisher com.hergertsynthora · first seen 2026-08-12 · endpoint https://mcp.hergertsynthora.com/mcp

allow

verdict

stale-mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · retrieval-public ● · V3 has answer key ◐

allow — because answers ●, 30 tools legible (band A) ●, no confirmed drift in 6 probes ●; not yet checked: truth (2 attempts unverifiable, 0 disagreements)

Cluster stale-mid-solo · distinctiveness 0.39 (moderate). Every figure is a percentile or class within the 15,472-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency331 ms

vs populationtypical

protocolbehind

authopen

Can it be used? Q4 · observed

tools30

vs populationhigh

capabilities1

harnessA

Did it hold when checked? Q3–Q4 · derived

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers true0/0 agree

🔏 Signed receipt rr_d12991314b127d21b90c6be3 · 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 — 6 probes ●evidence ↓

Q2What is it?retrieval-public ● evidence ↓

Q3Can it be checked?V3 has answer key ◐evidence ↓

Q4Did it hold?harness A · truth not yet run · no drift ●evidence ↓

Q5What company does it keep?stale-mid-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 (6 shown, 2026-08-12 → 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 (2 events)

date	type	what changed
2026-08-23	outcome	ok_tools (was not_mcp)
2026-08-12	outcome	first probe: not_mcp

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 →):

nature	tools	meaning	what checking applies
retrieval-public	23	serves public facts	truth-checkable against a public source — the V-ladder applies in full
predictive	4	claims about the future	scoreable only in retrospect — the archive scores yesterday's predictions against today's outcome
computational	2	deterministic transforms	self-checkable by re-computation and known-answer tests
orchestration	1	routes other tools	identity + fronted-service disclosure checks (gateway vs costume)

Tools last seen observed

asset_risk chokepoint_risk codeaudit daily_intel_brief dispute_risk domain_risk emerging_protocols funding_spread identity_risk insider_radar macro_surprise macrobundle market_sentiment polymarket_odds_movers polymarket_resolution_watch polymarket_whales registry_watch resolution_source_feed resolution_verdict rwa_gap_watch sanctions_screen shipping_alpha space_weather_risk threat_exposure tvl_concentration tx_simulator txintent vessel_sanctions volume_anomaly wallet_enrich

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

30 of 30 tools graded · 30 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 yet confirmed — 2 attempt(s) currently unverifiable (rate limits, walls, or unmappable schemas — never counted against the server) · 0 disagreements.

claim class	key	verdict	primary source
OFAC SDN screening (vs the official list)	ISLAMIC REVOLUTIONARY GUARD CORPS	unverifiable	ofac-sdn
OFAC SDN screening (vs the official list)	MAERSK LINE	unverifiable	ofac-sdn

Protocol conformance observed

2025-03-26

protocol version

—

session model

1.0.1

server version synthora-mcp

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)	outcome	http	ms	protocol
2026-09-06T06:12:30Z	ok_tools	200	331	2025-03-26
2026-08-30T06:12:14Z	ok_tools	200	314	2025-03-26
2026-08-23T06:11:54Z	ok_tools	200	320	2025-03-26
2026-08-16T06:11:44Z	not_mcp	200	326
2026-08-14T19:58:12Z	not_mcp	200	327
2026-08-12T05:33:26Z	not_mcp	200	427

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/com.hergertsynthora/synthora-x402.svg)](https://robinsaige.com/s/com.hergertsynthora/synthora-x402)

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 →