Should my agent depend on the MCP server io.github.vinsenzo83/baton?

Verdict: allow — rich-fast-solo — safe to depend on As of 2026-08-15T11:28:18Z: a dated observation with receipts, not a warranty.

baton

io.github.vinsenzo83/baton

Hand off AI work with a signed Verification Receipt — an independent verifier proves it runs.

— the operator's own registry description reported

Publisher io.github.vinsenzo83 · first seen 2026-08-12 · endpoint https://baton-mcp-production.up.railway.app/mcp

allow

verdict

rich-fast-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-fast-solo — safe to depend on

Cluster rich-fast-solo · distinctiveness 0.605 (unusual). Every figure is a percentile or class within the 11,094-server census — see the whole spectrum.

Reach — can an agent get to it?

answersalive_tools

latency32 ms

vs populationfast

protocolcurrent

authopen

Use — can it use it?

tools45

vs populationhigh

capabilities2

harnessB

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

🔏 Signed receipt rr_ddface96e4884098ccf8d5bc · 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.

Tools last seen

baton_account baton_agent_list baton_agent_record_result baton_agent_register baton_approve baton_close_room baton_confirm_payment baton_consolidate baton_cost_record baton_cost_summary baton_create_room baton_diff baton_git_evidence baton_git_record baton_hub_list baton_hub_observe baton_hub_register baton_inbox baton_join baton_kick baton_leave baton_memory_delete baton_memory_get baton_memory_put baton_memory_search baton_new_invite baton_pass baton_receive baton_revoke baton_send baton_signup baton_task_create baton_task_graph baton_task_link baton_task_update baton_upgrade baton_verify baton_verify_plan baton_who spider_checklist spider_classify_tier spider_plan spider_pull_corpus spider_record_pattern spider_signals

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	45/45	✓
has a description	45/45	✓
description is substantive	32/45	32/45
parameters are typed	41/45	41/45
parameters are described	9/45	9/45

45 of 45 tools graded · 45 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 in the Tier-2 trade lane, or not yet checked. Tier-2 re-derives a server's answers against published primary sources — see truth checks.

Protocol conformance observed

2025-06-18

protocol version

—

session model

0.4.1

server version baton

Capabilities: resources tools

Drift

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

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)

date	type	what changed
2026-08-12	outcome	first probe: ok_tools

raw probe records

probed (UTC)	outcome	http	ms	protocol
2026-08-14T20:00:19Z	ok_tools	200	32	2025-06-18
2026-08-12T05:35:31Z	ok_tools	200	27	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.vinsenzo83/baton.svg)](https://robinsaige.com/s/io.github.vinsenzo83/baton)

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