Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Verify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
You need
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": {
"agent-guard": {
"command": "npx",
"args": [
"-y",
"@liminallablibs/agent-guard-mcp"
]
}
}
}Run this in your terminal
claude mcp add agent-guard -- npx -y @liminallablibs/agent-guard-mcpPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"agent-guard": {
"command": "npx",
"args": [
"-y",
"@liminallablibs/agent-guard-mcp"
]
}
}
}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.
Paste into .vscode/mcp.json in your project
{
"servers": {
"agent-guard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"@liminallablibs/agent-guard-mcp"
]
}
}
}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.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
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 7, 2026
The registry name was verified with the GitHub account liminalpepe, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
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.
The registry does not list a required key, though some servers ask you to sign in on first use.
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).
The GitHub repo last changed –, and the latest version (0.2.1) reached the registry 4 months ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Signoff
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
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
Five gates that make an agent's 'done' provable: run them, read the verdict, audit the record.
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.
One line: Verify-before-act safety for AI agents — check packages, lockfiles, skill manifests, and CI workflows *before* install or merge. Zero API keys. Zero config.
Scores Cursor/Claude skill manifests + GitHub Actions workflows — not just npm dependencies.
| When you… | Call |
|---|---|
npm install foo / agent suggests a new dep | check_package |
| Review an LLM-generated lockfile | verify_lockfile |
| Install a Cursor skill or MCP plugin | score_manifest |
Merge a PR touching .github/workflows/* | check_workflow |
Call these *before* installing a dependency, merging a CI change, or installing a third-party skill/plugin — so an agent refuses hallucinated packages, typosquats, poisoned manifests, and compromised CI actions.
Exposes four MCP tools (also available as a plain HTTP service):
| Tool | Use before… | Returns | |
|---|---|---|---|
check_package | adding a single npm/PyPI dependency | OK / SUSPICIOUS / DANGER + typosquat/slop flags | |
verify_lockfile | running npm/pip/yarn install | scans every direct + transitive dep in a lockfile | |
score_manifest | installing a Cursor/Claude skill or MCP/Smithery plugin | poison-signature + scope-overreach + drift score 0–100 | |
check_workflow | merging a PR that touches CI | flags mutable action pins, compromised actions, curl\ | bash, pwn-requests, secret exposure |
AI agents routinely hallucinate package names (slopsquatting), trust LLM-generated lockfiles, install unvetted skill packs, and pin CI actions to mutable tags. Each is a live supply-chain vector. This server gives an agent a cheap "is this safe?" call before it acts.
{
"mcpServers": { "agent-guard": { "command": "npx", "args": ["-y", "@liminallablibs/agent-guard-mcp@0.2.1"] } } }
Before installing any npm/PyPI package, running install from a lockfile, installing a third-party skill/MCP plugin, or merging CI workflow changes, call the agent-guard MCP tools (
check_package,verify_lockfile,score_manifest,check_workflow). If verdict is SUSPICIOUS, REVIEW, or BLOCK/DANGER, stop and show findings to the user — do not proceed.
npx -y @liminallablibs/agent-guard-mcp@0.2.1 # MCP clients spawn this via npx
npm run http && curl "http://localhost:8402/check?name=reactt&ecosystem=npm"
Or run directly:
npm install
node src/mcp-server.mjs # stdio MCP server npm run http # optional HTTP mirror on :8402
GET /check?name= &ecosystem= POST /check-lockfile {lockfile_content, format} — format ∈ package-lock.json | yarn.lock | pnpm-lock.yaml | poetry.lock | requirements.txtPOST /score-manifest {manifest_type, manifest_content}POST /check-workflow {workflow_content}MIT.