protoAgent (protoLabsAI/protoAgent) is an MCP server listed on the M8ven Trust Index. It scores 39 out of 100, grade F. It declares 81 tools. No publisher has claimed this listing.

F
Warning
39/100

protoAgent

Template for building protoLabs A2A agents on LangGraph — fork me

Warning. Serious findings were identified. Review the full report before connecting. 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

protoLabsAI

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
🚨
Secret credentials may flow to a network call
3 flows detected: A2A_AUTH_TOKEN, OPENAI_API_KEY. We can’t prove the destination matches the brand the credential belongs to.
🚨
Code appears obfuscated
12 files are unreadable to a human reviewer. Cannot audit what they do.
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — edit_soul (line 2770: provenance_path.unlink(missing_ok=True))
🔐
You'll be asked for 6 credentials: GITHUB_TOKEN, GH_TOKEN, A2A_AUTH_TOKEN, A2A_FEDERATION_TOKEN, EVAL_API_KEY, OPENAI_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.
configPROTOAGENT_MCP_TRUST
configOPERATOR_MCP_TOOLS
configCOMSPEC
🔐 secretGITHUB_TOKEN
🔐 secretGH_TOKEN
configPROTOAGENT_PUBLIC_METRICS
🔐 secretA2A_AUTH_TOKEN
🔐 secretA2A_FEDERATION_TOKEN
configAGENT_NAMEschedule_task / list_schedules / cancel_schedule tools backed by a bundled sqlite scheduler. Multi-agent-safe — every job is namespaced by AGENT_NAME. See [Schedule future work](./docs/guides/scheduler.md)
configPUSH_NOTIFICATION_ALLOWED_HOSTS
configPUSH_NOTIFICATION_ALLOWED_CIDRS
configBACKGROUND_FIRE_TIMEOUT_S
configBACKGROUND_MAX_CONCURRENCY
configBACKGROUND_BATCH_JOIN_TIMEOUT_S
🔐 secretEVAL_API_KEY
configEVAL_BASE_URL
configAGENT_BASE_URL
configPROTOAGENT_CONFIG
configEVAL_JUDGE_MODEL
configPROTOAGENT_INSTANCE
configPROTOAGENT_HOME
configAUDIT_PATH
configBACKGROUND_AUTO_S
🔐 secretOPENAI_API_KEY
configPROTOAGENT_UI
configPROTOAGENT_MODEL
configPROTOAGENT_FLEET_AUTOSTART
configPROTOAGENT_CONFIG_DIR
configPROTOAGENT_SEED_CONFIG
configPROTOAGENT_SEED_SOUL
configPROTOAGENT_GATEWAY_RESPONSES_API
configPROTOAGENT_AUTO_SCOPE
configPROTOAGENT_BOX_ROOT
configXDG_CONFIG_HOME
configPROTOAGENT_HOST_CONFIG
configPROTOAGENT_PLUGINS_DIR
configPROTOAGENT_PLUGINS_LOCK
configPROTOAGENT_WORKSPACE
configKNOWLEDGE_DB_PATH
configPROTOAGENT_INJECTION_LOG
configLOG_BUFFER_LINES
configLOG_FORMAT
configLOG_LEVELINFO is the default — LOG_LEVEL=DEBUG for more
// 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

83/83 tools missing one or more hints — show_config (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); my_tool (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_projects (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +80 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.

Destructive tools are labelled

2 tools perform destructive updates without destructiveHint — delete_file deletes at line 904 (target.unlink()); edit_soul deletes at line 2770 (provenance_path.unlink(missing_ok=True))

Add destructiveHint:true to any tool whose handler calls .delete(), .upsert(), .update(), unlink, rm, DELETE, DROP, REPLACE INTO, or any operation that overwrites existing data.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — edit_soul (line 2770: provenance_path.unlink(missing_ok=True))

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

No eval / new Function

1 eval() or new Function() call — dynamic code execution

Replace eval / Function with explicit parsing or safer alternatives.

Readable source code

12 files are minified or bundled, which is usually build output rather than concealment

Ship unminified, readable source.

Secrets stay with their owner

3 secrets sent to a request target we could not resolve (A2A_AUTH_TOKEN → dynamic, OPENAI_API_KEY → dynamic) — often a configured endpoint, not necessarily third-party

Audit where credentials are sent. A NOTION_TOKEN should only reach api.notion.com — never a third-party host.

Secrets not logged

2 secret values sent to print

Redact or omit secret values from log output.

Tool description accuracy

edit_soul: description implies read-only but handler writes/deletes/executes

Update tool descriptions to accurately reflect all capabilities — especially write, delete, or execute operations.

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 9 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/protolabsai/protoagent?variant=verified)](https://m8ven.ai/mcp/protolabsai/protoagent)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 54b10b37b4447160b032c870f17852497093bca6
code hash: c5240c62d9e5ddd320fdb746540e4be62bc3cf7328fa472a91007351c0243917
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