Robin Saige we check the tools AI agents call

onyx mcp

io.github.dimitrilaouanis-tech/onyx-mcp

Ed25519-signed ground-truth oracle — 63 paid x402 tools live on Base mainnet.

— the operator's own registry description reported

Publisher io.github.dimitrilaouanis-tech · first seen 2026-08-12 · endpoint https://onyx-actions.onrender.com/mcp/

allow
verdict
rich-slow-solo
cluster
ok_tools
answers
33
tools served

Dependency rating derived

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

Cluster rich-slow-solo · distinctiveness 0.435 (moderate). Every figure is a percentile or class within the 11,094-server censussee the whole spectrum.

Does it answer? Q1 · observed
answersalive_tools
latency479 ms
vs populationslow
protocolcurrent
authopen
Can it be used? Q4 · observed
tools33
vs populationhigh
capabilities2
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_4ea5f8dbf39a680b99333c04 · 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 — 2 probes ●evidence ↓
Q2What is it?action ● 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-slow-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 (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)
datetypewhat changed
2026-08-12outcomefirst 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
action17changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public11serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified4not classifiable from its textTier-1 only until its tools describe themselves
computational1deterministic transformsself-checkable by re-computation and known-answer tests

Tools last seen observed

onyx_aeo_score onyx_agent_economy_index onyx_agent_registry onyx_agent_verify onyx_ai_visibility onyx_attestation_verify onyx_contract_audit onyx_ecosystem_intel onyx_erc8004_lookup onyx_intel_exchange onyx_mail_check onyx_mail_send onyx_market_rank onyx_merchant_fact_check onyx_payment_gate onyx_perm_check onyx_perm_grant onyx_preflight onyx_research_intel onyx_retail_price_check onyx_secure_payment onyx_security_flags onyx_signature_guard onyx_token_risk onyx_track_record onyx_tx_guard onyx_tx_preflight onyx_verified_issue onyx_verify_explain onyx_x402_receipt_verify rhinogent_identity rhinogent_mandate rhinogent_verify_counterparty

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 & specific33/33
has a description33/33
description is substantive33/33
parameters are typed33/33
parameters are described32/3332/33

33 of 33 tools graded · 33 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
tariff-dutyunmappedunverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.26.0
server version onyx-actions

Capabilities: experimental tools

Drift observed

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

raw probe records
probed (UTC) outcomehttpmsprotocol
2026-08-14T19:59:29Zok_tools2004792025-06-18
2026-08-12T05:34:42Zok_tools2004672025-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/io.github.dimitrilaouanis-tech/onyx-mcp.svg)](https://robinsaige.com/s/io.github.dimitrilaouanis-tech/onyx-mcp)

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