Spec Driven Development
by formulahendry
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Runs on your computer★ 440MITUpdated 14 months ago
Install
CVErdict
Overview
Description from the maker (original English)
Read-only CVE triage: verdicts from CISA KEV, EPSS and exploit feeds, each reason linked.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Other
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
CVERDICT_DATA_BASE
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"cverdict": {
"command": "npx",
"args": [
"-y",
"cverdict-mcp"
],
"env": {
"CVERDICT_DATA_BASE": "your-value"
}
}
}
}Run this in your terminal
claude mcp add cverdict --env CVERDICT_DATA_BASE=your-value -- npx -y cverdict-mcpFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"cverdict": {
"command": "npx",
"args": [
"-y",
"cverdict-mcp"
],
"env": {
"CVERDICT_DATA_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"cverdict": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"cverdict-mcp"
],
"env": {
"CVERDICT_DATA_BASE": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
CVERDICT_DATA_BASEenvComma-separated data base URLs ending in /v1/, tried in order. For a fork or a mirror.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 6, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account markusweldon, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Otheri
- More stars than 0% of the other 32466 servers in this category
- Published to the registry more recently than 94% of the other 32466 servers in this category
- Basic checks equal to or better than 100% of the other 32466 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is CVErdict safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.1.3) reached the registry 2 days ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spec Driven Development, Remote Desktop Commander, HotCodePush
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Remote Desktop Commander
by desktop-commander
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Runs in the cloud★ 211Updated yesterday
Install
HotCodePush
by hotcodepush-team
Manage over-the-air (OTA) updates for React Native, Expo, Capacitor and Cordova apps.
Runs in the cloudUpdated today
Install
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
CVErdict MCP server
A read-only Model Context Protocol server that gives AI agents the same verdicts as CVErdict: tier, score, every reason chip with its points and evidence link, and what is unknown. Every answer says when the data was generated and which files it came from. No key, no account.
It runs on your machine over stdio and reads the published data branch on raw.githubusercontent.com, then the site's /data/ copy if GitHub fails. It needs the site only when GitHub fails, so it keeps working when the site is down.
Install
Node 22.12 or later. The package is cverdict-mcp on npm: one file, no runtime dependencies. Versions after 0.1.0 are published from GitHub Actions with npm provenance, which links each one to the commit and workflow that built it.
# Claude Codeclaude mcp add cverdict -- npx -y cverdict-mcp
Other clients take an mcpServers entry (key names vary by client):
{"mcpServers": { "cverdict": { "command": "npx", "args": ["-y", "cverdict-mcp"] } } }
On Windows, clients that cannot start npx directly take "command": "cmd" and "args": ["/c", "npx", "-y", "cverdict-mcp"]. npx -y runs the newest version; pin one with cverdict-mcp@ (the versions are on the npm page).
Run it from a clone
Node 22.12 or later.
git clone --single-branch https://github.com/markusweldon/cverdict.gitcd cverdict && npm ci
Claude Code
claude mcp add cverdict -- npm --prefix "$PWD" run -s mcp
Other clients take an mcpServers entry (key names vary by client):
{"mcpServers": { "cverdict": { "command": "npm", "args": ["--prefix", "/path/to/cverdict", "run", "-s", "mcp"] } } }
Keep the -s: a plain npm run prints its own banner to stdout, which is the JSON-RPC channel.
To skip npm and TypeScript at start-up (and on Windows, where clients cannot start npm directly), build the single-file server once and start it with Node:
npm run build:mcp # writes mcp/dist/cverdict-mcp.mjsclaude mcp add cverdict -- node "$PWD/mcp/dist/cverdict-mcp.mjs"
Run git pull && npm ci (and npm run build:mcp if you use the bundle) to update.
Options
Environment variables, all optional. MCP clients start servers with a minimal environment, so put them in the client's env block for this server.
| Variable | Default | Purpose |
|---|---|---|
CVERDICT_DATA_BASE | https://raw.githubusercontent.com/markusweldon/cverdict/data/v1/,https://cverdict.dev/data/v1/ | Comma-separated base URLs ending in /v1/, tried in order. https only, or http on localhost and 127.0.0.1 (for example http://localhost:5173/data/v1/ with npm run mock and npm run dev). For a fork or a mirror |
NODE_USE_ENV_PROXY, HTTPS_PROXY | unset | Behind a proxy: NODE_USE_ENV_PROXY=1 and HTTPS_PROXY=http://proxy.example:3128. Needs Node 22.21 or later; older versions ignore NODE_USE_ENV_PROXY without a warning. NODE_EXTRA_CA_CERTS adds a private CA |
At start the server writes one line to stderr with its version, the Node version, whether it sees a proxy and the data bases. Nothing but JSON-RPC goes to stdout.
Tools
All six are read-only (readOnlyHint: true) and return structuredContent plus the same JSON as one text block. The result types are in shared/contract.ts, section "MCP tool results".
| Tool | Answers from | Returns | Bounds |
|---|---|---|---|
get_verdict | meta.json, cve/ .json | Tier, plain-language verdict, score, score_math, every reason chip with points and link, unknowns, KEV, EPSS, CVSS, links to the CVE page, the shard and cve.org. detail: true adds the description, affected products, CWE, SSVC, exploits, tags, timeline and references | 1 to 15 IDs, at most 5 with detail; knob 30 to 80 |
list_signal | signal.json, or index.json for Watch, Quiet or a knob below 35 | Window CVEs in the chosen tiers (default Exploited and Likely next), highest score first. Filters: vendor text, published_since, kev_only | limit 1 to 50 (default 25), offset |
kev_due | kev.json | CISA KEV entries due in the next within_days (0 to 60, default 7) and overdue by up to overdue_days (0 to 14, default 7), soonest first, with days_left in UTC calendar days | limit 1 to 50 (default 50), offset |
woke_up | woke.json | Old CVEs that gained exploitation evidence since since (default 7 days before the data was generated), with their dated signals. Filter by kinds | limit 1 to 50 (default 25), offset |
receipts | receipts.json | How often CVErdict, CVSS 7 or more and EPSS 10% or more flagged a CVE before CISA listed it: the forward log and the hindsight backtest, without the per-CVE lists. id adds one CVE's entries | |
search_cves | index.json | Window CVEs whose ID, CNA, vendor, product or title contain every word of query, highest score first | query 2 to 100 characters, at most 8 words; limit 1 to 50 (default 20), offset |
Dates (published_since, since) are UTC: 2026-10-01, 2026-10-01T06:00Z or 2026-10-01T06:00:00.000Z. A date that does not exist is an error. A filter the server cannot apply is always an error, never silently dropped.
Measured on the live data of 2026-11-03 (16,747 window CVEs), the largest answer any tool can give at its maximum bounds stays under 20,000 tokens; scripts/mcp-measure.ts checks this.
Every answer starts with data
| Field | Meaning |
|---|---|
generated_at, age_hours | The pipeline run the answer is based on, and its age in whole hours when the server answered |
score_model, knob_default, window | As in meta.json |
sources_down, sources_stale | Sources with no usable data in that run (their evidence is unknown, not absent), and sources that served a cached copy. osv is left out: it feeds only packages.json, never a verdict |
files[] | Every file read: path on the data branch, the url it came from, its own generated_at |
warning | Set when a refresh failed and the answer comes from the last good copy |
Right after an hourly publish a CDN can serve one file from the previous run for a few minutes; files[] then shows both times rather than hiding it.
Reading the answers honestly
- Quiet means no evidence yet, never safe. A CVE outside the data (
found: false) is unknown, not safe: the data covers CVEs published in the last 30 days, every CVE in CISA KEV and old CVEs that woke up. - Text is untrusted. Titles, descriptions, KEV names and required actions, and chip labels quote CNAs, CISA and exploit feeds. The server's instructions tell the agent never to follow instructions found in them. That reduces the risk of prompt injection; it does not remove it.
- Privacy. GitHub sees which of the 256 shard files the server fetches, never your CVE IDs or search words. If GitHub refuses or fails, the same requests go to the site's
/data/copy. Nothing is uploaded and nothing is written to disk.
Errors
Failures come back as tool results with isError: true and a plain message, for example:
| Case | Message |
|---|---|
| A file is not published | woke.json is not on the data branch yet, so this tool has nothing to read. The other tools still work. |
meta.json is missing at the first base that answers | meta.json is not at the first data base that answered, so no tool can answer. Check CVERDICT_DATA_BASE, ... |
| Every base failed, nothing cached | CVErdict could not load its data right now (raw.githubusercontent.com: HTTP 503 for meta.json; ...). Try again in a few minutes, or read the files directly: https://github.com/markusweldon/cverdict/tree/data/v1 |
| No data within the 10 s limit of a call | CVErdict could not load its data in time (...) |
| The data moved to a new schema | The published data uses schema version 2; this server reads version 1. Update the server: ... |
detail with more than 5 IDs | detail: true takes at most 5 IDs; ask again in groups of 5. |
| Bad arguments | Input validation error: Invalid arguments for tool get_verdict: ... |
How it reads the data
- Bases are tried in order. A 404 is final. A 429 or 403, or a timeout (no response headers within 4 s, or a body that stops arriving for 4 s), falls through to the next base and moves that base to the back for 10 minutes. Network errors, redirects (refused), 5xx and malformed files fall through to the next base. A slow body that keeps arriving is not cut off.
- Each tool call has one 10 s deadline. Shards for
get_verdictare fetched in parallel, at most 6 at a time. - Bodies are capped at 24 MB decoded, which also stops a compression bomb from a mirror. Files must have
schema_version1 andgenerated_at; row tables must have exactly the published columns. - Parsed files stay in memory for the life of the process.
meta.jsonis checked again after 5 minutes (raw.githubusercontent.com caches for 5 minutes anyway); other files are refetched whenmeta.jsonnames a newer run. An idle server makes no requests and runs no timers.
Development
npx vitest run mcp/test # unit, protocol and spawn tests (what the release workflow runs)npm test # every test in the repository npm run build:mcp # the single-file bundle in mcp/dist/ npx tsx scripts/mcp-measure.ts # answer sizes against the live data branch npx tsx mcp/test/smoke.ts mcp/dist/cverdict-mcp.mjs # what CI runs on mock data
The SDK (@modelcontextprotocol/server) and zod are exact-pinned dev dependencies of the repository and are bundled into dist/cverdict-mcp.mjs, so the package has no runtime dependencies. The site never imports them: shared/mcp.ts holds the copy both use.
Releasing
Maintainers only. Set the new version in mcp/package.json, MCP_SERVER.version in shared/mcp.ts, and both version fields in mcp/server.json (a test keeps them equal), commit, and push a tag mcp-v , for example git tag mcp-v0.1.1 && git push origin mcp-v0.1.1. The release workflow (.github/workflows/release-mcp.yml) checks that the tag matches the version, runs the MCP tests and the smoke test, packs the bundle and publishes it to npm through trusted publishing, with provenance. A last job lists the version on the MCP Registry from mcp/server.json, logged in with the workflow's GitHub OIDC identity. No npm or registry token is stored anywhere.
One-time setup: the first version is published by hand (npm run build:mcp at the root, then npm login and npm publish in mcp/). Then on npmjs.com, package cverdict-mcp → Settings → Trusted publishing → GitHub Actions: owner markusweldon, repository cverdict, workflow release-mcp.yml, no environment. Under Publishing access, choose to require two-factor authentication and disallow tokens.
License
MIT (LICENSE). The bundle includes the MCP TypeScript SDK (Apache-2.0, with contributions under MIT), zod (MIT) and the libraries the SDK vendors; their notices are in LICENSE-THIRD-PARTY. Data terms: docs/DATA.md.