# io.github.CloudCorpRecords/claimscope (oci · ghcr.io/cloudcorprecords/claimscope)

Compare engine answers, inspect disagreement and grade study evidence for questions.

- Trust score: 38/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- npm · `@reneturcios/claimscope`: 68/100, [markdown](https://verifymcp.io/servers/cloudcorprecords-claimscope/reneturcios-claimscope.md), [page](https://verifymcp.io/servers/cloudcorprecords-claimscope/reneturcios-claimscope)
- oci · `ghcr.io/cloudcorprecords/claimscope`: 38/100 (this document), [markdown](https://verifymcp.io/servers/cloudcorprecords-claimscope/ghcr-io-cloudcorprecords-claimscope.md), [page](https://verifymcp.io/servers/cloudcorprecords-claimscope/ghcr-io-cloudcorprecords-claimscope)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/cloudcorprecords/claimscope`
- Version: `0.1.0`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Supply Chain Security**: 0/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 833 tokens (~69/item across 12 items; 12 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability observed for 1 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 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.
  - An AI judge read all 12 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**Unverified: 1 category.** A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

## Install

### How do I install the io.github.CloudCorpRecords/claimscope MCP server?

io.github.CloudCorpRecords/claimscope runs locally as a container image, launched with docker run --rm -i ghcr.io/cloudcorprecords/claimscope:0.1.0. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add cloudcorprecords-claimscope -- docker run --rm -i ghcr.io/cloudcorprecords/claimscope:0.1.0
```

### Cursor

```json
{
  "mcpServers": {
    "cloudcorprecords-claimscope": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/claimscope:0.1.0"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "cloudcorprecords-claimscope": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/claimscope:0.1.0"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add cloudcorprecords-claimscope -- docker run --rm -i ghcr.io/cloudcorprecords/claimscope:0.1.0
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "cloudcorprecords-claimscope": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/claimscope:0.1.0"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  cloudcorprecords-claimscope:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/cloudcorprecords/claimscope:0.1.0"]
```

### Netclaw

```json
{
  "McpServers": {
    "cloudcorprecords-claimscope": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/claimscope:0.1.0"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "cloudcorprecords-claimscope": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/cloudcorprecords/claimscope:0.1.0"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-05 (score 38, 0)

- [security regression] Provenance: unverified → fail

### 2026-11-04 (score 38)

First indexed and scored.

## MCP tools (12)

### `ecca_synthesize` (~147 tokens)

Compare Engine Answers

Compare answers from configured engines and inspect disagreement, with lexical similarity and final-answer agreement when measurable.

Input parameters:

- `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, required): The core inquiry, hypothesis, or decision challenge to synthesize.

### `ecca_pre_mortem` (~68 tokens)

Run a Pre-Mortem

Executes an adversarial pre-mortem identifying failure modes and early warning indicators using empirical argument verification.

Input parameters:

- `horizonMonths` (integer): Time horizon in months to simulate forward failure modes.
- `premise` (string, required): The strategic plan, architecture, or business premise to stress-test.

### `ecca_decision_tournament` (~58 tokens)

Compare Decision Options

Evaluates multi-option decision matrix using minimax regret and Pareto ranking over candidate pathways.

Input parameters:

- `decisionContext` (string, required): Context of the decision to evaluate.
- `options` (array, required): List of discrete options or strategic pathways.

### `ecca_bts_divergence` (~46 tokens)

Measure Answer Divergence

Measures lexical and semantic divergence across candidate assertions to penalize sycophancy.

Input parameters:

- `assertions` (array, required): Array of candidate assertions or claims to measure divergence for.

### `ecca_refine` (~57 tokens)

Refine a Question

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.

Input parameters:

- `text` (string, required): The rough question or text to refine and sharpen.

### `ecca_research` (~76 tokens)

Research Supporting Studies

Use one keyed tier-quota slot and dispatch-ceiling reservation to fetch and grade studies from scholarly indexes; return fetched evidence and explicit gaps.

Input parameters:

- `niche` (string): Subject niche to focus the research on: psychology, learning, nutrition or money.
- `question` (string, required): The research question to fetch and grade studies for.

### `ecca_verify` (~61 tokens)

Verify Another AI Answer

Independently answer a question and compare the candidate against deterministic panel agreement. Show named dissent; spends one solve.

Input parameters:

- `candidate_answer` (string, required): The candidate answer to verify against the panel.
- `question` (string, required): The question the candidate answer responds to.

### `ecca_psychology` (~56 tokens)

Check a Psychology Question

Psychology research: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

Input parameters:

- `question` (string, required): The psychology question to research and give a verdict on.

### `ecca_learning` (~60 tokens)

Check a Learning Question

Learning and study skills: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

Input parameters:

- `question` (string, required): The learning / study-skills question to research and give a verdict on.

### `ecca_nutrition` (~59 tokens)

Check a Nutrition Question

Nutrition and supplements: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

Input parameters:

- `question` (string, required): The nutrition / supplements question to research and give a verdict on.

### `ecca_money` (~57 tokens)

Check a Money Question

Money and business: refine the question, fetch studies, and show named claims before the verdict. Applies evidence and claims checks; spends one solve.

Input parameters:

- `question` (string, required): The money / business question to research and give a verdict on.

### `ecca_claim_protocol_validate` (~88 tokens)

Validate a Claim Protocol Document

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.

Input parameters:

- `document` (object, required): The protocol document to check (docs/CLAIM_PROTOCOL.md).

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/cloudcorprecords-claimscope/ghcr-io-cloudcorprecords-claimscope#diagnostics

## Score history

- 2026-11-05: 38
- 2026-11-04: 38

## Common questions

### 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 container image (ghcr.io/cloudcorprecords/claimscope).

### Is the io.github.CloudCorpRecords/claimscope MCP server safe to use?

io.github.CloudCorpRecords/claimscope scores 38 out of 100 on VerifyMCP. 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.

## Links

- GitHub Container Registry: https://ghcr.io/cloudcorprecords/claimscope
- Repository: https://github.com/CloudCorpRecords/claimscope
- Changelog RSS feed: https://verifymcp.io/servers/cloudcorprecords-claimscope/ghcr-io-cloudcorprecords-claimscope.xml
- Changelog JSON feed: https://verifymcp.io/servers/cloudcorprecords-claimscope/ghcr-io-cloudcorprecords-claimscope.json
- HTML version of this page: https://verifymcp.io/servers/cloudcorprecords-claimscope/ghcr-io-cloudcorprecords-claimscope