Should my agent depend on the MCP server io.github.ronaldanton/agentpay?

Verdict: allow — mid-solo — safe to depend on As of 2026-09-13T06:22:43Z: a dated observation with receipts, not a warranty.

AgentPay — Pay-per-call AI Microservices

io.github.ronaldanton/agentpay

22 AI microservices with x402 micropayments: summarize, translate, code-review. USDC on Base.

— the operator's own registry description reported

Publisher io.github.ronaldanton · first seen 2026-09-13 · endpoint https://agentpay.help/mcp

allow

verdict

mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow
allow — alive & usable · kind unknown · V n/a

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

Cluster mid-solo · distinctiveness 0.249 (typical). Every figure is a percentile or class within the 19,148-server census — see the whole spectrum.

Does it answer? Q1 · observed

answersalive_tools

latency148 ms

vs populationtypical

protocolcurrent

authopen

Can it be used? Q4 · observed

tools28

vs populationmid

capabilities1

harnessB

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_29a25d2e5b7975aa2755ded3 · 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?kind unknown ● evidence ↓

Q3Can it be checked?V n/a for this kind ◐evidence ↓

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

Q5What company does it keep?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 (1 shown, 2026-09-13 → 2026-09-13). 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-09-13	outcome	first 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 →):

nature	tools	meaning	what checking applies
unclassified	16	not classifiable from its text	Tier-1 only until its tools describe themselves
retrieval-public	6	serves public facts	truth-checkable against a public source — the V-ladder applies in full
action	2	changes the world	no true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
generative	2	creates content	no answer key exists; disclosure + stability checks, never truth verdicts
predictive	2	claims about the future	scoreable only in retrospect — the archive scores yesterday's predictions against today's outcome

Tools last seen observed

agent-reputation classify-insurance code-review content-safety crypto-price deep-research defi-yields eth-gas extract geocode image-describe insurance-analysis legal-lookup market-intel memory news-feed on-chain-events prediction-market sanctions-screen sentiment summarize threat-intel token-safety translate wallet-risk weather-data web-scrape web-search

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 B — usable, with rough edges.

legibility check	tools passing	ok
name is clear & specific	28/28	✓
has a description	28/28	✓
description is substantive	28/28	✓
parameters are typed	28/28	✓
parameters are described	1/28	1/28

28 of 28 tools graded · 28 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-06-18

protocol version

—

session model

1.0.0

server version agentpay

Capabilities: tools

Drift observed

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

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-09-13T06:18:03Z	ok_tools	200	148	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.ronaldanton/agentpay.svg)](https://robinsaige.com/s/io.github.ronaldanton/agentpay)

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 →