Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Local-first AI agent security evidence and approval workflows through HOL Guard's stdio MCP server.
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": {
"hol-guard": {
"command": "uvx",
"args": [
"hol-guard",
"mcp",
"serve",
"--stdio"
]
}
}
}Run this in your terminal
claude mcp add hol-guard -- uvx hol-guard mcp serve --stdioPaste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"hol-guard": {
"command": "uvx",
"args": [
"hol-guard",
"mcp",
"serve",
"--stdio"
]
}
}
}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": {
"hol-guard": {
"type": "stdio",
"command": "uvx",
"args": [
"hol-guard",
"mcp",
"serve",
"--stdio"
]
}
}
}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 hashgraph-online, 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 (3.59.0) reached the registry 2 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Agent Data Tools: Utilities
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.
103 tools: JSON repair, CSV, hashes, cron, dates, units, validators. 25 free calls.
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.
| | Stop risky AI actions before they compromise your machine. HOL Guard is a local-first security layer for AI agents, tools, plugins, skills, MCP servers, and package installs.
Install HOL Guard Read the documentation PyPI Package (hol-guard) Report an Issue | | :--- | :--- |
HOL Guard reviews agent actions before they run: shell commands, file access, package installs, and MCP tool calls. It detects secret exposure, destructive operations, prompt injection, and supply-chain risks, then allows, blocks, or requests approval according to your policy.
Run it locally without an account. Use the CLI and local dashboard to manage protection, resolve approvals, and inspect decision history. Optional Guard Cloud adds shared history, team policy, and fleet management.
Get started · Supported agents · Plugin scanner · Documentation · Contribute an extension · Contribute an adapter · Development
Requires Python 3.10 or newer, pipx, and a matching native runtime. Check the platform support and Windows ARM64 setup notes before installing.
pipx install hol-guard
hol-guard init
The first-run wizard discovers supported agents and walks you through protection setup. It asks before each setup change, including opening the dashboard, installing agent integrations, and connecting optional cloud services.
Check your installation:
hol-guard --version
hol-guard status
To update an existing installation:
hol-guard update
For manual setup, see the installation guide. Annotated release notes with upgrade context live at hol.org/guard/releases; raw releases and prereleases are on the GitHub releases page.
| Surface | Protection |
|---|---|
| Shell commands and file access | Reviews destructive operations, sensitive file access, credential exposure, and suspicious outbound commands. |
| Package installs | Evaluates supported package-manager operations against supply-chain intelligence before installation. |
| Plugins, skills, and agent configuration | Inventories local artifacts and reviews new or changed tools before launch. |
| MCP servers and tools | Inspects server configuration and reviews tool calls through supported hooks and managed proxies. |
| Prompts and tool results | Screens supported events for prompt injection and sensitive content. |
| Approvals and evidence | Routes decisions to native prompts or the approval center, and records local receipts for review. |
Guard connects through native agent hooks, managed MCP proxies, and launch integrations. Coverage depends on the events each agent exposes; the support matrix documents enforcement, approval delivery, and failure behavior per integration.
Codex, Claude Code, GitHub Copilot CLI, Cursor, Cline, Gemini CLI, Grok, Hermes, Kimi Code, Pi, oh-my-pi, OpenClaw, OpenCode, Antigravity, ZCode, and Devin. Paseo is supported through these native provider integrations, with per-provider coverage.
For example, to set up Codex explicitly:
hol-guard install codex
hol-guard run codex --dry-run hol-guard run codex
The dry run records the current artifact state before launch. For Codex, Guard installs native pre-tool hooks and refuses a managed launch if those hooks are missing or disabled.
Agent support matrix · Troubleshooting
| Task | Command |
|---|---|
| Check protection status | hol-guard status |
| Diagnose an agent integration | hol-guard doctor codex |
| Inspect changes before launch | hol-guard diff codex |
| Review pending approvals | hol-guard approvals |
| Approve or deny a request | hol-guard approvals approve / hol-guard approvals deny |
| Read decision history | hol-guard receipts |
| List tracked artifacts | hol-guard inventory |
| Export an AI bill of materials | hol-guard abom --format json |
| Scan workspace dependencies | hol-guard supply-chain scan |
| Connect optional cloud sync | hol-guard connect |
Inspect the command's classification and matching rules:
hol-guard command test 'rm -rf ./build'
hol-guard command explain 'git clean -ndx' hol-guard command extensions command.git --json
command test and command explain inspect the command without executing it or creating an approval. Use hol-guard approvals to resolve a pending request and hol-guard receipts to review the recorded decision.
The Extension directory lists command coverage generated from the Rust-compiled catalog. External contributions require explicit opt-in; required core protections remain enabled. To add coverage, follow the Extension contribution guide.
hol-guard supply-chain sync
hol-guard supply-chain scan hol-guard supply-chain explain minimist@1.2.5 --ecosystem npm
The package verdict includes the available advisory evidence and ecosystem coverage. See the get-started guide for package-manager interception and the remediation guide for handling false positives.
This repository also ships plugin-scanner, a CLI for maintainers who want security and quality checks before publishing agent plugins, skills, and MCP integrations.
pipx install plugin-scanner
plugin-scanner scan . plugin-scanner lint . plugin-scanner verify .
| Command | Purpose |
|---|---|
scan | Security findings and a quality report across detected package surfaces. |
lint | Rule-level authoring feedback. |
verify | Install-surface and runtime readiness checks. |
submit | A submission artifact for one plugin package. |
doctor | Component diagnostics and troubleshooting bundles. |
The scanner detects Codex, Claude Code, DeepSeek Harness, Gemini CLI, Kimi Code, and OpenCode package formats. Use plugin-scanner --list-ecosystems to list them or --ecosystem to select one. At a Codex marketplace root, it discovers local plugin entries automatically.
Checks cover manifests, secrets, MCP transport and command configuration, approval defaults, skills, dependency lockfiles, and GitHub Actions permissions. Optional Cisco integrations add skill and MCP analysis. Reports support text, JSON, Markdown, and SARIF.
plugin-scanner scan . --format sarif --output plugin-scanner.sarif
plugin-scanner scan . --fail-on-severity high
Quality grades use the checks applicable to each package. Trust scoring has separate provenance and weights; see the skill, MCP, and plugin scoring references.
hol-guard plugin is the Plugin Kit. Point it at one plugin source, such as a Claude Code plugin, Codex plugin, Gemini CLI extension, MCP Registry server.json or a folder of skills, and it checks the source and writes a ready-to-load copy for each agent runtime that can use it. It runs locally, reads only the folder you name and makes no network calls.
hol-guard plugin check # what marketplaces and runtime loaders would reject
hol-guard plugin package # writes dist/hol-plugin/ / for each runtime hol-guard plugin convert --to agent-plugins # Agent Plugins 1.0 package, checked against the spec hol-guard plugin links # install commands per runtime, plus listing links hol-guard plugin card # draft .well-known plugin card as JSON hol-guard plugin init --name my-plugin # scaffold a new plugin in an empty folder
Runtimes: claude-code, codex, gemini-cli, cursor, vscode, opencode, mcp-registry, agent-skills and agent-plugins. See the Plugin Kit guide.
Add the scanner to a plugin repository:
name: Plugin security
on: [push, pull_request]
permissions: contents: read
jobs: scan: runs-on: ubuntu-latest steps:
See the action documentation for SARIF uploads, submission workflows, and machine-readable outputs. The action source is maintained in action/.
</a
Only the beginning is shown; read the rest in the repo