Back to MCP Trust Indexm8ven
C
Warning
74/100
8 hours ago

Pyrus MCP

Enables authorized employees and AI hosts to perform Pyrus operations over the Model Context Protocol (MCP) with production-grade security and observability.

→ sparko161-droid/pyrus_mcp_bd_complect· listed on glama

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

Code 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

sparko161-droid

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 →

⚡ Connect GitHub for Live Monitored

Install from

Glama

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

// key findings
🚨
Secret credentials may flow to a network call
1 flow detected: EMBEDDING_KEY. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 5 credentials: PYRUS_SECURITY_KEY, BANK_TOKEN, EMBEDDING_KEY, MCP_BEARER, PYRUS_ACCESS_TOKEN
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.
configPYRUS_LOGIN
🔐 secretPYRUS_SECURITY_KEY
🔐 secretBANK_TOKEN
configEMBEDDING_URL
🔐 secretEMBEDDING_KEY
configEMBEDDING_MODEL
configEMBEDDING_DIM
configBANK_PORT
configMCP_URL
🔐 secretMCP_BEARER
🔐 secretPYRUS_ACCESS_TOKEN
configSCOPE_UPSTREAM
configSCOPE_LOG
configSCOPE_MAX_BODY
configPYRUS_API_URL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployDATABASE_URL
// 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

15/15 tools missing one or more hints — t_list_zones (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); t_search (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); t_get_entry (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +12 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 test coverage

Only 0/15 tools referenced in tests (0%)

Write tests that reference each tool by name so every tool has at least one test.

Secrets stay with their owner

1 secret/sensitive value flow into network calls (EMBEDDING_KEY → dynamic)

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

Secrets not logged

4 secret values sent to console.log

Redact or omit secret values from log output.

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 5 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/sparko161-droid-pyrus-mcp-bd-complect-147n08?variant=verified)](https://m8ven.ai/mcp/sparko161-droid-pyrus-mcp-bd-complect-147n08)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 898c2e54908c84311e3471c8d328f94016e9c2e4
code hash: b9540384542c84444d411a1b7d51eec0676483ed73ffee1e6c58ff2e32ee77f6
verified: 8/19/2026, 9:35:04 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