Robin Saige we check the tools AI agents call

x402 tools

dev.workers.kikoribera03.flat-rate-llm/x402-tools

61 x402 pay-per-call tools that chain: each answer names the next call. No API key, no account.

— the operator's own registry description reported

Publisher dev.workers.kikoribera03.flat-rate-llm · first seen 2026-09-09 · endpoint https://flat-rate-llm.kikoribera03.workers.dev/mcp

allow
verdict
rich-fast-solo
cluster
ok_tools
answers
63
tools served

Dependency rating derived

allow
allow — alive & usable · kind unknown · V n/a
allow — because answers ●, 63 tools legible (band A) ●, no confirmed drift in 1 probes ●; not yet checked: truth (1 attempts unverifiable, 0 disagreements)

Cluster rich-fast-solo · distinctiveness 0.66 (unusual). Every figure is a percentile or class within the 19,148-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency40 ms
vs populationfast
protocolcurrent
authopen
Can it be used? Q4 · observed
tools63
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_1670b343954bbd8450bfd5c0 · 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 A · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-fast-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)
datetypewhat changed
2026-09-13outcomefirst 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 →):

naturetoolsmeaning what checking applies
unclassified25not classifiable from its textTier-1 only until its tools describe themselves
action19changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public9serves public factstruth-checkable against a public source — the V-ladder applies in full
computational7deterministic transformsself-checkable by re-computation and known-answer tests
orchestration2routes other toolsidentity + fronted-service disclosure checks (gateway vs costume)
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

catalog content_advice content_fact content_horror_story content_joke content_riddle content_roast content_word_of_the_day crypto_sanctions evm_balance evm_block evm_call evm_chains evm_ens evm_erc20_allowance evm_erc20_balance evm_estimate_gas evm_fees evm_gas evm_is_contract evm_nft_owner evm_nonce evm_portfolio evm_receipt evm_storage evm_token_info evm_token_price evm_token_safety evm_tx fx_convert llm_completion random_coinflip random_dice random_number random_password random_pick random_shuffle red_asn red_cert red_dnsbl red_domain_check red_email_check red_ip red_whois time_convert time_now time_zones util_address util_base64 util_hex util_iban util_keccak256 util_phone util_selector util_sha256 util_units util_uuid util_vat util_verify_signature weather_forecast weather_now web_read web_status

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 checktools passingok
name is clear & specific63/63
has a description63/63
description is substantive63/63
parameters are typed63/63
parameters are described63/63

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

claim classkeyverdictprimary source
OFAC SDN screening (vs the official list)unmappedunverifiableofac-sdn

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version flat-rate-x402-tools

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) outcomehttpmsprotocol
2026-09-13T06:14:07Zok_tools200402025-06-18

Watch or embed this verdict

verdict badge

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/dev.workers.kikoribera03.flat-rate-llm/x402-tools.svg)](https://robinsaige.com/s/dev.workers.kikoribera03.flat-rate-llm/x402-tools)

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 →