# io.github.Correctover/ccs (npm · ccs-mcp-server)

Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts.

- Trust score: 73/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-25

## Components

- npm · `ccs-mcp-server`: 73/100 (this document), [markdown](https://verifymcp.io/servers/correctover-ccs/ccs-mcp-server.md), [page](https://verifymcp.io/servers/correctover-ccs/ccs-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `ccs-mcp-server`
- Version: `1.2.7`
- 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-09-25.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 6/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (Elastic-2.0) isn't a recognized OSI-approved license.
  - Actively maintained (last published 4 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 562 tokens (~112/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 69% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 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.

## Install

### How do I install the io.github.Correctover/ccs MCP server?

io.github.Correctover/ccs runs locally as an npm package, launched with npx -y ccs-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add correctover-ccs -- npx -y ccs-mcp-server
```

### Cursor

```json
{
  "mcpServers": {
    "correctover-ccs": {
      "command": "npx",
      "args": [
        "-y",
        "ccs-mcp-server"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "correctover-ccs": {
      "command": "npx",
      "args": [
        "-y",
        "ccs-mcp-server"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add correctover-ccs -- npx -y ccs-mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "correctover-ccs": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "ccs-mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add correctover-ccs --command npx --arg -y --arg ccs-mcp-server
```

### Hermes

```yaml
mcp_servers:
  correctover-ccs:
    command: "npx"
    args: ["-y", "ccs-mcp-server"]
```

### Netclaw

```json
{
  "McpServers": {
    "correctover-ccs": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "ccs-mcp-server"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add correctover-ccs -t stdio -c npx -a -y ccs-mcp-server
```

### Other

```json
{
  "mcpServers": {
    "correctover-ccs": {
      "command": "npx",
      "args": [
        "-y",
        "ccs-mcp-server"
      ]
    }
  }
}
```

## 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-09-25 (score 73, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-22 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 67, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-10 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `verify_tool_call` (~167 tokens)

Verify an AI agent tool call against CCS 7 dimensions (Structure, Schema, Security, Identity, Integrity, Latency, Cost) plus semantic attack-chain analysis and math overflow detection. Returns verdict (allowed/denied) with detailed findings. DEFAULT MODE BLOCKS UNSAFE CALLS.

Input parameters:

- `arguments` (object): Tool call arguments to verify
- `caller` (object): Caller identity, e.g. {agent_id: 'agent-001'}
- `metadata` (object): Optional metadata (execution_time_us, cost, request_id, etc.)
- `policy` (object): Optional CCS policy override (allowed_tools, denied_tools, mode, budgets, etc.)
- `tool` (string, required): Tool name as namespace.action, e.g. 'shell.exec' or 'read.file'

### `issue_evidence` (~84 tokens)

Issue a CCS evidence record for a tool call. Evidence is cryptographically bound (content_hash + evidence_hash), tamper-evident, independently verifiable. Issued for allowed AND denied calls.

Input parameters:

- `arguments` (object)
- `caller` (object, required)
- `metadata` (object)
- `policy` (object)
- `tool` (string, required)

### `audit_mcp_config` (~56 tokens)

Audit an MCP client/server configuration JSON for security risks: plain HTTP, weak secrets, disabled TLS, missing commands. Returns structured issues with severity.

Input parameters:

- `config` (object, required): MCP configuration JSON (e.g. Claude Desktop config)

### `verify_intent_binding` (~107 tokens)

Verify that actual tool call arguments match a declared intent with zero tolerance. Catches cross-model parameter drift (planner says amount=100, executor writes amount=10000). No LLM needed — pure deterministic comparison. Supports exact match, numeric tolerance, and regex pattern binding modes.

Input parameters:

- `arguments` (object, required): Actual tool call arguments
- `intent` (object, required): Structured intent declaration from the agent framework
- `tool` (string, required): Tool being called, e.g. payments.send

### `verify_receipt` (~148 tokens)

Offline-verify a CCS Ed25519-signed receipt. Auditors call this with a receipt JSON produced by issue_evidence or verify_intent_binding; it checks the signature against the embedded signer_public_key and reports whether the body was tampered with. Optionally pin an expected signer public key (PEM string or sha256: fingerprint) to reject receipts from untrusted signers.

Input parameters:

- `expected_signer` (string): Optional. Either the expected PEM public key, or a sha256:<hex> fingerprint of the DER SPKI public key.
- `receipt` (object, required): The signed receipt object (must include signer_public_key, signature_alg, signature, and the signed body fields).

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/correctover-ccs/ccs-mcp-server#diagnostics

## Score history

- 2026-09-25: 73
- 2026-09-24: 72
- 2026-09-23: 72
- 2026-09-22: 72
- 2026-09-21: 71
- 2026-09-20: 71
- 2026-09-19: 70
- 2026-09-18: 70
- 2026-09-17: 69
- 2026-09-16: 69
- 2026-09-15: 68
- 2026-09-14: 68
- 2026-09-13: 67
- 2026-09-12: 67
- 2026-09-11: 66
- 2026-09-10: 66
- 2026-09-09: 65
- 2026-09-08: 62
- 2026-09-07: 62
- 2026-09-06: 62
- 2026-09-05: 62
- 2026-09-04: 62
- 2026-09-03: 62
- 2026-09-02: 47

## Common questions

### What is the io.github.Correctover/ccs MCP server?

io.github.Correctover/ccs is an MCP server listed in the public MCP registry as io.github.Correctover/ccs. Runtime verification MCP server: fail-closed checks for agent tool calls, signed evidence receipts. This page covers its npm package (ccs-mcp-server).

### Is the io.github.Correctover/ccs MCP server safe to use?

io.github.Correctover/ccs scores 73 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 25 September 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.Correctover/ccs MCP server expose?

io.github.Correctover/ccs exposes 5 tools: verify_tool_call, issue_evidence, audit_mcp_config, verify_intent_binding, verify_receipt. Their descriptions and schemas cost roughly 562 tokens of context every time the server is loaded.

### Is the io.github.Correctover/ccs MCP server still maintained?

io.github.Correctover/ccs is still listed as active in the MCP registry. We last reached this channel on 25 September 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.Correctover/ccs MCP server under?

io.github.Correctover/ccs declares the Elastic-2.0 licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/ccs-mcp-server
- Socket report: https://socket.dev/npm/package/ccs-mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/correctover-ccs/ccs-mcp-server.xml
- Changelog JSON feed: https://verifymcp.io/servers/correctover-ccs/ccs-mcp-server.json
- HTML version of this page: https://verifymcp.io/servers/correctover-ccs/ccs-mcp-server