# io.github.BrienBounded/evr (pypi · evidence-readiness)

Checks agent traces for evidence-readiness: verifies evidence is present, not that it is true.

- Trust score: 81/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- pypi · `evidence-readiness`: 81/100 (this document), [markdown](https://verifymcp.io/servers/brienbounded-evr/evidence-readiness.md), [page](https://verifymcp.io/servers/brienbounded-evr/evidence-readiness)

## Channel facts

- Registry: `pypi`
- Package: `evidence-readiness`
- Version: `0.1.2`
- 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-20.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it.
  - No production dependencies, so there is no dependency health to assess.
- **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 (Apache-2.0).
  - Actively maintained (last published 38 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 650 tokens (~216/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 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**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.BrienBounded/evr MCP server?

io.github.BrienBounded/evr runs locally as a PyPI package, launched with uvx evidence-readiness. 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 brienbounded-evr -- uvx evidence-readiness
```

### Cursor

```json
{
  "mcpServers": {
    "brienbounded-evr": {
      "command": "uvx",
      "args": [
        "evidence-readiness"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "brienbounded-evr": {
      "command": "uvx",
      "args": [
        "evidence-readiness"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add brienbounded-evr -- uvx evidence-readiness
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "brienbounded-evr": {
      "type": "local",
      "command": [
        "uvx",
        "evidence-readiness"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add brienbounded-evr --command uvx --arg evidence-readiness
```

### Hermes

```yaml
mcp_servers:
  brienbounded-evr:
    command: "uvx"
    args: ["evidence-readiness"]
```

### Netclaw

```json
{
  "McpServers": {
    "brienbounded-evr": {
      "Transport": "stdio",
      "Command": "uvx",
      "Arguments": [
        "evidence-readiness"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add brienbounded-evr -t stdio -c uvx -a evidence-readiness
```

### Other

```json
{
  "mcpServers": {
    "brienbounded-evr": {
      "command": "uvx",
      "args": [
        "evidence-readiness"
      ]
    }
  }
}
```

## 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-19 (score 81, −3)

- [functional] Stability: pass → 0.80

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

- [security] Stability: 0.97 → pass

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

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

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

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

### 2026-09-12 (score 81, −3)

- [functional] Stability: pass → 0.80

### 2026-09-11 (score 84, +1)

- [security] Stability: 0.97 → pass

### 2026-09-09 (score 83, +1)

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

### 2026-09-07 (score 82, +1)

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

## MCP tools (3)

### `check_trace_readiness` (~254 tokens)

Check an agent execution trace against the evidence-readiness specification and report, per requirement, whether the evidence a post-hoc causal reconstruction would need is met, partially met, or unmet — naming the specific missing field and the span kind it belongs on. Accepts a file/directory path OR inline JSON content (exactly one). Runs entirely locally in this process; nothing is transmitted or persisted, and inline content is processed in memory only. This tool NEVER determines whether a failure occurred: it answers "does this trace contain what a reconstruction of class X would require," never "did class X occur." A fabricated-but-internally-consistent trace passes. This tool verifies evidence is present, not that it is true, and its result must never be relayed as "this agent is safe".

Input parameters:

- `require_class` (array): Fold these classes' evidence requirements into the exit code (choices: config_drift, session_isolation_failure, cascade_contamination, prompt_injection).
- `trace_content` (string): A trace document as a JSON string, checked in memory and never written to disk.
- `trace_path` (string): Path to a trace .json file or a directory of traces (*manifest.json excluded).

### `get_requirement` (~152 tokens)

Return one evidence-readiness requirement by ID (for example EVR-R3 or EVR-PI-7): its title, the published field forms, the span kind the evidence belongs on, its spec section, and — for prompt_injection — which attribution tiers include it. Requirements state what must be PRESENT in a trace; the spec is not an enumeration of everything the reconstruction engine reads, so no inference can be drawn from a field's absence. This tool verifies evidence is present, not that it is true, and its result must never be relayed as "this agent is safe".

Input parameters:

- `requirement_id` (string, required): A requirement ID, e.g. EVR-R1, EVR-CD-4.

### `list_class_requirements` (~178 tokens)

List the evidence requirements for one failure class (config_drift, session_isolation_failure, cascade_contamination, prompt_injection), or pass "universal" for the requirements every trace must meet (EVR-R1..R6). States which items are required versus supporting, and for prompt_injection the per-tier evidence sets. tool_misuse returns its documented negative result (investigated and declined), not an error. Requirements state what must be PRESENT; nothing may be inferred about fields the spec does not name. This tool verifies evidence is present, not that it is true, and its result must never be relayed as "this agent is safe".

Input parameters:

- `class_name` (string, required): One of: config_drift, session_isolation_failure, cascade_contamination, prompt_injection, universal, tool_misuse.

## Diagnostics

Captured diagnostic sections: Provenance, Install scripts, Dependencies. The full working is on the page: https://verifymcp.io/servers/brienbounded-evr/evidence-readiness#diagnostics

## Score history

- 2026-09-20: 81
- 2026-09-19: 81
- 2026-09-18: 84
- 2026-09-17: 83
- 2026-09-16: 83
- 2026-09-15: 82
- 2026-09-14: 82
- 2026-09-13: 81
- 2026-09-12: 81
- 2026-09-11: 84
- 2026-09-10: 83
- 2026-09-09: 83
- 2026-09-08: 82
- 2026-09-07: 82
- 2026-09-06: 81
- 2026-09-05: 81
- 2026-09-04: 81
- 2026-09-03: 80
- 2026-09-02: 80
- 2026-09-01: 79
- 2026-08-31: 79
- 2026-08-30: 78
- 2026-08-29: 78
- 2026-08-28: 77
- 2026-08-27: 77
- 2026-08-26: 76
- 2026-08-25: 75
- 2026-08-24: 74
- 2026-08-23: 74
- 2026-08-22: 73

## Common questions

### What is the io.github.BrienBounded/evr MCP server?

io.github.BrienBounded/evr is an MCP server listed in the public MCP registry as io.github.BrienBounded/evr. Checks agent traces for evidence-readiness: verifies evidence is present, not that it is true. This page covers its PyPI package (evidence-readiness).

### Is the io.github.BrienBounded/evr MCP server safe to use?

io.github.BrienBounded/evr scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. 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.BrienBounded/evr MCP server expose?

io.github.BrienBounded/evr exposes 3 tools: check_trace_readiness, get_requirement, list_class_requirements. Their descriptions and schemas cost roughly 584 tokens of context every time the server is loaded.

### Is the io.github.BrienBounded/evr MCP server still maintained?

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

io.github.BrienBounded/evr declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- PyPI project: https://pypi.org/project/evidence-readiness/
- Socket report: https://socket.dev/pypi/package/evidence-readiness
- Repository: https://github.com/evidence-readiness/spec
- Changelog RSS feed: https://verifymcp.io/servers/brienbounded-evr/evidence-readiness.xml
- Changelog JSON feed: https://verifymcp.io/servers/brienbounded-evr/evidence-readiness.json
- HTML version of this page: https://verifymcp.io/servers/brienbounded-evr/evidence-readiness