Robin Saige we check the tools AI agents call

argo mcp

io.github.Argo-RPG-Platform/argo-mcp

MCP server for Argo RPG Platform — connects AI assistants to campaign data via OAuth2

— the operator's own registry description reported

Publisher io.github.Argo-RPG-Platform · first seen 2026-08-12 · endpoint https://mcp.argo.games/mcp

allow
verdict
rich-solo
cluster
ok_tools
answers
62
tools served

Dependency rating derived

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

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

Does it answer? Q1 · observed
answersalive_tools
latency140 ms
vs populationtypical
protocolcurrent
authopen
Can it be used? Q4 · observed
tools62
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_c1c670f79a5ec21e84a745e1 · 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-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
action34changes the worldno true answer exists; we check the CONTRACT (destructive/read-only/idempotent declarations, error legibility) and never fire real actions
retrieval-public23serves 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

Tools last seen observed

accept_friend_request add_campaign_to_guild add_co_gm add_guild_calendar_event cancel_friend_request create_archive_mnemons create_campaign create_custom_mnemons create_journal_mnemons create_location_mnemons create_lore_mnemons create_mnemon_relationship create_npc_mnemons create_player_mnemons create_quest_mnemons create_session create_session_summary_mnemons delete_mnemon delete_mnemon_relationship describe_mnemon_types forum_create_topic forum_get_latest_topics forum_get_notifications forum_get_user_posts forum_list_categories forum_list_topics forum_read_topic forum_reply forum_search get_campaign get_guild get_mnemon get_session invite_guild_member list_campaigns list_co_gms list_friends list_guild_members list_guilds list_mnemon_relationships list_mnemons list_received_friend_requests list_sent_friend_requests list_sessions reject_friend_request remove_co_gm remove_guild_member search_mnemons send_friend_request set_guild_member_role update_archive_mnemons update_campaign update_custom_mnemons update_journal_mnemons update_location_mnemons update_lore_mnemons update_mnemons_content update_npc_mnemons update_player_mnemons update_quest_mnemons update_session update_session_summary_mnemons

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 & specific62/62
has a description62/62
description is substantive60/6260/62
parameters are typed62/62
parameters are described39/6239/62

62 of 62 tools graded · 62 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.1.0
server version argo-mcp

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:58:55Zok_tools2001402025-06-18
2026-08-12T05:34:09Zok_tools2001252025-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.Argo-RPG-Platform/argo-mcp.svg)](https://robinsaige.com/s/io.github.Argo-RPG-Platform/argo-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