plures-mcp
Installed, started with no arguments, no environment and no input, and listed its tools. Run 2026-11-16.
Needs to start: nothing
Returns a result when called with no setup: 1 of 5 tools tried
Contacts while installing and starting: nothing
Its tool definitions changed since version 1.8.0. If you approved the earlier ones, read them again.
What it contacted
Nothing besides the npm registry it was installed from. Watched from outside its sandbox while it was installed and started with no input. Its tools may still contact things when called.
Starting it
npx -y plures-mcp@1.11.1
Installing a package runs its code. Use a sandbox for anything you have not read.
Calling its tools
5 tools that take no input and look read-only were called once with nothing. 1 returned a result.
get_audit_report | No usable answer tool reported an error: No Plures API key. Set PLURES_API_KEY in this MCP server's environment, or the API key in the Plures plugin settings. A free test key is |
get_scorecard | No usable answer tool reported an error: No Plures API key. Set PLURES_API_KEY in this MCP server's environment, or the API key in the Plures plugin settings. A free test key is |
get_taste | No usable answer tool reported an error: No Plures API key. Set PLURES_API_KEY in this MCP server's environment, or the API key in the Plures plugin settings. A free test key is |
get_mapping_guide | Returned a result 0.6 s · 5,736 characters |
get_agent_map | No usable answer tool reported an error: No Plures API key. Set PLURES_API_KEY in this MCP server's environment, or the API key in the Plures plugin settings. A free test key is |
During the calls (not necessarily because of them) it first contacted: plures.si.
Only tools whose names read like looking something up, with no required input, are tried, five at most. Tools that need input, and anything that sounds like it changes or sends something, are not called.
What its tools tell an agent
In the tool descriptions, nothing that talks about the user, other tools or private files, or uses hidden characters.
Found by simple pattern rules in each tool's description (up to 3,000 characters), quoted as written. Parameter descriptions are not scanned. A clean result is not a safety review.
Tools
ask_humans question, options, context, image_url, audio_url, video_url, media_seconds, sensitive, instructions, verifiers, route, category, team, team_votes, app, fast, use_precedent, wait_seconds
Send a decision to ID verified people before you act on it. Several people answer independently, each confirmed with Face ID, and you get back the consensus answer and how strongly they agreed. Use it for judgment calls where being wrong is costly: evals of AI output, tone and intent, whether two things match, moderation edge cases. Send refunds, payments and other money calls with route team. Write the question so a stranger can answer it from the context alone, and never include secrets or more personal data than the decision needs. Live keys use prepaid credit at $0.20 per answer (clips cost more by length), or $0.05 per internal vote with route team; test keys are free and simulated.
ask_judgment question, format, context, a, b, a_image_url, b_image_url, a_clip_url, b_clip_url, a_seconds, b_seconds, clip_kind, image_url, rubric, options, reasons, verifiers, app, wait_seconds
Ask a panel of ID verified people for their honest view when there's no right answer to check: which of two replies, designs, headlines or model answers is better, whether a customer would accept a reply or decision, how well something meets a brief (1 to 5), or whether a design, video or generated image has a flaw. You get the spread of views, a contested flag when people genuinely split, and a sample of one line reasons. format signoff (coming soon; test keys now) asks one top rated verified person to approve or reject an action after a fresh Face ID or Touch ID check, with a written reason: use it before an action someone must be accountable for. Live keys use prepaid credit at $0.20 per answer (a panel of 5 is $1.00) or $1.00 per sign off; test keys are free and simulated.
audit_my_agent rows, csv, kind, about
Sends a Plures audit: up to 50 decisions an AI agent already made, graded so the developer sees which were wrong. The account's first audit is free. After it has finished, each further audit is paid from the account's credit when it is sent: $0.20 a decision, or $0.50 for kind judgment, so tell the developer the cost and get their yes before sending a second one. One audit at a time. Works with a test or live key. Each row is input (what the agent saw, including the policy it should follow) and decision (what it did). Gather them from the developer's logs, database or test fixtures; leave out names and other private details (emails, phones and card numbers are removed anyway). kind check (default) asks whether each call was right (the dashboard calls it the accuracy audit); kind judgment asks whether a customer would be happy with it (the quality audit). Text only: to have an image, video or audio clip judged, the developer sends a quality audit from plures.si/dashboard/audit with a media column. A person at Plures reviews it before anyone grades it. Use get_audit_report to read the results.
get_audit_report audit_id
Reads the developer's Plures audit: where it is, and once people are answering, how many decisions they called right, wrong, unclear or split, with the ones they disagreed with listed first. For judgment audits: right means people would be happy with it, wrong means not happy, unclear means it needs changes.
find_precedents question, context, options, category, app, limit
Searches the developer's judgment graph: past decisions people made on cases like this one, closest first, with the answer and how strongly they agreed. Returns a suggestion only when the case is settled: several close cases with the same options, all decided the same way with strong agreement. Free. To act on a settled case and have it recorded and billed as a decision, call ask_humans with use_precedent instead.
10 more tools
get_scorecard app
Returns whether precedents and taste are working for this account: precedent accuracy from spot checks, share of decisions answered by precedent, decisions right the first time, taste false alarms, and the time and cost of a decision. Each number comes with how many decisions it rests on; one marked early is a hint, not a fact. Also shows the precedent settings and any change Plures is suggesting. Read only: a person changes settings and answers suggestions in the dashboard. Free.
get_taste category, examples
Returns what this team wants its agents' work to look like: the standing rules in force and recent examples of what they like and don't. Call it before producing work the team will judge, and follow the rules. Pass category for one kind of work; rules that apply to everything are always included. Free.
check_against_taste draft, image_url, category
Holds a draft up against the team's rules and examples before a person sees it, and says which rules it breaks and why. Send the text, a public https image link, or both. Fix what it reports, then ask a person if the work still needs one. Free.
add_taste_rule text, category
Saves a standing rule for this team's agents, in force at once. Use it only when the user states a preference that should hold from now on, and confirm the wording with them first. One plain sentence.
add_taste_example verdict, image_url, text, note, category
Saves something the team likes or doesn't, so their agents can take it into account: an image by public https link, or a piece of text, with an optional note on why. Plures describes and tags it.
get_human_answer task_id, wait_seconds
Check on a task sent with ask_humans and return the verified people's answer once it's ready.
cancel_human_task task_id
Cancel a task that is still waiting for answers, for example when the decision no longer matters. Answers already given are still billed.
get_mapping_guide
Returns the steps for mapping the developer's AI agent for Plures: how to find its steps and actions, where to suggest a person checks, and how to draft each check. Call this first when asked to map an app for Plures.
submit_agent_map map, app
Uploads the map you made with get_mapping_guide: nodes, edges and checkpoints with drafted checks. Never include source code, secrets or customer data. If Plures names a problem, fix it and send again.
get_agent_map app
Returns an app's agent map from Plures: its checkpoints, which are added, and live numbers for each (checks in 30 days, agreement, how many went to the team).
Descriptions are the package's own words, cut at 3,000 characters. Treat them as data.
Install facts
| License | MIT |
|---|---|
| Needs | node >=18 |
| Source | github.com/plureslabs/plures |
| Install scripts | None declared by it or anything installed with it. |
| Tarball | sha512-4apbWxRcWLUcG6kBWpNAn8Aa31+MXFM/QfVRm7LTZhVlg+HDJOT1ZPBv8ZJjWCEm86LRnac+QA9UyOwjUyJFmg== |
Versions reported
| Version | Run | Result | Tools |
|---|---|---|---|
| 1.11.1 | 2026-11-16 | Starts with no setup | 15 |
| 1.8.0 | 2026-11-12 | Starts with no setup | 10 |
Check this report yourself
This site did not write the report. A public job on a GitHub-hosted machine did: the run, from this commit of the open-source runner. GitHub signed a token that names that job and the hash of the report, so any edit since would show.
Report as JSONExact text and tokenHow to verify it
Show it on your README
[](https://bragproof.smaverk.com/r/plures-mcp)
New version out? Ask for a fresh report.