pi-mcp (zhaob1n/pi-mcp) is an MCP server listed on the M8ven Trust Index. It scores 66 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

C
Caution
66/100
22 days ago

pi-mcp

MCP server exposing pi coding-agent tools for file and shell operations, including read, write, edit, bash, grep, find, and ls.

Caution. Specific findings reduced this grade. They are listed on the page. Grades reflect the full trust pyramid: code, verification depth, and reputation. New projects cap at C until adoption is earned.

How we verified

⚡ Live Monitored: not connected

Verified is a snapshot. Live keeps it current, and builds your track record.

⚡ Connect GitHub → continuous verification on every pushwhy connect →

Who stands behind it

zhaob1n

Source: Glama

Is this your MCP?

Claim it to get a verified publisher badge, a free copy of our full audit findings, and direct contact for any high-priority issues we find. Or connect your repo for our deepest verification, Live Monitored: read-only, revoke anytime. What we access →

Install from

M8ven verifies MCPs across every public registry — install directly from whichever one you prefer.

// key findings
⚠️
Tool annotations don’t match behaviour
2 read-only tools perform write/delete/exec — find (line 62: spawn(options.fdPath, args, { stdio: ["ignore", "pipe", "pipe"] })); grep (line 69: spawn(options.rgPath, args, { stdio: ["ignore", "pipe", "pipe"] }))
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — find (line 62: spawn(options.fdPath, args, { stdio: ["ignore", "pipe", "pipe"] }))
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
Open source with a license and README
Anyone can audit the code, the license is declared, and the publisher documents what it does.
// environment variables
To run this server yourself, you supply these values. They go in your own MCP client configuration and stay on your machine. The secret label means the value is sensitive, not that the server mishandles it.
configProgramFiles
configProgramFiles(x86)
// quality suggestions

All four hints declared on every tool

7/7 tools missing one or more hints — bash (missing: readOnlyHint, idempotentHint); edit (missing: readOnlyHint, idempotentHint); find (missing: destructiveHint, idempotentHint), +4 more. OpenAI's directory rejects tools where any of the four hints are missing or non-boolean.

For every tool, set all four hints (readOnlyHint, destructiveHint, idempotentHint, openWorldHint) to explicit true/false values that match the handler’s actual behaviour.

Tool annotations match behaviour

2 read-only tools perform write/delete/exec — find (line 62: spawn(options.fdPath, args, { stdio: ["ignore", "pipe", "pipe"] })); grep (line 69: spawn(options.rgPath, args, { stdio: ["ignore", "pipe", "pipe"] }))

Either remove the readOnlyHint:true annotation, or remove the write/delete call from the tool handler.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — find (line 62: spawn(options.fdPath, args, { stdio: ["ignore", "pipe", "pipe"] }))

Rename the tool, rewrite the description, or move the side-effect into a separate clearly-named tool.

Tool inputs are validated

Only 0/7 tool handlers declare input schemas (0%)

Declare an inputSchema with zod/joi/yup on every tool definition.

Tests exist

No test files found

Add tests that exercise each declared tool.

Shell command execution

3 child_process/subprocess calls in production code — runs shell commands (src/vendor/shell.ts:22, src/vendor/shell.ts:40, src/vendor/shell.ts:136)

Prefer library functions over shell-outs. If you must shell out, ensure all inputs are properly escaped.

Claim the listing to review these findings one by one and send us a correction where you disagree, straight to the team. Claiming also means we tell you when the grade moves, and reach you first if we find anything urgent.

// full audit trail
The findings above are the summary. The full trail, every check we ran, each deduction, the network hosts observed and the dependency advisories, goes to verified publishers, along with an alert whenever a new one lands. Verified publishers can also review each finding and dispute it in one click. Publisher corrections have sharpened several of our checks this month, because the maintainer knows the codebase better than any scanner.
// improvement guidance — verified publishers only
We have 6 concrete improvements we can share with the publisher of this MCP. Each comes with specific guidance to raise the trust score.
// embed badge in your README
[![M8ven Verified](https://m8ven.ai/badge/mcp/zhaob1n/pi-mcp?variant=verified)](https://m8ven.ai/mcp/zhaob1n/pi-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: f92eb4112535547193f1d6977ad3aea396f14eb7
code hash: de93f50ed040819e4dfe28c348174cdbd8c4f04c8088d80d840ec572437e7a0d
verified: 8/19/2026, 9:39:57 AM
view raw JSON →
Check MCPs from inside your assistant
Tool Check · MCP

Vetting this one by hand? Tool Check is an MCP that scores other MCPs. Add it once and ask Claude, ChatGPT, or any MCP client to grade a server, surface CVEs, check the publisher, and suggest safer alternatives — before you install.

https://m8ven.ai/api/mcp/tool-check
check_toolsearch_toolscompare_toolsrecommend_alternativescheck_publisherreport_concern
How to add it →Free · no account needed · works in any MCP client