ai-agent-playbook (blueroaring/ai-agent-playbook) is an MCP server listed on the M8ven Trust Index. It scores 74 out of 100, grade C. It declares 20 tools. No publisher has claimed this listing.

C
Emerging
74/100

ai-agent-playbook

Reusable engineering lessons (symptom -> root cause -> fix -> verification) and zero-dependency MCP bridge recipes for AI coding agents. Sanitized: contains no personal profile.

Emerging. No concerning findings. Grades remain capped until the project builds reputation through adoption. 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

blueroaring

Source: github_repo_search

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

The grade above is for the source repository. Registries can serve a different version, so we mark the ones we were not able to read.

// key findings
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.
🔐
You'll be asked for 3 credentials: GH_TOKEN, GITHUB_TOKEN, ZOTERO_API_KEY
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// 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.
configBRIDGE_DEBUG
configBRIDGE_SERVER_NAME
configBRIDGE_TOKEN_FILE
configBRIDGE_TRACE_FILE
configDSH_GODOT_BRIDGE_PORT
🔐 secretGH_TOKEN
🔐 secretGITHUB_TOKEN
configGITHUB_TOKEN_FILE
configGIT_BIN
configGIT_MCP_DEFAULT_CWD
configGODOT_BIN
configGODOT_OUTPUT_DIR
configGODOT_PROJECT
configGODOT_SCAN_ROOTS
configGODOT_STEAM_ROOTS
configPHONE_GATEWAY_BIND
configPHONE_GATEWAY_KEY_FILE
configPHONE_GATEWAY_LOG
configPHONE_GATEWAY_PORT
configPHONE_GATEWAY_QUIET
configPHONE_GATEWAY_TARGET_HOST
configPHONE_GATEWAY_TARGET_PORT
configPHONE_GATEWAY_TOKEN_FILE
🔐 secretZOTERO_API_KEY
configZOTERO_API_KEY_FILE
configZOTERO_DATA_DIR
configZOTERO_LIBRARY
// quality suggestions

Tool annotations

No tools have read-only/destructive annotations

Add readOnlyHint or destructiveHint annotations to every tool so hosts can warn users before invoking.

All four hints declared on every tool

20/20 tools missing one or more hints — godot_status (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); godot_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); godot_new_project (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +17 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.

Tests exist

No test files found

Add tests that exercise each declared tool.

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 3 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 Score](https://m8ven.ai/badge/mcp/blueroaring/ai-agent-playbook)](https://m8ven.ai/mcp/blueroaring/ai-agent-playbook)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: e95af21fd1cfaff4ed17c1501fcf4820cade5b42
code hash: 493696454d3798909e73b62724825057f6c323be864f9a1714fbe92b09470281
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