io.github.CloudCorpRecords/claimscope
NPM · @RENETURCIOS/CLAIMSCOPE · 2 COMPONENTS
Compare engine answers, inspect disagreement and grade study evidence for questions.
Available components
Last scanned (10 hours ago)
Scores higher than 35% of npm servers
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 30 of 92 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 833 tokens (~69/item across 12 items; 12 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management3
- Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "ecca_pre_mortem" implies "execute" and declares no destructiveHint at all, which the MCP spec reads as destructive by default. See how to fix → Fail
- An AI judge read all 12 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
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.
- 5 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 0 to 3. That category is still filling its 30-day observation window: 0 days of observed history at the previous scan, 1 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Nov 26 67
First indexed and scored.
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 5 Nov 2026 · Analysed npm/@reneturcios/claimscope@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 92 packages
| Packages resolved | 92 |
|---|---|
| Stale | 30 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
ecca_bts_divergence Measure Answer Divergence ~46
Measures lexical and semantic divergence across candidate assertions to penalize sycophancy.
| Name | Type | Req | Description |
|---|---|---|---|
| assertions | array | yes | Array of candidate assertions or claims to measure divergence for. |
No output schema declared.
No examples provided.
ecca_claim_protocol_validate Validate a Claim Protocol Document ~88
Check one ecca.claim-protocol 1.0 document for shape: versioned, engine slots only (no vendor names), split causes from the published taxonomy, question text only with consent, seal present. Returns ok with the error list; validates shape, never the record behind it.
| Name | Type | Req | Description |
|---|---|---|---|
| document | object | yes | The protocol document to check (docs/CLAIM_PROTOCOL.md). |
No output schema declared.
No examples provided.
ecca_decision_tournament Compare Decision Options ~58
Evaluates multi-option decision matrix using minimax regret and Pareto ranking over candidate pathways.
| Name | Type | Req | Description |
|---|---|---|---|
| decisionContext | string | yes | Context of the decision to evaluate. |
| options | array | yes | List of discrete options or strategic pathways. |
No output schema declared.
No examples provided.
ecca_learning Check a Learning Question ~60
Learning and study skills: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The learning / study-skills question to research and give a verdict on. |
No output schema declared.
No examples provided.
ecca_money Check a Money Question ~57
Money and business: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The money / business question to research and give a verdict on. |
No output schema declared.
No examples provided.
ecca_nutrition Check a Nutrition Question ~59
Nutrition and supplements: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The nutrition / supplements question to research and give a verdict on. |
No output schema declared.
No examples provided.
ecca_pre_mortem Run a Pre-Mortem ~68
Executes an adversarial pre-mortem identifying failure modes and early warning indicators using empirical argument verification.
| Name | Type | Req | Description |
|---|---|---|---|
| horizonMonths | integer | – | Time horizon in months to simulate forward failure modes. |
| premise | string | yes | The strategic plan, architecture, or business premise to stress-test. |
No output schema declared.
No examples provided.
ecca_psychology Check a Psychology Question ~56
Psychology research: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.
| Name | Type | Req | Description |
|---|---|---|---|
| question | string | yes | The psychology question to research and give a verdict on. |
No output schema declared.
No examples provided.
ecca_refine Refine a Question ~57
Use one keyed tier-quota slot to sharpen rough student questions without adding facts; return detected niches and refinement chips. A closed engine ceiling falls back locally.
| Name | Type | Req | Description |
|---|---|---|---|
| text | string | yes | The rough question or text to refine and sharpen. |
No output schema declared.
No examples provided.
ecca_research Research Supporting Studies ~76
Use one keyed tier-quota slot and dispatch-ceiling reservation to fetch and grade studies from scholarly indexes; return fetched evidence and explicit gaps.
| Name | Type | Req | Description |
|---|---|---|---|
| niche | string | – | Subject niche to focus the research on: psychology, learning, nutrition or money. |
| question | string | yes | The research question to fetch and grade studies for. |
No output schema declared.
No examples provided.
ecca_synthesize Compare Engine Answers ~147
Compare answers from configured engines and inspect disagreement, with lexical similarity and final-answer agreement when measurable.
| Name | Type | Req | Description |
|---|---|---|---|
| antagonist | boolean | – | When true, forces one engine to act as adversarial red-team antagonist. |
| depth | string | – | intuitive and fast route to one engine; executive, pioneer and deep route a multi-engine dispatch (free callers: two engines first, expanding on measured divergence, one deep solve per day). Any othe… |
| model | string | – | Label echoed in the result. Every value dispatches through the same registered engines; depth decides fast or multi-engine. |
| query | string | yes | The core inquiry, hypothesis, or decision challenge to synthesize. |
No output schema declared.
No examples provided.
ecca_verify Verify Another AI Answer ~61
Independently answer a question and compare the candidate against deterministic panel agreement. Show named dissent; spends one solve.
| Name | Type | Req | Description |
|---|---|---|---|
| candidate_answer | string | yes | The candidate answer to verify against the panel. |
| question | string | yes | The question the candidate answer responds to. |
No output schema declared.
No examples provided.
How do I install the io.github.CloudCorpRecords/claimscope MCP server?
io.github.CloudCorpRecords/claimscope runs locally as an npm package, launched with npx -y @reneturcios/claimscope. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @reneturcios/claimscope
claude mcp add cloudcorprecords-claimscope -- npx -y @reneturcios/claimscope
What is the io.github.CloudCorpRecords/claimscope MCP server?
io.github.CloudCorpRecords/claimscope is an MCP server listed in the public MCP registry as io.github.CloudCorpRecords/claimscope. Compare engine answers, inspect disagreement and grade study evidence for questions. This page covers its npm package (@reneturcios/claimscope).
Is the io.github.CloudCorpRecords/claimscope MCP server safe to use?
io.github.CloudCorpRecords/claimscope scores 68 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. 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 io.github.CloudCorpRecords/claimscope MCP server expose?
io.github.CloudCorpRecords/claimscope exposes 12 tools: ecca_synthesize, ecca_pre_mortem, ecca_decision_tournament, ecca_bts_divergence, ecca_refine, and 7 more. Their descriptions and schemas cost roughly 833 tokens of context every time the server is loaded.
Is the io.github.CloudCorpRecords/claimscope MCP server still maintained?
io.github.CloudCorpRecords/claimscope is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.CloudCorpRecords/claimscope MCP server under?
io.github.CloudCorpRecords/claimscope declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.