MCP.Market

Laguarde MCP server

by futur-panda.dev·dev.futur-panda/laguarde·v0.3.2·1 stars

Self-hostable policy control plane for AI coding agents.

A86/100grade A
What users say
No reviews yet
Be the first
Safety scan
A86/100

full report

Adoption
Growing

1 stars39 downloads/wk

Reviews

Write one

Nobody has reviewed Laguarde yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Laguarde tools (5)

write = sends, deletes, buys or posts

Read from the package source without running it. The installed server may list more.

  • evaluate_action

    Preview the policy decision for an intended action. Returns allowed, limited, approval, or forbidden. This preview is not an audit record; use record_decision before acting.

  • get_policy_bundle

    Return active, context-specific engineering policies with exact revision IDs. Call at the beginning of work and before planning a substantial change.

  • list_preference_proposals

    List existing preference proposals and observations. Use this before proposing feedback so similar observations converge on one proposal.

  • propose_preference

    Capture reusable developer feedback. Add to an existing proposal when it expresses the same preference; otherwise create a new proposal. Three observations promote it for human review, but only a human can accept it.

  • record_decision

    Re-evaluate an exact intended action and persist an immutable audit decision. This tool cannot override policy or self-approve an action.

Public scan report

scanner v0.1.9 · 2026-09-24 · same rubric, same numbers if you re-run it

no findings
  • Code scan5 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 60 days ago12/15
  • Maintainer identitynamespace and repository owner differ; GitHub account older than a year; website matches verified namespace7/10
Overall 86/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Laguarde compares

Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
86/100
higher than 72% of 48,255 servers
Tools
5
the typical server has 7
Tools that change things
0%
typical: 0%. Fewer write tools means less an agent can break
GitHub stars
1
more than 65% of 28,688 servers
Downloads a week
39
more than 30% of 12,191 servers with a package

What its tools let an agent do: 4 read · 1 run or deploy

Install Laguarde in Claude Code, Cursor or VS Code

Runs npx -y laguarde-mcp on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add laguarde -- npx -y laguarde-mcp
Add to Cursor

What the publisher says

From the Laguarde repository's README, as published. We do not edit it. Read it on GitHub

Laguarde

Laguarde is a self-hostable policy control plane for AI coding agents.

It gives a team one persistent place to define engineering practices, evaluate agent actions, ratify recurring developer preferences, and retain the exact policy revisions behind important decisions.

Laguarde runs locally for one developer or behind a team URL. Agents interact with the same server through standard MCP; humans use the dashboard and REST API.

What the prototype proves

initialization recipes, and PR review guidelines.

  • Four policy categories: code rules, general guardrails, project

allowed.

  • Four decisions: allowed, limited, approval, and forbidden.
  • Context-specific policy bundles with immutable revision identifiers.
  • One local daemon with a persistent registry of projects and Git origins.
  • Fail-safe action evaluation: an unmatched action is limited, not silently

actions.

  • Human approval for dependency, migration, deletion, and authentication

three observations promote it as a stronger candidate.

  • SQLite decision records plus human-readable Markdown evidence.
  • Developer feedback convergence: a human may merge any proposal immediately;

ratification.

  • A dashboard for policy CRUD, decision evaluation/review, and feedback

Quick start

For a local MCP installation, use Node.js 24 or newer:

npx -y --package laguarde-mcp@0.3.2 laguarde-daemon ensure
npx -y --package laguarde-mcp@0.3.2 laguarde-daemon register --cwd .

The first command reuses the healthy local daemon or starts it once. The second registers the current Git repository and prints its project-specific MCP URL. All local projects share the daemon, dashboard, SQLite database, and audit history while remaining separately identifiable.

Conceptual MCP configuration:

{
  "mcpServers": {
    "laguarde": {
      "type": "http",
      "url": "http://127.0.0.1:3000/mcp/projects/RETURNED_PROJECT_ID"
    }
  }
}

For repository development, install Bun and run:

bun install
bun run build
bun run start

Project HTTP MCP endpoints live under http://localhost:3000/mcp/projects/:projectId, and agent-facing discovery is available at .

Onboarding surfaces:

  • human guide: http://localhost:3000/guide;
  • agent self-setup contract: http://localhost:3000/install (text/plain).

To onboard a capable agent, send it the /install URL and explicitly ask it to connect Laguarde for the current project. The contract tells it how to verify the server, make a minimal native MCP configuration change, discover the tools, and load the registered project's policy bundle.

Agent policy-gate skill

Install the optional fail-closed skill from this repository with:

npx skills add https://github.com/FuturPanda/laguarde --skill laguarde-policy-gate

The skill requires a cooperative agent to load the project-bound Laguarde policy bundle, evaluate and record every material action, and stop when policy is unavailable, limited, approval-required, or forbidden. It does not replace a sandbox or host-level execution hook.

For S3/CloudFront onboarding, generate the two static upload objects with:

bun run export:onboarding

See docs/s3-onboarding.md.

MCP Registry publication is automated through GitHub Actions after a one-time DNS authentication setup. See docs/registry-publishing.md.

The daemon's first start creates ~/.laguarde/laguarde.db, seeds global policy, and adds ten policies. Set LAGUARDEDATADIR, or the more specific LAGUARDEDBPATH and LAGUARDEEVIDENCEDIR, to place persistent data elsewhere.

Agent workflow

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Laguarde: common questions

Is Laguarde MCP server safe?
Yes, by our scan: it is graded A (86/100). Read the Laguarde safety report
How do I install Laguarde?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Laguarde need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Laguarde maintained?
The last commit was 101 days ago (2026-07-26). The latest release is v0.3.2.
How does Laguarde compare with other MCP servers?
safety score 86/100 (higher than 72% of 48,255 servers); tools 5 (the typical server has 7); tools that change things 0% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.