Mnki MCP runs on your own machine — the client starts it, so there is no endpoint to ping. 77 installs a week from npm. Last commit 21 Sep 2026.
MCP proxy that checks every tools/call against Agent Trust policy, with evidence, before it runs.
What the code does
We read the source, 3 d ago · rules 995398eba69f
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
const child = spawn(command, args, { env, stdio: ["pipe", "pipe", "pipe"] });
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
This code can reach further than it looks
We found places where it runs commands, builds paths or queries from values it is given. None of that is a flaw by itself — it becomes one when the code changes, and code changes quietly between releases. We re-read it on every one.
Connect this server
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add mnki-mcp -e 'MNKI_API_KEY=<MNKI_API_KEY>' -- npx -y mnki-mcp{
"mcpServers": {
"mnki-mcp": {
"command": "npx",
"args": [
"-y",
"mnki-mcp"
],
"env": {
"MNKI_API_KEY": "<MNKI_API_KEY>"
}
}
}
}[mcp_servers.mnki-mcp]
command = "npx"
args = ["-y", "mnki-mcp"]
env = { MNKI_API_KEY = "<MNKI_API_KEY>" }{
"mcpServers": {
"mnki-mcp": {
"command": "npx",
"args": [
"-y",
"mnki-mcp"
],
"env": {
"MNKI_API_KEY": "<MNKI_API_KEY>"
}
}
}
}{
"servers": {
"mnki-mcp": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"mnki-mcp"
],
"env": {
"MNKI_API_KEY": "<MNKI_API_KEY>"
}
}
}
}Put your own value in place of
<MNKI_API_KEY> (Agent Trust API key with the verify scope (console → Settings → API keys)).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
MNKI_URL (Console base URL; https://mnki.com unless self-hosted).
Alternatives to Mnki MCP
same job, measured the same wayMCP gateway that checks each agent tool call against a signed grant and policy, and signs a receipt
Governs what AI agents do: tool calls, SQL, commands, files checked against policy before they run.
Spend limits for AI agents that pay with x402: every paywall is policy-checked before a cent moves.
MCP runtime security proxy. Blocks dangerous AI agent tool calls with a policy engine.
See, price, and control every tool call your AI agents make: policy checks, cost, and audit tools.
Transparent MCP proxy that independently re-verifies tool-call claims before the Host trusts them.
Compatibility checks for AI agents before they buy or install: verdicts, evidence, receipts.
MCP security trust-check for agents before installing MCPs, Skills or tools.
Mnki MCP — questions
Answers built from our own checks of this server.