io.github.BrienBounded/evr
PYPI · EVIDENCE-READINESS · SCANNED SEP 20
Checks agent traces for evidence-readiness: verifies evidence is present, not that it is true.
Available components
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 Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
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 (Apache-2.0).Pass
- Actively maintained (last published 38 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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
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.
pypi · evidence-readiness
claude mcp add brienbounded-evr -- uvx evidence-readiness
{
"mcpServers": {
"brienbounded-evr": {
"command": "uvx",
"args": [
"evidence-readiness"
]
}
}
} {
"servers": {
"brienbounded-evr": {
"command": "uvx",
"args": [
"evidence-readiness"
]
}
}
} codex mcp add brienbounded-evr -- uvx evidence-readiness
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"brienbounded-evr": {
"type": "local",
"command": [
"uvx",
"evidence-readiness"
],
"enabled": true
}
}
} openclaw mcp add brienbounded-evr --command uvx --arg evidence-readiness
mcp_servers:
brienbounded-evr:
command: "uvx"
args: ["evidence-readiness"] {
"McpServers": {
"brienbounded-evr": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"evidence-readiness"
]
}
}
} assistant mcp add brienbounded-evr -t stdio -c uvx -a evidence-readiness
{
"mcpServers": {
"brienbounded-evr": {
"command": "uvx",
"args": [
"evidence-readiness"
]
}
}
} 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.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 −3
- Stability: pass → 0.80 functional
- 11 Sept 26 +1
- Stability: 0.97 → pass security
- 9 Sept 26 +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.
- 7 Sept 26 +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.
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 20 Sept 2026 · Analysed pypi/evidence-readiness@0.1.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| 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 →
check_trace_readiness ~254
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".
| Name | Type | Req | Description |
|---|---|---|---|
| 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). |
No output schema declared.
No examples provided.
get_requirement ~152
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".
| Name | Type | Req | Description |
|---|---|---|---|
| requirement_id | string | yes | A requirement ID, e.g. EVR-R1, EVR-CD-4. |
No output schema declared.
No examples provided.
list_class_requirements ~178
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".
| Name | Type | Req | Description |
|---|---|---|---|
| class_name | string | yes | One of: config_drift, session_isolation_failure, cascade_contamination, prompt_injection, universal, tool_misuse. |
No output schema declared.
No examples provided.
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.