Evidrift
NPM · EVIDRIFT · SCANNED SEP 21
Catch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI.
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 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
- 6 of 18 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency100
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to bm1016bm-svg/evidrift). View diagnostics → Pass
- Clear OSI-approved license (MPL-2.0).Pass
- Actively maintained (last published 56 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability76
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 336 tokens (~168/item across 2 items; 2 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 Management87
- Stability observed for 26 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 Evidrift MCP server?
Evidrift runs locally as an npm package, launched with npx -y evidrift. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · evidrift
claude mcp add bm1016bm-svg-evidrift -- npx -y evidrift
{
"mcpServers": {
"bm1016bm-svg-evidrift": {
"command": "npx",
"args": [
"-y",
"evidrift"
]
}
}
} {
"servers": {
"bm1016bm-svg-evidrift": {
"command": "npx",
"args": [
"-y",
"evidrift"
]
}
}
} codex mcp add bm1016bm-svg-evidrift -- npx -y evidrift
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bm1016bm-svg-evidrift": {
"type": "local",
"command": [
"npx",
"-y",
"evidrift"
],
"enabled": true
}
}
} openclaw mcp add bm1016bm-svg-evidrift --command npx --arg -y --arg evidrift
mcp_servers:
bm1016bm-svg-evidrift:
command: "npx"
args: ["-y", "evidrift"] {
"McpServers": {
"bm1016bm-svg-evidrift": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"evidrift"
]
}
}
} assistant mcp add bm1016bm-svg-evidrift -t stdio -c npx -a -y evidrift
{
"mcpServers": {
"bm1016bm-svg-evidrift": {
"command": "npx",
"args": [
"-y",
"evidrift"
]
}
}
} 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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.
- 19 Sept 26 −3
- Stability: pass → 0.80 functional
- 18 Sept 26 0
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 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 0
- Stability: 0.97 → pass security
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 21 Sept 2026 · Analysed npm/evidrift@0.4.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | bm1016bm-svg/evidrift |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/bm1016bm-svg/evidrift/.github/workflows/release.yml@refs/tags/v0.4.0 |
| Rekor log index | 2255739818 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:f067b7ca2b8bc980521078f0151413e425529989dcc9cdfc3cd45f9fe8cc7bb4cf608a181f32a9540a637251b8a23cfd9f9db31db7da4bed62e82e70a |
Background: How many MCP packages publish verified provenance →
Dependencies 18 packages
| Packages resolved | 18 |
|---|---|
| Stale | 6 |
| 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 →
evidrift_record Record deterministic TypeScript evidence ~181
Resolve an actually installed dependency and create a content-addressed Evidrift receipt. When affectedCodeLine points at an overloaded call, TypeScript selects the real call-site signature. The tool records evidence only; it never declares the receipt verified or the code correct.
| Name | Type | Req | Description |
|---|---|---|---|
| affectedCodeLine | integer | – | Optional 1-based affected source line. |
| affectedCodePath | string | yes | Repository-relative source file affected by the claim. |
| claim | string | yes | Human claim explaining why this evidence matters. |
| overload | integer | – | Optional 1-based overload selector used only when recording an overloaded symbol. |
| packageName | string | yes | Installed npm dependency name. |
| parameter | string | – | Optional parameter name that must exist. |
| projectRoot | string | – | Repository-relative directory containing the consuming package.json. |
| symbol | string | yes | Exported callable TypeScript symbol. |
No output schema declared.
No examples provided.
evidrift_record_json_pointer Record deterministic JSON Pointer evidence ~134
Read one repository-local JSON file, resolve an RFC 6901 pointer, and create a content-addressed Evidrift receipt. No URL, command, package code, or LLM is invoked.
| Name | Type | Req | Description |
|---|---|---|---|
| affectedCodeLine | integer | – | Optional 1-based affected source line. |
| affectedCodePath | string | yes | Repository-relative source file affected by the claim. |
| claim | string | yes | Human claim explaining why this JSON contract matters. |
| jsonPath | string | yes | Repository-relative `.json` source path. |
| pointer | string | yes | RFC 6901 JSON Pointer. An empty string selects the document root. |
No output schema declared.
No examples provided.
What is the Evidrift MCP server?
Evidrift is an MCP server listed in the public MCP registry as io.github.bm1016bm-svg/evidrift. Catch TypeScript API and OpenAPI contract drift in AI-generated code, then revalidate it in CI. This page covers its npm package (evidrift).
Is the Evidrift MCP server safe to use?
Evidrift scores 93 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Evidrift MCP server expose?
Evidrift exposes 2 tools: evidrift_record, evidrift_record_json_pointer. Their descriptions and schemas cost roughly 315 tokens of context every time the server is loaded.
Is the Evidrift MCP server still maintained?
Evidrift is still listed as active in the MCP registry. We last reached this channel on 21 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 Evidrift MCP server under?
Evidrift declares the MPL-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.