English Français العربية

io.github.liminalpepe/agent-guard-mcp

Registre officiel Sécurité

Verify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows.

Code source Documentation

Que pouvez-vous faire avec io.github.liminalpepe/agent-guard-mcp ?

  • GET /check?name=<pkg>&ecosystem=<npm|pypi>
  • POST /check-lockfile {lockfile_content, format} — format ∈ package-lock.json | yarn.lock | pnpm-lock.yaml | poetry.lock | requirements.txt
  • POST /score-manifest {manifest_type, manifest_content}
  • POST /check-workflow {workflow_content}

Installation

Ajoutez ceci à la configuration MCP de votre client (Claude Desktop : claude_desktop_config.json ; Cursor : .cursor/mcp.json ; VS Code et les autres utilisent la même forme « mcpServers »).

NPM package @liminallablibs/agent-guard-mcp
Claude Code 
claude mcp add agent-guard-mcp -- npx -y @liminallablibs/agent-guard-mcp@0.2.1
Configuration JSON (Claude Desktop, Cursor, VS Code) 
{
    "mcpServers": {
        "agent-guard-mcp": {
            "command": "npx",
            "args": [
                "-y",
                "@liminallablibs/agent-guard-mcp@0.2.1"
            ]
        }
    }
}

Documentation

Tirée du README du projet sur GitHub, actualisée chaque semaine. Les liens ouvrent GitHub.

Sommaire
  1. agent-guard-mcp
  2. Why
  3. Install (MCP client)
  4. Agent rule (paste into Cursor Rules / CLAUDE.md)
  5. Quick demo
  6. HTTP endpoints (mirror of the MCP tools)
  7. License

agent-guard-mcp

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 depcheck_package
Review an LLM-generated lockfileverify_lockfile
Install a Cursor skill or MCP pluginscore_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):

ToolUse before…Returns
check_packageadding a single npm/PyPI dependencyOK / SUSPICIOUS / DANGER + typosquat/slop flags
verify_lockfilerunning npm/pip/yarn installscans every direct + transitive dep in a lockfile
score_manifestinstalling a Cursor/Claude skill or MCP/Smithery pluginpoison-signature + scope-overreach + drift score 0–100
check_workflowmerging a PR that touches CIflags mutable action pins, compromised actions, curl\bash, pwn-requests, secret exposure

Why

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.

Install (MCP client)

{
  "mcpServers": {
    "agent-guard": { "command": "npx", "args": ["-y", "@liminallablibs/agent-guard-mcp@0.2.1"] }
  }
}

Agent rule (paste into Cursor Rules / CLAUDE.md)

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.

Quick demo

npx -y @liminallablibs/agent-guard-mcp@0.2.1   # MCP clients spawn this via npx
# HTTP mirror:
npm run http && curl "http://localhost:8402/check?name=reactt&ecosystem=npm"
# → DANGER — typosquat of "react"

Or run directly:

npm install
node src/mcp-server.mjs        # stdio MCP server
npm run http                   # optional HTTP mirror on :8402

HTTP endpoints (mirror of the MCP tools)

  • GET /check?name=<pkg>&ecosystem=<npm|pypi>
  • POST /check-lockfile {lockfile_content, format} — format ∈ package-lock.json | yarn.lock | pnpm-lock.yaml | poetry.lock | requirements.txt
  • POST /score-manifest {manifest_type, manifest_content}
  • POST /check-workflow {workflow_content}

License

MIT.

Questions fréquentes

Qu'est-ce que io.github.liminalpepe/agent-guard-mcp ?

Verify-before-act safety checks for AI agents: packages, lockfiles, manifests, CI workflows.

Comment installer io.github.liminalpepe/agent-guard-mcp ?

Il s'exécute sur votre machine. Dans Claude Code : claude mcp add agent-guard-mcp -- npx -y @liminallablibs/agent-guard-mcp@0.2.1. Pour les autres clients, collez la configuration JSON de cette page dans leurs réglages MCP.

Faut-il une clé API pour io.github.liminalpepe/agent-guard-mcp ?

Son entrée au registre n'indique aucune clé ni secret obligatoire. Certaines fonctions peuvent tout de même demander un compte auprès du service auquel il se connecte.

io.github.liminalpepe/agent-guard-mcp est-il open source ?

Oui. Son code est sur GitHub sous licence MIT.

Qui maintient io.github.liminalpepe/agent-guard-mcp ?

Il est publié par liminalpepe. AI.tn le référence sans le maintenir ni le recommander.

Issu du registre MCP officiel. Être listé n'est pas une recommandation : vérifiez le code et les permissions d'un serveur avant de lui donner accès à vos données.