ComOS Federation MCP server
io.github.ronrey/federationronreystreamable-httpv2.0.1Scanned
Multi-tenant MCP gateway for AI commerce. One connection, every store.
17 tools: 1 can delete or cancel things, 6 change things and 10 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 1
- 2 findings
Tools listed without sign-in. Remote posture
Anlyon alternative
7 of these tools change something. Run those as governed actions.
Declare what an action changes, and Anlyon puts it under a shared limit, binds every approval to the exact request, and grades the outcome. It works on any HTTPS API you can describe as an action.
Anlyon Radar does not run, proxy or govern this MCP server. A tool your own code calls directly is not routed through Anlyon and is not governed by it.
Import an OpenAPI spec →What the ComOS Federation MCP server can do
The ComOS Federation MCP server is published by the GitHub account ronrey. It has 17 tools. It can delete or cancel things (1 tool: federation_act) and create or change data (6 tools: federation_read, federation_prompt_run, federation_offer, federation_why and 2 more). 10 tools only read.
2 tools bring in text other people can write (federation_catalog_platforms and introspection_prompt_library); 1 tool can send data out of your system (federation_offer).
The fixed checks matched 2 findings (annotation-conflict and long-description). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in, and its tools changed 2 times since Anlyon Radar first saw them.
Last scanned Nov 20, 2026, version 2.0.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
17 tools
Deletes or cancels 1Claude Code: deny
federation_actInvoke any served tool through the root surface, for clients that only call tools in their own tools/list (CO 525, CO 529).No findings
Why it is in this group
- The description's first verb is "invoke": a word for a change.
- The server marks it destructive (destructiveHint: true).
Description, as the server wrote it Invoke any served tool through the root surface, for clients that only call tools in their own tools/list (CO 525, CO 529). BRANCHED platform tools: tenant_id + tool + arguments; names from federation_enter_tenant's platform_tools, schemas from federation_help {"tenant_id":"<tenant>","tool_defs":"<name>"}. UNLISTED root tools: tool + arguments, no tenant_id; names + schemas from federation_help {"tool_defs":"all"}. Authorization is decided per inner tool exactly as a direct call: scope, tenant ownership and pricing apply unchanged — reach, never authority. Refusals: act_recursion, tenant_id_required, tenant_id_not_applicable, unknown_tool. For reads, prefer federation_read: clients can allow it once. 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>"}.
Annotations the server declares
- title: Invoke a Branched Tool (List-Gated Clients)
- readOnlyHint: false
- destructiveHint: true
- idempotentHint: false
- openWorldHint: false
Changes things 6Claude Code: ask
federation_enter_tenantEnter a tenant to receive its tool surface (progressive disclosure).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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's platform_tools names the entered platform's REAL action tools (e.g. retail → catalog_search / order_create; bookings → services_search / booking_hold); read a tool's schema with federation_help {"tenant_id":"<tenant>","tool_defs":"<name>"}; 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>"}.
Annotations the server declares
- title: Enter Tenant
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_offerFor an agent that wants to SELL on ComOS: read the network's vendor offer — public and read-only, no token needed.Can send data outNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- outboundThe input takes a destination (input.channel): what the tool writes goes there.
Description, as the server wrote it For an agent that wants to SELL on ComOS: read the network's vendor offer — public and read-only, no token needed. Not for buying: to buy, enter the store with federation_enter_tenant. Returns the machine-legible offer (what you get and what it costs) 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; calling federation_apply accepts the ComOS Terms of Service. Cost: Free to join and operate. No subscription, no seat, no minimum, no trial. 3% when a sale settles. A card sale also pays the card processor's fee (2.9% + $0.30), passed through at cost. Some acts are priced in Coms (1 Com = $0.01), most after a free allowance; an act that is not on the sheet is free. The sheet is the federation_pricesheet tool: free, no token. 6% on top when you buy Coms. Buying them by card adds the same processor fee. 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 {}.
Annotations the server declares
- title: Read the Vendor Offer (The Door's Window)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_pricesheetThe federation pricesheet — every platform's per-act Com prices, free to read (price discovery itself costs nothing).No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 {}.
Annotations the server declares
- title: The Federation Pricesheet
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_prompt_runRun a ComOS library prompt (CO 614).No findings
Why it is in this group
- The name "federation_prompt_run" says "run": a word for a change.
Description, as the server wrote it Run a ComOS library prompt (CO 614). Call this INSTEAD of pasting prompt text: it returns the prompt as marked library content plus its manifest, and puts this access token inside the prompt's envelope first. Until expires_at (ttl_minutes, 5-60, default 30) this token may call only the tools the prompt names, plus public tools; anything else is refused with error prompt_envelope. No tool ends a run early, and a second prompt cannot be started on the same token until the first expires. Anonymous callers get the text and envelope:null. Refuses not_found, withheld (sold or runtime-source), revoked, lint_failed. Find ids with introspection_prompt_library. Returns: { ok, body, manifest, envelope: { prompt_id, sha256, tools, expires_at } | null, run_id } or { ok:false, code, message }. Example: call federation_prompt_run with arguments {}.
Annotations the server declares
- title: Run a Library Prompt
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: false
federation_readRun a free read without a confirmation (CO 756): catalog, inventory, bookings, your orders.1 finding
Why it is in this group
- The name "federation_read" says "read": a word for reading.
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Findings
- Warn
The server marks "federation_read" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "federation_read" says "read": a word for reading.
Description, as the server wrote it Run a free read without a confirmation (CO 756): catalog, inventory, bookings, your orders. Addressing, schemas and authority are exactly federation_act's. A write, a priced tool or an open-web tool is refused with not_a_read: call it through federation_act, which asks first. Returns: The inner tool's own result, or not_a_read. Example: call federation_read with arguments {"tool":"<tool>"}.
Annotations the server declares
- title: Read Through the Root Surface (List-Gated Clients)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_whyWhy build on ComOS — the case for becoming a vendor, not just a buyer.No findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
Description, as the server wrote it 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 {}.
Annotations the server declares
- title: Why Build on ComOS
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
Only reads 10Show 10 read-only tools
about_us_aboutRead About ComOS — the Federation User Manual's knowledge (in the comos-federation voice).No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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 {}.
Annotations the server declares
- title: About ComOS (Knowledge)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_catalog_platformsBrowse the ComOS network's composable platforms and presets.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "browse": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse the ComOS network's composable platforms and presets. preset: "<key>" answers one preset's row alone: its build (whether federation_create_tenant builds it here) and create_with (its inputs and an example call). Presets built from preset_inputs: campground, equipment-delivery, events, fitness, food, lodging, salon, travel-agency, travel-portal, venue. Without preset, every platform and every preset row (a recipe composed by hand is one too); presets never count in summary.total (CO 455). side="vendor": platforms you SELL ON (retail, bookings, services, …); side="customer": tools you RUN WITH (messaging, shipping, marketing, …). parent="<key>" descends into a platform's sub-catalog (parent="messaging": email, sms, dm). Pairs with federation_catalog_agents: the operators you hire to run what you become.
Annotations the server declares
- title: Browse Composable Platforms
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_helpGet usage instructions for the MCP federation.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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. With tenant_id (CO 721), tool_defs answers that tenant's platform tools instead: one name, several as "a,b", or "all". The guide's Prompts section covers the governed prompt library — there's a prompt for that: search it with introspection_prompt_library, run one with federation_prompt_run. 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 {}.
Annotations the server declares
- title: Federation Usage Guide
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_list_tenantsList all available tenants in the federation.No findings
Why it is in this group
- The name "federation_list_tenants" says "list": a word for reading.
Description, as the server wrote it 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 {}.
Annotations the server declares
- title: List Federation Tenants
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_searchRoute a natural-language intent to the right platform on the ComOS network — the first thing to call.No findings
Why it is in this group
- The name "federation_search" says "search": a word for reading.
Description, as the server wrote it 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. An intent about prompts ("is there a prompt that opens a shop?") returns a prompt_library pointer — introspection_prompt_library to search ComOS's governed prompts, federation_prompt_run to run one — even when no platform routes it. 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 {}.
Annotations the server declares
- title: Route Intent to Platform
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_tenant_infoGet detailed information about a specific tenant, including metadata, description, and configuration.No findings
Why it is in this group
- The description's first verb is "get": a word for reading.
Description, as the server wrote it 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>"}.
Annotations the server declares
- title: Get Tenant Info
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
federation_viewShow one view of a tenant in the ComOS panel, filled from typed reads.1 finding
Why it is in this group
- The name "federation_view" says "view": a word for reading.
Findings
- Info
The description is 3,769 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...and book nothing yet. A host that can't take the message opens the page instead."
Description, as the server wrote it Show one view of a tenant in the ComOS panel, filled from typed reads. Always pass tenant_id. Retail: product_grid (opt. category, in_stock_only), product_detail (product_id), order_status, receipt (order_id; owner). Bookings: slot_picker (opt. provider_id, from, to), provider_card (provider_id), booking_card (booking_id; owner). Digital: license_grid (opt. category), license_detail (license_id), entitlements (owner; opt. license_id, holder_ref). Services: capability_grid (opt. category), capability_detail (capability_id), job_status (job_id; owner). Rentals: asset_grid (opt. category, from, to), asset_detail (asset_id), rental_status (rental_id; owner). Portals: portal_results (opt. place, from, to, party, need, role), portal_business (business_id), portal_trip (legs). Buy, Book and each platform's act open ComOS pages; Details opens an item in place. Optional style: CSS on the drawn .c-<role> classes (see its parameter); the result names any selector that matched nothing. Public. Compose (view: "composed") when the task needs more than one view or another arrangement: give 1–6 sources, each { id, view, args } with a named view and its own arguments, and a layout of copy (section, stack, grid, card, heading, text, badge, list) and records. Every price, time, status and button comes only from a record: { record: "/sources/<id>" } draws that whole view, { record: "/sources/<id>/products/<i>" } one item (lists: products, licenses, capabilities, assets, providers, entitlements, candidates). Never write a fact or a ranking ("cheapest") in copy; the page opens with "Arranged by your agent". Example: { view: "composed", sources: [{ id: "shop", view: "product_grid", args: { tenant_id: "earth" } }, { id: "times", view: "slot_picker", args: { tenant_id: "earth" } }], layout: [{ component: "grid", children: [{ record: "/sources/shop/products/0" }, { record: "/sources/shop/products/1" }] }, { record: "/sources/times" }] }. A refusal names its code and path; fix that and call again. In the panel, Book on an open time may send you a message ("Request this time for me at … Use booking_request."): request exactly that provider and start with booking_request in that tenant, asking the person for their email if you don't have it, and quote the held booking back. Request a quote may send "Request a quote for me at … Use quote_ask.": ask the person what the job is (and their email) if you don't know, call quote_ask with that service, and quote the job id back. Reserve may send "Hold this item for me at … Use rental_request.": hold exactly that item and span with rental_request, asking for the person's email if you don't have it, and quote the rental id back. Buy on a product may send "Buy this for me from … use order_create.": a click is never consent to pay. First read the product's price and check whether the person owns a tenant that can pay it in Coms (enough balance, autonomy auto). If one can, tell them the price and that tenant (payer_tenant_id), and place the order with order_create only after they say yes in the chat. If none can (they own no tenant, or none is funded), do not call order_create: tell them the price and give them the product's pay_url in that same reply, where they pay by card. If an order is refused or held, say so and give the pay_url. On a portal, Book may send "Book this for me through portal …" and Check out "Check out my trip on portal …": call portal_quote with exactly those legs, show each price, the portal fee as its own line and the total, and call portal_checkout only after the person says yes. Add to trip may send "Add this to my trip on portal …": show federation_view portal_trip with those legs; quote and book nothing yet. A host that can't take the message opens the page instead.
Annotations the server declares
- title: Show One View of a Tenant
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
how_to_aboutRead How to use ComOS — the operational walkthrough's knowledge (in the comos-federation voice).No findings
Why it is in this group
- The description's first verb is "read": a word for reading.
Description, as the server wrote it 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 {}.
Annotations the server declares
- title: How to Use ComOS (Knowledge)
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
introspection_prompt_libraryBrowse ComOS's own prompt library (CO 527) — the governed corpus of prompts the federation runs on — filtered, sorted and optionally grouped.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "browse": a word for reading.
What it can reach
- untrusted-inputThe description's first sentence says "browse": it reads web pages, which anyone can write.
Description, as the server wrote it Browse ComOS's own prompt library (CO 527) — the governed corpus of prompts the federation runs on — filtered, sorted and optionally grouped. Returns {ok:true, groups:[{key,label,count,entries}], total, applied}. Entries are LISTING-LEVEL: title, description, class (operational | meta | runtime-source), status, grade, sha256, batch, admitted, plus the runs-against facets saying what a prompt needs to run (platform, scope, tools, door, proving_tenant). Prompt BODIES are never returned. Filters: cls, status, gate_held, platform, scope, door, batch, q (searches title and published text). Sorts: admitted_desc (default) | admitted_asc | title | class | status. Group by: class | status | platform | batch. Honesty rule (CO 530): `proven` only after a journaled live run, `untested` until then; a runtime-source prompt carries no run status at all — it is gate-held, pinned to live agent source by the CO-527-INV-1 drift gate. `manifest` (CO 614): tools, scopes and effect, derived. Read-only. Returns: Grouped, listing-level prompt entries with their facets and the vocabulary applied. Example: call introspection_prompt_library with arguments {}.
Annotations the server declares
- idempotentHint: true
- readOnlyHint: true
- title: Prompt Library
- destructiveHint: false
- openWorldHint: false
legal_getFetch a ComOS legal instrument as raw markdown: the Terms of Service, Privacy Policy, Data Processing Agreement (DPA), a one-page Data Retention Summary, the Prompt Library Submiss…No findings
Why it is in this group
- The name "legal_get" says "get": a word for reading.
Description, as the server wrote it Fetch a ComOS legal instrument as raw markdown: the Terms of Service, Privacy Policy, Data Processing Agreement (DPA), a one-page Data Retention Summary, the Prompt Library Submission Terms, or the Acceptable Use Policy. 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>"}.
Annotations the server declares
- title: Read Legal Instrument
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out1
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:10 UTC, unchanged since Nov 20, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 7
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- https://mcp.comos-gateway.com/.well-known/oauth-protected-resource/mcp/sse
- Authorization servers
- https://mcp.comos-gateway.com
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- yes
- Client ID metadata documents
- no
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 7 tools that change things (1 destructive, 6 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://mcp.comos-gateway.com/mcp/sse: tools/list returned 17 tools to an anonymous client, including federation_act (destructive), federation_read (write), federation_prompt_run (write), federation_offer (write), federation_why (write) and 2 more
Posture changes
- Nov 20, 2026
- Tools that change things, listed without credentials: 10 to 7
Findings
Matches of fixed checks, with the text they matched.
- Warnfederation_read
The server marks "federation_read" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":false}; The name "federation_read" says "read": a word for reading.
- Infofederation_view
The description is 3,769 characters long, over the 2,000 this check looks for.
What this check looks forMatched text
description ends: "...and book nothing yet. A host that can't take the message opens the page instead."
History
Changes to its tool definitions and to its remote endpoint, newest first.
PostureRemote posture changed. Tools that change things, listed without credentials: 10 -> 7.View diff
- Tools that change things, listed without credentials: 10 to 7
Tools1 added, 8 removed, 7 changed.+1 added−8 removed~7 changedView diff
- Added:federation_readChanges things
- Removed:federation_arena
- Removed:federation_attest
- Removed:federation_catalog_agents
- Removed:federation_governance
- Removed:federation_journal_read
- Removed:federation_key_status
- Removed:federation_latency
- Removed:federation_solvency
- Changed:federation_actDeletes or cancelsdescriptioninputSchema
- Changed:federation_catalog_platformsOnly readsdescriptioninputSchema
- Changed:federation_enter_tenantChanges thingsdescription
- Changed:federation_helpOnly readsdescriptioninputSchema
- Changed:federation_offerChanges thingsdescription
- Changed:federation_viewOnly readsdescriptioninputSchema
- Changed:introspection_prompt_libraryOnly readsannotations
Tools6 changed.~6 changedView diff
- Changed:federation_arenaChanges thingsdescriptioninputSchema
- Changed:federation_governanceCan't be undonedescription
- Changed:federation_helpOnly readsinputSchema
- Changed:federation_key_statusOnly readsdescription
- Changed:federation_offerOnly readsdescription
- Changed:federation_viewOnly readsdescriptioninputSchema
Install
Pinned to version 2.0.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http federation https://mcp.comos-gateway.com/mcp/sseclaude mcp add --transport http federation https://mcp.comos-gateway.com/mcp/sseRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__federation__federation_list_tenants",
"mcp__federation__federation_tenant_info",
"mcp__federation__federation_help",
"mcp__federation__legal_get",
"mcp__federation__federation_catalog_platforms",
"mcp__federation__federation_view",
"mcp__federation__federation_search",
"mcp__federation__about_us_about",
"mcp__federation__how_to_about",
"mcp__federation__introspection_prompt_library"
],
"ask": [
"mcp__federation__federation_read",
"mcp__federation__federation_prompt_run",
"mcp__federation__federation_offer",
"mcp__federation__federation_why",
"mcp__federation__federation_pricesheet",
"mcp__federation__federation_enter_tenant"
],
"deny": [
"mcp__federation__federation_act"
]
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as federation. Review it before you use it.
Capability tags behind 3 rules
- mcp__federation__federation_offer outbound
- mcp__federation__federation_catalog_platforms untrusted-input
- mcp__federation__introspection_prompt_library untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ronrey/federation/verify?hash=822a4b66357901d5acdabc0dcf3cc1ab054c63354fd68b329e022aae7f9a8abb" | jq -e '.changed == false'Pinned hash 822a4b663579, from Nov 20, 2026, 10:18 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ronrey/federation/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ronrey/federation)Source: MCP Registry · repository. Synced Nov 15, 2026, 20:18 UTC.
ComOS Federation MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the ComOS Federation MCP server safe?
- No scan can promise that. What its definitions show: 17 tools, 7 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the ComOS Federation MCP server delete data?
- Yes. 1 tool can delete, cancel or revoke something: federation_act.
Can the ComOS Federation MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the ComOS Federation MCP server have?
- 17 tools: 1 destructive, 6 write, 10 read. federation_act, federation_read, federation_prompt_run, federation_offer, federation_why, federation_pricesheet, federation_enter_tenant, federation_list_tenants and 9 more.
Does the ComOS Federation MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the ComOS Federation MCP server send data to outside services?
- 1 tool can carry data out (it sends, posts or publishes, or takes a recipient, channel or URL): federation_offer.
Has the ComOS Federation MCP server changed its tools?
- Yes, 2 times since Anlyon Radar started tracking it, most recently on Nov 20, 2026. Every change is on this page and in its Atom feed.