e18e
NPM · @E18E/MCP · 2 COMPONENTS · SCANNED SEP 20
The official e18e MCP server keeping your agent in check from installing bloated dependencies.
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
- No install/post-install scripts declared.Pass
- 1 of 12 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency84
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to e18e/mcp). View diagnostics → Pass
- License check failed: no license is declared. See how to fix → Fail
- Actively maintained (last published 31 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1983 tokens (~15/item across 131 items; 3 tools + 128 resources), lean.Pass
- 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.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 current MCP spec version (2026-07-28).Pass
How do I install the e18e MCP server?
e18e runs locally as an npm package, launched with npx -y @e18e/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @e18e/mcp
claude mcp add dev-e18e-e18e -- npx -y @e18e/mcp
{
"mcpServers": {
"dev-e18e-e18e": {
"command": "npx",
"args": [
"-y",
"@e18e/mcp"
]
}
}
} {
"servers": {
"dev-e18e-e18e": {
"command": "npx",
"args": [
"-y",
"@e18e/mcp"
]
}
}
} codex mcp add dev-e18e-e18e -- npx -y @e18e/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"dev-e18e-e18e": {
"type": "local",
"command": [
"npx",
"-y",
"@e18e/mcp"
],
"enabled": true
}
}
} openclaw mcp add dev-e18e-e18e --command npx --arg -y --arg @e18e/mcp
mcp_servers:
dev-e18e-e18e:
command: "npx"
args: ["-y", "@e18e/mcp"] {
"McpServers": {
"dev-e18e-e18e": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@e18e/mcp"
]
}
}
} assistant mcp add dev-e18e-e18e -t stdio -c npx -a -y @e18e/mcp
{
"mcpServers": {
"dev-e18e-e18e": {
"command": "npx",
"args": [
"-y",
"@e18e/mcp"
]
}
}
} 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
- Security disclosure: unverified → fail ▼ functional
- Stability: pass → 0.80 functional
- 18 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 16 Sept 26 −1
- Stability: pass → 0.93 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- Security disclosure: unverified → fail ▼ functional
- 13 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.
- 12 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 11 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 npm/@e18e/mcp@0.0.11
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 | e18e/mcp |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/e18e/mcp/.github/workflows/release.yml@refs/heads/main |
| Rekor log index | 2514180602 |
| Predicate type | https://slsa.dev/provenance/v1 |
| Subject digest | sha512:79f483e52751407fd385eca9a12ad752a58d13d3fd26fb5b4c928587bace21cadf0b5c8a7f09e741fe3de7cb99eca3dfd33919b764b659ef93b8f287e |
Background: How many MCP packages publish verified provenance →
Dependencies 12 packages
| Packages resolved | 12 |
|---|---|
| Stale | 1 |
| 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 →
code-checker Check if the code contains some inefficient or outdated packages imported and suggests alternatives. ~35
Check if the code contains some inefficient or outdated packages imported and suggests alternatives.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code to check. |
| Name | Type | Req | Description |
|---|---|---|---|
| suggestions | array | yes | – |
No examples provided.
lookup-replacement Check if a package has a more performant, maintained or efficient replacement by package name, replacement text, or topic. Returns a list of suggestions with descriptions and documentation links. ~77
Check if a package has a more performant, maintained or efficient replacement by package name, replacement text, or topic. Returns a list of suggestions with descriptions and documentation links.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | The package name, replacement text, or topic to search for, e.g. `chalk`, `filter`, or `Array.prototype.map`. |
| Name | Type | Req | Description |
|---|---|---|---|
| results | array | yes | – |
No examples provided.
npm-i-checker Check for outdated or insecure npm packages in an install script like `npm i` or `pnpm add` or `yarn add` or `bun i`. ~87
Check for outdated or insecure npm packages in an install script like `npm i` or `pnpm add` or `yarn add` or `bun i`.
| Name | Type | Req | Description |
|---|---|---|---|
| command | string | yes | The install command to check, e.g. `npm i express lodash` or `pnpm add express lodash` or `yarn add express lodash` or `bun i express lodash`. |
| Name | Type | Req | Description |
|---|---|---|---|
| suggestions | array | yes | – |
No examples provided.
What is the e18e MCP server?
e18e is an MCP server listed in the public MCP registry as dev.e18e/e18e. The official e18e MCP server keeping your agent in check from installing bloated dependencies. This page covers its npm package (@e18e/mcp).
Is the e18e MCP server safe to use?
e18e scores 91 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 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 e18e MCP server expose?
e18e exposes 3 tools: code-checker, lookup-replacement, npm-i-checker. Their descriptions and schemas cost roughly 199 tokens of context every time the server is loaded.
Is the e18e MCP server still maintained?
e18e 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.