Should my agent depend on the MCP server io.github.gomission/mcp?

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

Mission — Trust Graduation Gate

io.github.gomission/mcp

Trust Graduation gate: Claude can do real work once Mission decides what it is allowed to do.

— the operator's own registry description reported

Publisher io.github.gomission · first seen 2026-08-12 · endpoint https://claude.gomission.io/mcp/

allow

verdict

stale-mid-solo

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — stale-mid-solo — safe to depend on

Cluster stale-mid-solo · distinctiveness 0.163 (typical). 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

latency191 ms

vs populationtypical

protocolstale

authopen

Use — can it use it?

tools29

vs populationmid

capabilities1

harnessA

Trust — can it rely on it?

identitysolo

servers on its host1

verifiabilityunassessed

duplicate inventoryno

drift events0

answers trueno primary

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

get_receipt log_action mission_account_setup mission_account_status mission_adoption_proof mission_check_approval mission_classify mission_draft_queue mission_fetch mission_get_workspace_status mission_learning_status mission_list_connectors mission_market_radar mission_open_approval_packet mission_open_cockpit mission_open_loops mission_prepare_approval_packet mission_prepare_email_draft mission_prepare_market_countermove mission_prepare_social_reply mission_proof_loop mission_receipts mission_search mission_start_connector_setup mission_status mission_submission_readiness mission_today mission_voice_profile request_approval

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 check	tools passing	ok
name is clear & specific	29/29	✓
has a description	29/29	✓
description is substantive	29/29	✓
parameters are typed	29/29	✓
parameters are described	9/29	9/29

29 of 29 tools graded · 29 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

2024-11-05

protocol version

—

session model

0.1.0-demo

server version mission

Capabilities: 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-14T19:59:34Z	ok_tools	200	191	2024-11-05
2026-08-12T05:34:47Z	ok_tools	200	249	2024-11-05

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.gomission/mcp.svg)](https://robinsaige.com/s/io.github.gomission/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