federation_latency — ComOS Federation MCP Tool
federation_latency
(federation latency) is one of 21 tools on the
ComOS Federation
MCP server. Connect the server and your client discovers it on the handshake.
by client
How to call federation_latency from your client
- Claude Code ComOS Federation federation_latency run in your project directory
- Claude Desktop ComOS Federation federation_latency ~/Library/Application Support/Claude/claude_desktop_config.json
- Cursor ComOS Federation federation_latency ~/.cursor/mcp.json
- VS Code ComOS Federation federation_latency .vscode/mcp.json
- Zed ComOS Federation federation_latency ~/.config/zed/settings.json
- Windsurf ComOS Federation federation_latency ~/.codeium/windsurf/mcp_config.json
- Cline ComOS Federation federation_latency ~/Library/Application Support/Code/User/globalStorage/saoudrizwan.claude-dev/settings/cline_mcp_settings.json
- Gemini CLI ComOS Federation federation_latency ~/.gemini/settings.json
- Grok ComOS Federation federation_latency .mcp.json (in your project root)
- ChatGPT ComOS Federation federation_latency Settings → Connectors → Advanced → Developer mode
- Claude.ai ComOS Federation federation_latency Settings → Connectors → Add custom connector
- LangChain ComOS Federation federation_latency pip install langchain-mcp-adapters
Fastest route
claude mcp add --transport http federation https://mcp.comos-gateway.com/mcp/sseOther tools on this server
- federation_list_tenants
- federation_tenant_info
- federation_journal_read
- federation_act
- federation_attest
- federation_key_status
- federation_offer
- federation_help
- federation_why
- federation_governance
- legal_get
- federation_pricesheet
- federation_catalog_platforms
- federation_catalog_agents
- federation_arena
- federation_solvency
- federation_search
- federation_enter_tenant
- about_us_about
- how_to_about
This list was read from the server itself, by connecting to it and calling tools/list on 24 September 2026. It is what
the server actually exposes, not what its listing claims.
Mutating and Read-only are read off each tool's name, not its schema — a hint, not a guarantee. The registry stores tool names only; connect the server for its live schemas.