What it does
claimscope is a local bridge to the hosted ECCA MCP server, a panel-style engine for examining claims and questions. The upstream server compares answers from its configured engines and shows where they disagree, runs adversarial pre-mortems and decision tournaments, and verifies candidate answers written by other AIs. For psychology, learning, nutrition and money questions, it fetches scholarly studies and grades the evidence before giving a verdict. The bridge holds no answers and grades nothing; it serves the upstream tool list and returns upstream results unchanged.
Someone might reach for it to test a question against several engines instead of relying on one model's reply, to stress-test a plan by simulating how it could fail, to score discrete options under minimax regret, or to check a candidate answer against independent panel agreement. It also exposes a shape-only validator for ecca.claim-protocol 1.0 documents, and separate tools for refining rough questions and fetching graded research for a given niche.
It runs as an MCP server over stdio, as a CLI in which each tool takes one JSON argument string, or as a Docker container whose default command starts the MCP server. The upstream endpoint can be overridden with ECCA_MCP_URL. If ECCA_API_KEY is set, it is sent as a bearer token on every upstream request; otherwise no auth header is sent. The session opens on the first tool call. Failures come back as an isError result whose text starts with "claimscope error:". The test suite runs against a stubbed upstream.
Limitations and requirements
Every tool call is forwarded to the upstream hosted service at eccaai.com by default, so results depend on that endpoint being reachable. The upstream's own tool descriptions refer to "keyed tier-quota slots"; this client adds no quota or payment handling of its own. An API key is optional and is sent only when ECCA_API_KEY is set. The CLI exits with code 1 on an isError result and code 2 on a usage error.
Safety
Our team has not reviewed this resource. Only automated rules checked it; resources with high-risk signals are not published. These are signals, not a guarantee that installing it is safe. Try it in a sandbox project first.
- Runs code or changes an assistant's behaviour
Sources
- Official MCP Registry first seen 13 Nov 2026 · last seen 13 Nov 2026 · its page on the source
io.github.CloudCorpRecords/claimscope
Compare engine answers, inspect disagreement and grade study evidence for questions.
v0.1.0As shown on registry.modelcontextprotocol.io when we last read it