
Mnki Mcp
io.github.MNKIAgentOSPublished by GitHub account MNKIAgentOSv0.3.0Updated Oct 24, 2026
MCP proxy that checks every tools/call against Agent Trust policy, with evidence, before it runs.
Overview
A local MCP proxy that checks each tools/call against Agent Trust policy, with evidence, before forwarding it to the wrapped MCP server.
- What you can do
- Intercept tools/call requests between an MCP client and a wrapped MCP server, whether that server is a stdio command or a Streamable HTTP endpoint, and verify each call against Agent Trust policy before it runs, returning evidence with the verdict. Forward all other MCP traffic untouched. Run in observe, warn, require_approval or enforce mode, from log-only to denying calls and waiting for human approval. Surface JSON-RPC errors for denied calls, approval required or rejected or expired, verification quota exceeded, and Agent Trust being unreachable.
- When to use it
- Use it when you want a policy checkpoint in front of an existing MCP server so that tool calls are verified and evidenced before execution, and when you need graduated rollout from logging to enforcement.
- Requirements
- Runs locally over stdio, typically via npx from the mnki-mcp npm package, so Node.js is needed. Requires an Agent Trust API key with the verify scope in MNKI_API_KEY; MNKI_URL optionally points at a self-hosted console instead of the default. Network access to the Agent Trust service is needed for verification. Desktop clients only.
Installation
In SourceWeft
- Open Mnki Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
mnki-mcp
mnki-mcp is a local MCP proxy: it sits between an MCP client (Claude Desktop, Claude Code, Cursor, Windsurf, VS Code) and
an MCP server — a stdio command or a Streamable HTTP endpoint — and verifies every tools/call against Agent Trust
before it reaches the server. Everything else is forwarded untouched.
Modes (--mode): observe (log only, always forward — the default), warn (forward, surface evidence), require_approval
(escalate only where policy says so, never hard-deny), enforce (deny with evidence, wait for human approval).
JSON-RPC errors the client sees in enforce mode: -32003 denied (with the ✓/⚠/✕ evidence), -32001 approval required /
rejected / expired, -32005 verification quota exceeded, -32006 Agent Trust unreachable (observe and warn forward instead).
Install it with mnki protect (dry run by default) or by hand — see examples/.
Source: packages/mcp/README.md at commit e2bfe80
Tools
0Version history
3- v0.3.0LatestSep 20, 2026
- v0.1.6Sep 18, 2026
- v0.1.3Sep 17, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts