Dev error explainers
NPM · DEV-ERROR-EXPLAINERS · SCANNED OCT 3
Offline, deterministic cause and fix for Node, npm, Next.js, CORS and Postgres URL errors.
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
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to mahdibrr/dev-error-explainers). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability66
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 559 tokens (~559/item across 1 items; 1 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 Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
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 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 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
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
How do I install the Dev error explainers MCP server?
Dev error explainers runs locally as an npm package, launched with npx -y dev-error-explainers. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · dev-error-explainers
claude mcp add mahdibrr-dev-error-explainers -- npx -y dev-error-explainers
{
"mcpServers": {
"mahdibrr-dev-error-explainers": {
"command": "npx",
"args": [
"-y",
"dev-error-explainers"
]
}
}
} {
"servers": {
"mahdibrr-dev-error-explainers": {
"command": "npx",
"args": [
"-y",
"dev-error-explainers"
]
}
}
} codex mcp add mahdibrr-dev-error-explainers -- npx -y dev-error-explainers
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"mahdibrr-dev-error-explainers": {
"type": "local",
"command": [
"npx",
"-y",
"dev-error-explainers"
],
"enabled": true
}
}
} openclaw mcp add mahdibrr-dev-error-explainers --command npx --arg -y --arg dev-error-explainers
mcp_servers:
mahdibrr-dev-error-explainers:
command: "npx"
args: ["-y", "dev-error-explainers"] {
"McpServers": {
"mahdibrr-dev-error-explainers": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"dev-error-explainers"
]
}
}
} assistant mcp add mahdibrr-dev-error-explainers -t stdio -c npx -a -y dev-error-explainers
{
"mcpServers": {
"mahdibrr-dev-error-explainers": {
"command": "npx",
"args": [
"-y",
"dev-error-explainers"
]
}
}
} 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.
- 1 Oct 26 +15
- Malware scan: unverified → pass ▲ security
- 30 Sept 26 64
First indexed and scored.
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 3 Oct 2026 · Analysed npm/dev-error-explainers@0.2.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 | mahdibrr/dev-error-explainers |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/mahdibrr/dev-error-explainers/.github/workflows/release.yml@refs/tags/v0.2.0 |
| Rekor log index | 3017613149 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:759dfbe737ffd13970f9433149789268fdfdb29f7ce8a411e3477f3ea984ac39e55f6802b4b73291b1e11dd62f08ebe9d30b416df87eed62c47421982 |
Background: How many MCP packages publish verified provenance →
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 →
explain_error Explain a developer error ~483
Explain a concrete developer error message or log excerpt and return its documented cause and fix. Call it when the user pastes (or you captured from a terminal/browser console) an actual error, for example: - Node.js ESM/CommonJS errors: ERR_REQUIRE_ESM, ERR_MODULE_NOT_FOUND, "Cannot use import statement outside a module", "require is not defined in ES module scope". - npm ERESOLVE / peer-dependency conflict logs from npm install. - Next.js `next build` / `next dev` output (module not found, heap out of memory, server/client component errors, prerender failures). - Browser CORS console errors ("has been blocked by CORS policy", preflight, Access-Control-Allow-Origin). - A postgres:// or postgresql:// connection string (DATABASE_URL, Supabase pooler/direct URLs) that fails to connect. - Postgres connection errors from Node.js apps: connect ECONNREFUSED / ETIMEDOUT on 5432, getaddrinfo ENOTFOUND, Prisma P1000/P1001/P1017, "password authentication failed", "no pg_hba.conf entry", "too many clients", self-signed certificate. Pass the raw text verbatim, including the stack trace and the "Node.js vX" footer when present; do not paraphrase it. Returns a short human-readable diagnosis (cause, why, ranked fixes with code, official source links) plus the same result as structured JSON. If nothing is recognised it answers "No known error recognised — nothing guessed"; then rely on your own reasoning. Fully offline and deterministic: no network, no LLM, same input gives the same output. Secrets it can recognise (URL passwords, Bearer/Basic tokens, JWTs, token/key query parameters) are masked in the output.
| Name | Type | Req | Description |
|---|---|---|---|
| client | string | – | Optional database client for connection-string advice (default prisma). |
| error | string | yes | The raw error message or log excerpt, verbatim (max ~200 KB). Include the lines around the error: stack trace, npm log block, "Node.js vX" footer, or the full connection string. |
| node_version | string | – | Optional Node.js version in use (e.g. "20.10.0"), used to tailor ESM/CommonJS advice. Usually detected from the error text itself. |
| Name | Type | Req | Description |
|---|---|---|---|
| engine | string | yes | The code path that produced the diagnosis (src/contract.js). |
| matched | boolean | yes | True when at least one explainer recognised the input. |
| redactions | integer | yes | Number of values masked in the output. |
| results | array | yes | One Diagnosis per finding, most severe first (docs/CONTRACT.md); empty when matched is false. |
| tool | string | yes | Always "dev-error-explainers". |
| version | string | yes | Package version that produced the result. |
No examples provided.
What is the Dev error explainers MCP server?
Dev error explainers is an MCP server listed in the public MCP registry as io.github.mahdibrr/dev-error-explainers. Offline, deterministic cause and fix for Node, npm, Next.js, CORS and Postgres URL errors. This page covers its npm package (dev-error-explainers).
Is the Dev error explainers MCP server safe to use?
Dev error explainers scores 79 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 3 October 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 Dev error explainers MCP server expose?
Dev error explainers exposes 1 tool: explain_error. Their descriptions and schemas cost roughly 483 tokens of context every time the server is loaded.
Is the Dev error explainers MCP server still maintained?
Dev error explainers is still listed as active in the MCP registry. We last reached this channel on 3 October 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 Dev error explainers MCP server under?
Dev error explainers declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.