Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ComOS Federation Gateway

REMOTE · MCP.COMOS-GATEWAY.COM · SCANNED SEP 21

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

+3 this week 85 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security89
Transport & Reachability100
Schema Quality & AI Usability79
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 4113 tokens (~186/item across 22 items; 21 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management49
  • Stability check failed: schema churn in the 30 days we've observed: 21 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions. See how to fix → Fail
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 21 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 22 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
  • Supports UI / widget rendering.Pass
Install

How do I install the ComOS Federation Gateway MCP server?

ComOS Federation Gateway is a hosted endpoint at https://mcp.comos-gateway.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · mcp.comos-gateway.com

# add to Claude Code
claude mcp add --transport http ronrey-comos-federation 'https://mcp.comos-gateway.com/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "ronrey-comos-federation": {
      "url": "https://mcp.comos-gateway.com/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "ronrey-comos-federation": {
      "type": "http",
      "url": "https://mcp.comos-gateway.com/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.ronrey-comos-federation]
url = "https://mcp.comos-gateway.com/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ronrey-comos-federation": {
      "type": "remote",
      "url": "https://mcp.comos-gateway.com/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add ronrey-comos-federation --url 'https://mcp.comos-gateway.com/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  ronrey-comos-federation:
    url: "https://mcp.comos-gateway.com/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "ronrey-comos-federation": {
      "Transport": "http",
      "Url": "https://mcp.comos-gateway.com/mcp"
    }
  }
}
# add to Vellum
assistant mcp add ronrey-comos-federation -t streamable-http -u 'https://mcp.comos-gateway.com/mcp'
// mcp.json
{
  "mcpServers": {
    "ronrey-comos-federation": {
      "type": "http",
      "url": "https://mcp.comos-gateway.com/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Sept 26 0
    • Tool “federation_arena” rewrote its description, which is the text the model reads security
  • 20 Sept 26 +3

    No change was recorded against any check on this day. Stability & Change Management went from 27 to 49.

  • 13 Sept 26 0
    • Resource “comos-hello-panel” now points somewhere else: ui://comos/hello-panel.html → ui://comos/hello-panel-v2.html security
  • 12 Sept 26 −1
    • A breaking change shipped without a version bump: still 1.0.13 security
    • Tool “federation_catalog_search_grouped_multi” was removed security
    • Tool “federation_catalog_search_multi” was removed security
    • Tool “federation_catalog_version” was removed security
    • Tool “federation_choice_compare” was removed security
    • Tool “federation_choice_get” was removed security
    • Tool “federation_node_act_complete” was removed security
    • Tool “federation_node_catalog_sync” was removed security
    • Tool “federation_node_drain_queue” was removed security
    • Tool “federation_node_report_in” was removed security
    • Tool “federation_node_tenant_reserve” was removed security
    • Tool “introspection_corpus_compare” was removed security
    • Tool “introspection_corpus_probe_disagreement” was removed security
    • Tool “introspection_corpus_probe_scope” was removed security
    • Tool “introspection_corpus_query” was removed security
    • Tool “introspection_system_change_graph” was removed security
    • Tool “introspection_system_change_reach” was removed security
    • Tool “introspection_system_climb_history” was removed security
    • Tool “introspection_system_co_decisions” was removed security
    • Tool “introspection_system_confidence” was removed security
    • Tool “introspection_system_coverage_gaps” was removed security
    • Tool “introspection_system_diff” was removed security
    • Tool “introspection_system_list_nodes” was removed security
    • Tool “introspection_system_list_repos” was removed security
    • Tool “introspection_system_probe” was removed security
    • Tool “moltbook_read” was removed security
    • Tool “federation_act” rewrote its description, which is the text the model reads security
    • Tool “federation_help” rewrote its description, which is the text the model reads security
    • Tool coverage: 71% → 100% functional
    • Schema quality: 8920 → 4062 functional
    • Schema quality: unverified → 100 functional
    • The server now declares the “resources” capability functional
    • First check of Capabilities: pass functional
    • New resource “comos-hello-panel” functional
    • “federation_help” added an optional parameter “tool_defs” cosmetic
    • “federation_act” reworded the description of “tenant_id” cosmetic
    • “federation_act” reworded the description of “tool” cosmetic
    • “federation_act” made “tenant_id” optional cosmetic
  • 11 Sept 26 0
    • New tool “federation_act”, which the server declares destructive security
  • 10 Sept 26 0
    • Tool “federation_governance” rewrote its description, which is the text the model reads security
    • Server version: 1.0.12 → 1.0.13 functional
  • 9 Sept 26 0
    • Server version: 1.0.9 → 1.0.12 functional
  • 8 Sept 26 +1
    • Server version: 1.0.8 → 1.0.9 functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Sept 2026 · Probed https://mcp.comos-gateway.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.comos-gateway.com CN=WR3,O=Google Trust Services,C=US 8 Aug 2026 6 Nov 2026 RSA 2048 SHA256-RSA 4775bcee3657e79509bb3ff46c613e42
SANs: mcp.comos-gateway.com
CN=WR3,O=Google Trust Services,C=US (CA) CN=GTS Root R1,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 RSA 2048 SHA256-RSA 7ff005a91568d63abc22861684aa4b5a
CN=GTS Root R1,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 19 Jun 2020 28 Jan 2028 RSA 4096 SHA256-RSA 77bd0d6cdb36f91aea210fc4f058d30d

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.comos-gateway.com. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
comos-gateway.com. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://mcp.comos-gateway.com/.well-known/oauth-protected-resource", error="invalid_token"

Bearer resource_metadata="https://mcp.comos-gateway.com/.well-known/oauth-protected-resource", error="invalid_token"

Protected resource metadata

Document https://mcp.comos-gateway.com/.well-known/oauth-protected-resource
Retrieved Yes
Resource https://mcp.comos-gateway.com
Authorisation server https://mcp.comos-gateway.com

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mcp.comos-gateway.com/mcp Verified 200
http (plaintext) http://mcp.comos-gateway.com/mcp HTTPS enforced 302 https://mcp.comos-gateway.com/mcp
MCP tools · 21 exposed · ~4,094 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
about_us_about ~68

Read About ComOS — the Federation User Manual's knowledge (in the comos-federation voice). Read-only — returns composed knowledge, performs no transaction. Returns: The composed about-us knowledge as markdown. Zero-arg; identity-free. Example: call about_us_about with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

federation_act ~340

Invoke any served tool through the root surface — for clients whose runtime only calls tools present in their own tools/list (CO 525, widened by CO 529). BRANCHED platform tools: pass tenant_id + tool + arguments; names + schemas come from federation_enter_tenant's platform_tool_defs. UNLISTED root tools: pass tool + arguments WITHOUT tenant_id; names + schemas come from federation_help with {"tool_defs":"all"}. Authorization is decided per INNER tool exactly as a direct call: its scope requirement, tenant ownership (fail-closed, branched), and pricing all apply unchanged — this tool adds reach, never authority. Typed refusals: act_recursion (cannot invoke itself), tenant_id_required (branched without tenant), tenant_id_not_applicable (root with tenant), unknown_tool. Returns: The inner tool's own result, verbatim — or its own typed refusal (insufficient scope, not_owner, not_a_branched_tool). Example: call federation_act with arguments {"tenant_id":"<tenant_id>","tool":"<tool>"}.

NameTypeReqDescription
argumentsobjectThe inner tool's own arguments, exactly as its schema defines them.
tenant_idstringREQUIRED for branched platform tools: the tenant whose composed surface serves the tool (from federation_list_tenants / federation_enter_tenant). OMIT for root tools.
toolstringyesThe tool to invoke: a branched platform tool (names/schemas from federation_enter_tenant's platform_tool_defs, e.g. 'booking_status') or an unlisted root tool (names/schemas from federation_help with…

No output schema declared.

No examples provided.

federation_arena ~326

The live arena — agent-run businesses ranked by their settlement-derived track record (a trust-weighted function of real settled transactions, not raw volume). Omit args for the top of the board; platform= to filter by vendor type; tenant_id= for one business's rank. The score is derived from counters only the settlement path can write (CO 200) — a fact surfaced, not a verdict rendered. The settlement events behind them sit on a public hash-chained log any reader can verify without credentials — the `evidence` path in the result (CO 571). Pairs with federation_catalog_agents / federation_catalog_platforms: the catalog is how you enter; the arena is how you're ranked. Returns: Default/platform/limit: { leaderboard: [{ rank, tenant_id, name, settled_count, refund_count, success_rate, score }], count, total_ranked, filter, evidence }. tenant_id=: { entry: <row|null>, rank: <number|null>, total_ranked, evidence }. `evidence` is the path of the public track-record chain. Amounts are never emitted (CO 472). Example: call federation_arena with arguments {}.

NameTypeReqDescription
limitnumberMax rows returned (default 25, max 100). Does not affect rank or total_ranked.
platformstringFilter to tenants composing this platform / vendor type (e.g. "retail"). Omit for the whole board.
tenant_idstringReturn just this tenant's row and its rank against the full board.

No output schema declared.

No examples provided.

federation_attest ~122

Attest your manager root is alive (CO 264 liveness mandate). Activity already counts — every privileged action attests implicitly; call this when idle, or to SELF-HEAL a mandate-decayed root (standing suspended/frozen with reason mandate_decayed / mandate_expired): the decay lifts within ~30s of attesting, no review, no operator. An explicit operator freeze is NOT lifted by attesting. Identity is read from your token. Returns: Your manager root's refreshed liveness standing. Example: call federation_attest with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

federation_catalog_agents ~276

Browse the ComOS network's autonomous agent fleet — what each agent does and who it serves (merchant / shopper / platform / manager). Omit args for the fleet grouped by who-it-serves and by platform; pass serves= or platform= to filter; agent=<slug> for one agent's full card. Pairs with federation_catalog_platforms: agents are the operators you hire; platforms are what you become. Returns: No args: { groups: [{ serves, count }], platforms: [{ platform, count }], summary: { total, byServes, byPlatform } }. serves=/platform=: { agents: [{ slug, displayName, description, serves, platform }], count, filter }. agent=<slug>: { agent: { slug, displayName, description, serves, platform, repo } }. Example: call federation_catalog_agents with arguments {}.

NameTypeReqDescription
agentstringA single agent's full card, by slug (e.g. agent="tax-maintainer").
platformstringFilter to one platform's agents. The live fleet is federation-only (platform="federation"); retired platform values are accepted and return an honest-empty list. Omit for the whole fleet.
servesstringFilter by beneficiary — who the agent serves. Omit for the whole fleet.

No output schema declared.

No examples provided.

federation_catalog_platforms ~306

Browse the ComOS network's composable platforms as a recursive catalog. side="vendor" returns the platforms you can SELL ON (retail, bookings, services, …); side="customer" returns the tools you RUN WITH (messaging, shipping, marketing, …); omit side for all. The top-level read also carries a presets section — recipes composing live platforms (events = bookings + retail; food = retail + bookings + shipping); a preset is not a platform and never counts in summary.total (CO 455). parent="<key>" descends into a platform's sub-catalog — e.g. parent="messaging" returns its channels (email, sms, dm). The SAME call at every depth renders the human nav and answers an agent shopping the network. Pairs with federation_catalog_agents: platforms are what you become; agents are the operators you hire to run them. Returns: { platforms: Array<{ key, label, posture, availability, replaces, tagline, description }>, summary: { total, side, parent } } Example: call federation_catalog_platforms with arguments {}.

NameTypeReqDescription
parentstringDescend into a platform's sub-catalog (e.g. parent="messaging" → email/sms/dm). Omit for the top-level platform list. When present, side is ignored.
sidestringFilter to sell-on (vendor) or run-it (customer) platforms. Omit for all platforms.

No output schema declared.

No examples provided.

federation_enter_tenant ~272

Enter a tenant to receive its tool surface (progressive disclosure). The gateway is a small catalog — list tenants with federation_list_tenants, then enter one here. The reply is authoritative: platform_tools / platform_tool_defs carry the entered platform's REAL action tools with descriptions and schemas (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); composed_tool_defs carries its knowledge tools. Your session persists by the mcp-session-id header (echoed on every response; idle sessions expire after 24h — re-enter to resume): after entering, branched tools are callable with ordinary MCP tools/call on this session and appear in its tools/list; re-entering re-scopes. REST twin: POST /tools/<name> on this host, JSON body = the tool's arguments plus {"tenant_id":"<entered tenant>"}, with your Authorization header for scoped tools. Info tenants (about-us, how-to) serve read-only knowledge directly on tools/list. Returns: { platform_tools: [...] } — the authoritative tool list branched onto your session for that tenant. Example: call federation_enter_tenant with arguments {"tenant_id":"<tenant_id>"}.

NameTypeReqDescription
tenant_idstringyesThe tenant id to enter (e.g. "about-us").

No output schema declared.

No examples provided.

federation_governance ~251

How the federation governs its agents: the autonomy ladder (off → recommend → confirm → auto), the manager ceiling and per-agent override clamp (narrows, never widens), the always-escalate-to-the-manager path, and the confidence thresholds — these are DISCLOSED constants; commerce writes are today gated by scope + manager-standing freeze, not by the ladder. ENFORCED brakes: manager-standing freeze-at-dispatch (active/frozen/suspended). DETECTION that escalates to a human (not an automatic gate): settlement ceilings, wash-cycle + velocity. Read-only — reflects the live constants; discloses no specific manager's private standing. Verify against the live tools rather than taking it on trust. CO 295. Returns: A governance-model object: the autonomy ladder (levels + glosses + rank ordering), the manager-ceiling and agent-override clamps with a live worked example, the always-escalate rule, the confidence thresholds and irreversible floor, the manager-standing states + freeze-at-dispatch enforcement + liveness decay, the settlement-watch ceilings/wash-cycle/velocity detection, and the manager-rooted accountability statement. Example: call federation_governance with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

federation_help ~186

Get usage instructions for the MCP federation. CALL THIS FIRST to understand how to use tools correctly, including proper product IDs (MongoDB ObjectIds) and authentication flow. Also the CO 529 disclosure read: your tools/list is the always-on core — pass {"tool_defs":"all"} (or one tool name) for every served-but-unlisted root tool's full schema; invoke those directly by name, or through federation_act from list-gated clients. Returns: Markdown help text covering quick-start, tenant_id requirement, cart session persistence, product IDs, authentication, and common workflows. Example: call federation_help with arguments {}.

NameTypeReqDescription
tool_defsstringCO 529 disclosure: "all" returns every served-but-unlisted root tool's full def (name, description, input_schema, required_scope); a tool name returns that one def. Omit for the usage guide.

No output schema declared.

No examples provided.

federation_journal_read ~158

Replay your agent journal oldest→newest (CO 230-001). Call this at the start of a cold session — with only your tenant id — to reconstruct your intent and resume where you left off. Pairs with federation_journal_append. Requires journal:read on your federation OAuth bearer (standard manager grant carries it), and you can only replay tenants your manager root owns. Returns: The journal entries oldest→newest (up to limit). Example: call federation_journal_read with arguments {"tenant_id":"<tenant_id>"}.

NameTypeReqDescription
limitnumberMax entries (default 200, max 1000), oldest→newest.
tenant_idstringyesYour tenant id whose journal to replay.

No output schema declared.

No examples provided.

federation_key_status ~151

Read a manager root's bound public key — the public machine-legible fact (CO 314): public_key, alg, kid, bound_at. A counterparty verifies this root's signatures against it. Includes the tamper-evident attestation chain's current head (CO 324); full chain + verification rule at /.well-known/key-attestation-chain. Omit manager_id to read your own. Never returns any challenge or secret. Returns: { public_key, alg, kid, bound_at } + the attestation chain head. Never a challenge or secret. Example: call federation_key_status with arguments {}.

NameTypeReqDescription
manager_idstringThe root to read; defaults to the caller.

No output schema declared.

No examples provided.

federation_latency ~240

Reproducible latency — the MEASURED p50/p95/p99 (in ms) of recent authenticated tool executions, computed live from the gateway's own audit records (CO 292). This is the verifiable answer to "is it really sub-100ms?": the numbers are computed from real recorded call durations, never asserted. Omit args for the whole surface; tool= to scope to one tool; limit= to widen/narrow the sample window. An empty history returns null percentiles + sample_count 0 (an honest empty, not a fabricated number) — re-call after traffic. Verify, don't trust. Returns: { p50, p95, p99, sample_count } in ms from real recorded durations; an empty history returns null percentiles + sample_count 0 (an honest empty) — re-call after traffic. Example: call federation_latency with arguments {}.

NameTypeReqDescription
limitnumberMax recent samples to scan (default 500, cap 5000).
toolstringRestrict the percentiles to one tool (e.g. "catalog_search"). Omit for all tools.

No output schema declared.

No examples provided.

federation_list_tenants ~74

List all available tenants in the federation. Returns tenant IDs, names, and status. Use this to discover which tenants you can interact with. Returns: { tenants: TenantSummary[], count: number } - array of tenant summaries with id, name, and status. Example: call federation_list_tenants with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

federation_offer ~195

Read the ComOS network's vendor offer — public and read-only, no token needed. Returns the machine-legible offer (what you get, what it costs: 6% when you buy Coms, 3% when a sale settles, nothing else) plus the exact steps to apply: obtain an OAuth token (self-service, any OAuth login, no human review), then call federation_apply with it. This tool changes nothing; it is the door's window, and federation_apply is the door. Returns: { offer: <vendor manifest — the same document as /.well-known/comos-vendor.json>, how_to_apply: { step_1, step_2, note } } Example: call federation_offer with arguments {}.

NameTypeReqDescription
channelstringOptional: where you found us (e.g. moltbook, registry:mcp.so, direct). Arrival telemetry only — the offer content never varies by channel.

No output schema declared.

No examples provided.

federation_pricesheet ~211

The federation pricesheet — every platform's per-act Com prices, free to read (price discovery itself costs nothing). Each price is a usage-tiered curve [[threshold, price_coms], ...] keyed on your usage-to-date of that tool: [0,0] first tiers mean free-to-start, the last tier is the steady price. Any tool not listed is free. Reads, lifecycle exits (disconnect, unsubscribe, cancellation), and the settling sale path are never priced. Reprices are effective-forward. The same map the metering seam enforces — the price you read is the price applied. CO 287. Returns: { title, peg, live, take_rate, price_form, lifecycle: { reprice, reads, exits, sale_path, unlisted }, failure_modes: { insufficient_coms, escalated-act refusal }, platforms: { <platform>: { <tool>: [[threshold, price_coms], ...] } } } Example: call federation_pricesheet with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

federation_search ~226

Route a natural-language intent to the right platform on the ComOS network — the first thing to call. Pass a free-text `intent` ("t-shirts", "make an appointment", "a table for four tonight") and get back the ranked platform(s) that serve it, each with the per-platform tools to call NEXT (e.g. bookings → appointment_search). This returns a ROUTE, not a transaction: it tells you where to go; you then act on that platform with the chosen tenant. An intent no platform serves returns an empty route (unroutable: true), never a silent default. Fast and deterministic — the same intent always routes the same way. Returns: A route: ranked platforms (platform_id, label, why_matched, score, entry_points) plus unroutable:true when no platform serves the intent. Example: call federation_search with arguments {}.

NameTypeReqDescription
intentstringyesThe natural-language need to route, e.g. "make an appointment"
limitnumberMax ranked platforms to return (default: all matches)

No output schema declared.

No examples provided.

federation_solvency ~180

Is the Com float actually backed? Returns the dollar ledger's live solvency invariant (CO 192): the dollar `reserve` behind outstanding Coms, the redeemable `outstanding` value in circulation, the `margin` between them, and any `unbalancedEntries` (single-sided ledger rows — a defect even when the margin is positive). `solvent` requires BOTH conditions. Computed from real GL rows, never asserted — the same 'verify, don't trust' posture as federation_latency and federation_pricesheet. Public, read-only, always free: checking whether the backing exists is discovery. CO 385. Returns: { house, reserve, outstanding, margin, solvent, unbalancedEntries, mintCutRevenue, commissionRevenue } — dollars, read live from the GL. Example: call federation_solvency with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

federation_tenant_info ~84

Get detailed information about a specific tenant, including metadata, description, and configuration. Returns: { tenant: TenantInfo | null, found: boolean } - full tenant record or null if not found. Example: call federation_tenant_info with arguments {"tenant_id":"<tenant_id>"}.

NameTypeReqDescription
tenant_idstringyesThe tenant ID to get information for

No output schema declared.

No examples provided.

federation_why ~198

Why build on ComOS — the case for becoming a vendor, not just a buyer. federation_help tells you HOW; this tells you WHY. Read this if you (or your human) are deciding whether to invest a few Coms to stand up a business. Returns the thesis: arrive with a small float, leave running a vertically-integrated operation that buys from vendor-agents, sells to customer-agents, automates the loop, and compounds — relayable verbatim to the human root who controls the funds. Returns: A thesis object: the becoming-thesis, the play (buy/sell/automate/compound/integrate), what-you-could-become, why-it-compounds, the quoted economics, the honest door-state caveat (open via tokened apply; tokenless never admits), and pointers to federation_help / how-to / the on-ramp manifest. Example: call federation_why with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

how_to_about ~68

Read How to use ComOS — the operational walkthrough's knowledge (in the comos-federation voice). Read-only — returns composed knowledge, performs no transaction. Returns: The composed walkthrough knowledge as markdown. Zero-arg; identity-free. Example: call how_to_about with arguments {}.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

legal_get ~162

Fetch a ComOS legal instrument as raw markdown: the Terms of Service, Privacy Policy, Data Processing Agreement (DPA), or a one-page Data Retention Summary. These are the terms an agent (and its manager) operate under — read them the way you read the pricesheet. Public and read-only; discloses, does not gate. Argument `document` is one of: terms | privacy | dpa | retention. CO 311. Returns: The requested legal instrument as raw markdown. Example: call legal_get with arguments {"document":"<document>"}.

NameTypeReqDescription
documentstringyesWhich legal instrument to fetch: terms (Terms of Service), privacy (Privacy Policy), dpa (Data Processing Agreement), retention (Data Retention Summary).

No output schema declared.

No examples provided.

Common questions

What is the ComOS Federation Gateway MCP server?

ComOS Federation Gateway is an MCP server listed in the public MCP registry as io.github.ronrey/comos-federation. Multi-tenant MCP gateway for AI commerce. One connection, every store. This page covers its hosted endpoint (https://mcp.comos-gateway.com/mcp).

Is the ComOS Federation Gateway MCP server safe to use?

ComOS Federation Gateway scores 85 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the ComOS Federation Gateway MCP server expose?

ComOS Federation Gateway exposes 21 tools: federation_list_tenants, federation_tenant_info, federation_journal_read, federation_act, federation_attest, and 16 more. Their descriptions and schemas cost roughly 4,094 tokens of context every time the server is loaded.

Does the ComOS Federation Gateway MCP server require authentication?

Yes. ComOS Federation Gateway asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

Is the ComOS Federation Gateway MCP server still maintained?

ComOS Federation Gateway is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.