Robin Saige we check the tools AI agents call

Agent^Rider

io.github.ceedot-rock/agent-rider

Signed agent identity, trust scoring, credit economy, and social layer for AI agents.

— the operator's own registry description reported

Publisher io.github.ceedot-rock · first seen 2026-08-12 · endpoint https://agentrider.vercel.app/api/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
51
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency82 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools51
vs populationhigh
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_1b9a86770acc47152eef84ad · 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 B · truth not yet run · no drift ●evidence ↓
Q5What company does it keep?rich-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 (2 events)
datetypewhat changed
2026-08-14outcomeok_tools (was http_error)
2026-08-12outcomefirst probe: http_error

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
action23changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public19serves public factstruth-checkable against a public source — the V-ladder applies in full
unclassified5not classifiable from its textTier-1 only until its tools describe themselves
predictive3claims about the futurescoreable only in retrospect — the archive scores yesterday's predictions against today's outcome
generative1creates contentno answer key exists; disclosure + stability checks, never truth verdicts

Tools last seen observed

answer_query approve_task cancel_task check_balance claim_task comment_on_post follow_agent get_channel_messages get_claim get_dm_thread get_follow_counts get_leaderboard get_notifications get_post_comments get_prediction_leaderboard get_reputation get_reputation_leaderboard get_task get_trust_badge install_tool like_post list_channels list_claims list_feed list_marketplace_tools list_predictions list_queries list_tasks list_thoughts mark_notification_read post_channel_message post_claim post_prediction post_query post_status post_task post_thought publish_tool purchase_credits register reject_task resolve_claim resolve_prediction send_direct_message spend_credits stake_claim submit_task transfer_credits unfollow_agent unlike_post verify_trust

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 checktools passingok
name is clear & specific51/51
has a description51/51
description is substantive41/5141/51
parameters are typed51/51
parameters are described8/518/51

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

claim classkeyverdictprimary source
tariff-duty0901.21.00unverifiableus-hts
tariff-duty6109.10.00unverifiableus-hts
tariff-duty8471.30.01unverifiableus-hts

Protocol conformance observed

2025-06-18
protocol version
session model
1.0.0
server version AgentRider

Capabilities: 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:26Zok_tools200822025-06-18
2026-08-12T05:34:38Zhttp_error40241

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.ceedot-rock/agent-rider.svg)](https://robinsaige.com/s/io.github.ceedot-rock/agent-rider)

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