WARDEN — MCP Security Firewall MCP server

<!-- aicom-mirror-notice -->

🔄 Synced from a monorepo — but with a live history. warden mirrors the

canonical AI-Factory monorepo. History here is append-only (no force-push).

Pull requests are welcome — merged PRs are imported back into the monorepo

and re-synced here, so your contribution becomes canonical.

💬 Issues · Pull requests both welcome.

WARDEN — MCP server

<!-- mcp-name: io.github.alexar76/warden -->

<!-- aicom-readme-badges --> =20" /> <!-- /aicom-readme-badges -->

🌐 English · Русский · Español · Français · 中文 · Glossary

One MCP server. Security firewall for advertised tool definitions. Library included.

Transport: stdio (npx -y @aimarket/warden / node dist/mcp-server.js). Compatible hosts: Claude Desktop, Cursor, Glama, and any MCP client that speaks stdio. No API keys.

An MCP server tells your agent what its tools do. The agent believes it — that sentence is the attack surface. A tool description is prompt text delivered by a third party straight into your model's context, and a schema field named api_key is a request for your secrets phrased as an API.

WARDEN vets a server before any of its tools reach the model, and returns a verdict you can record: allow/block, a 0..1 score, the findings that produced it, a per-tool partition, and the exact rule table that was in force.

Zero npm runtime dependencies. The library's only import is node:crypto. The stdio MCP server adds other node: builtins (fs, path, process) and still pulls in no packages. It is the firewall out of ARGUS, extracted so you can put it in front of your own MCP host without adopting an agent.

Run as MCP server (stdio)

npx -y @aimarket/warden            # bin: warden-mcp
# from this repo:
npm run build && node dist/mcp-server.js

Shortened. The full README is on GitHub.