Plures runs on your own machine — the client starts it, so there is no endpoint to ping. 1 488 installs a week from npm. Last commit 2 Nov 2026.
Human in the loop for AI agents: ask ID verified people to check a decision before acting.
We read the source, 1 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.
try { const p = spawn(cmd, args as string[], { stdio: "ignore", detached: true }); p.on("error", () => {}); p.unref(); return true; } catch { return false; }
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
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.
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 plures -e 'PLURES_API_KEY=<PLURES_API_KEY>' -- npx -y plures-mcp
{
"mcpServers": {
"plures": {
"command": "npx",
"args": [
"-y",
"plures-mcp"
],
"env": {
"PLURES_API_KEY": "<PLURES_API_KEY>"
}
}
}
}
[mcp_servers.plures]
command = "npx"
args = ["-y", "plures-mcp"]
env = { PLURES_API_KEY = "<PLURES_API_KEY>" }
{
"mcpServers": {
"plures": {
"command": "npx",
"args": [
"-y",
"plures-mcp"
],
"env": {
"PLURES_API_KEY": "<PLURES_API_KEY>"
}
}
}
}
{
"servers": {
"plures": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"plures-mcp"
],
"env": {
"PLURES_API_KEY": "<PLURES_API_KEY>"
}
}
}
}
Put your own value in place of
<PLURES_API_KEY> (Your Plures API key. A free pk_test_ key works for trying it).
The author’s registry entry marks it as required.
Optional settings from the registry entry, left out of the block above:
PLURES_BASE_URL (API base URL, defaults to https://plures.si).
Human-in-the-loop for AI agents. Submit choices, get a human decision.
Human review for AI agents: ask through ActionBox and retrieve a typed decision before proceeding.
Trust metadata for AI agents — check files before building on them, stamp verified work.
Human-in-the-loop approval for agent actions, with verifiable action-bound receipts.
Human-in-the-loop for AI coding agents — ask questions, get approvals via Slack.
Offline scam check for agents: verify links and payments before acting (allow, ask or deny).
Check an email before an AI agent sends it: send / ask a human / block. Detects prompt injection.
Ask Vulnify before an AI agent acts. Check, record, and read policy decisions.
Answers built from our own checks of this server.