Should my agent depend on the MCP server io.github.ronrey/comos-federation?

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

ComOS Federation Gateway

io.github.ronrey/comos-federation

Multi-tenant MCP gateway for AI commerce. One connection, every store.

— the operator's own registry description reported

Publisher io.github.ronrey · first seen 2026-08-12 · endpoint https://mcp.comos-gateway.com/mcp

allow

verdict

rich-shared

cluster

ok_tools

answers

tools served

Dependency rating derived

allow — rich-shared — safe to depend on

Cluster rich-shared · distinctiveness 0.431 (moderate). 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

latency288 ms

vs populationtypical

protocolcurrent

authopen

Use — can it use it?

tools71

vs populationhigh

capabilities1

harnessA

Trust — can it rely on it?

identityshared

servers on its host2

verifiabilityunassessed

duplicate inventoryyes

drift events0

answers trueno primary

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

about_us_about cohort_email_send federation_admittance_decide federation_admittance_queue federation_agent_status federation_apply federation_arena federation_attest federation_bond_post federation_bond_release federation_bond_status federation_canon_get federation_canon_put federation_catalog_agents federation_catalog_platforms federation_catalog_search_grouped_multi federation_catalog_search_multi federation_catalog_version federation_choice_compare federation_choice_get federation_create_manager federation_create_tenant federation_delete_tenant federation_enter_tenant federation_freeze_manager federation_get_agent_runs federation_governance federation_help federation_journal_append federation_journal_read federation_key_bind federation_key_challenge federation_key_status federation_latency federation_list_agent_types federation_list_agents federation_list_managers federation_list_tenants federation_manager_tree federation_pricesheet federation_promote federation_refresh_tools federation_run_agent federation_search federation_solvency federation_suspend_tenant federation_tenant_info federation_unfreeze_manager federation_update_tenant federation_why how_to_about introspection_corpus_compare introspection_corpus_generate introspection_corpus_probe_disagreement introspection_corpus_probe_scope introspection_corpus_query introspection_system_change_graph introspection_system_change_reach introspection_system_climb_history introspection_system_co_decisions introspection_system_confidence introspection_system_coverage_gaps introspection_system_diff introspection_system_list_nodes introspection_system_list_repos introspection_system_probe legal_get llm_author moltbook_post moltbook_read web_research

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	71/71	✓
has a description	71/71	✓
description is substantive	71/71	✓
parameters are typed	70/71	70/71
parameters are described	58/71	58/71

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

1.0.0

server version comos-gateway

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-14T20:00:10Z	ok_tools	200	288	2025-06-18
2026-08-12T05:35:23Z	ok_tools	200	241	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.ronrey/comos-federation.svg)](https://robinsaige.com/s/io.github.ronrey/comos-federation)

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