CheckMCP
‹ directory
78MCP SCORE
C

federated

https://mcp.polarisray.com/federated
4 tools~1.9k tok/req0% annot.proto 2024-11-05
View public page ›
Xin
Raw JSON ›

Score by pillar

Security ·20100
Tool design ·18100
Schemas / desc ·1666
Reliability ·1480
Context-cost ·1273
Compliance ·1245
Coverage ·850

reliability: LOW (T1 single-shot, not credited - requires T3 >=24h)

Context-cost

1.9ktokens for tools/list

Paid on every request. Lean footprint for 4 tools.

this server1.9k
median≈ 3k

MCP primitive coverage

the quality score covers tools
4
Tools
0
Resources · none
0
Prompts · none

Why this score — causal attribution

Each penalty: measure → mechanism → effect → Δscore.

Schemas / desc · HIGH−5.4

0% typed+described params → schema = the contract the agent fills in → more malformed calls

Compliance · MEDIUM−3.6

0 declared annotations → destructiveHint/openWorldHint missing -> worst-case defaults → the tool is treated as destructive & open-world by clients

Compliance · MEDIUM−1.6

proto 2024-11-05 (4 rev. behind 2025-11-25) → outdated protocol version → recent features unavailable, recent clients weakened

Compliance · MEDIUM−1.2

capability 'resources' declared but resources/list empty → capabilities inconsistent with real behavior → clients misled

Compliance · MEDIUM−1.2

capability 'prompts' declared but prompts/list empty → inconsistent capabilities → clients misled

Compliance · LOW−0.6

no OAuth discovery (.well-known missing) → RFC 9728/8414 not exposed → auth not auto-discoverable by clients

Badge — paste it in your README

MCP Score badge — federated[![MCP Score](https://checkmcp.dev/badge/mcp-polarisray-com.svg?url=https%3A%2F%2Fmcp.polarisray.com%2Ffederated)](https://checkmcp.dev/report?url=https%3A%2F%2Fmcp.polarisray.com%2Ffederated)
Own this server?Get verified — fresh re-audit, badge if you pass ›

About federated — FAQ

Is the federated MCP server safe to use?+
CheckMCP audited federated and gave it an MCP Score of 78/100 (grade C) — moderate — some quality or security gaps worth reviewing. The audit runs an OWASP MCP Top 10 security pass (tool poisoning, hardcoded secrets, command injection, the lethal trifecta) against the live endpoint; see the per-pillar breakdown and the "why this score" attribution on this page, and re-audit anytime at checkmcp.dev.
What is the MCP Score of federated?+
federated scores 78/100 (grade C) on CheckMCP's vendor-neutral audit across six weighted pillars — security, tool design, schemas, context-cost, compliance and coverage — with reliability measured and shown but not yet credited.
How many tools does federated expose, and what is its context cost?+
federated exposes 4 tools, and its tools/list response costs roughly 1.9k tokens — paid on every request your agent makes to it. Lower is better for your context budget.
How was federated scored?+
By probing the live MCP endpoint (https://mcp.polarisray.com/federated), inspecting its tools, schemas and protocol compliance, running an OWASP MCP Top 10 security pass, and measuring the token cost of tools/list — then attributing every penalty as measure → mechanism → effect. The methodology is open: checkmcp.dev/#methodology.