Warning

22/100

2 days ago

CacheBash

Item: CacheBash
Rating: 22
Author: M8ven

An MCP server that coordinates AI coding agents with mobile notifications, enabling task queues, inter-agent messaging, session monitoring, and human-in-the-loop approvals.

→ rezzedai/cachebash · 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 push why connect →

Who stands behind it

rezzedai

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: DISPATCHER_WEBHOOK_SECRET. We can’t prove the destination matches the brand the credential belongs to.

🚨

Hardcoded credentials detected

1 live-looking API key in source: 1 Google API key

🔐

You'll be asked for 4 credentials: DISPATCHER_WEBHOOK_SECRET, GITHUB_TOKEN, GITHUB_WEBHOOK_SECRET, REZZED_AGENT_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.

configADMIN_USER_ID

configAUTH_MODE

configCACHEBASH_PROFILE

configCACHEBASH_TENANT_ID

configCLOUD_RUN_URL

🔐 secretDISPATCHER_WEBHOOK_SECRET

configDISPATCHER_WEBHOOK_URL

configDISPATCH_CALLER_BOUNDARY_TIMEOUT_MS

configFIREBASE_PROJECT_ID

configGCP_PROJECT_ID

configGITHUB_FEEDBACK_PAT

configGITHUB_PROJECT_ID

configGITHUB_REPO

configGITHUB_REPO_NAME

configGITHUB_REPO_OWNER

🔐 secretGITHUB_TOKEN

🔐 secretGITHUB_WEBHOOK_SECRET

configINTERNAL_OIDC_AUDIENCE

configLITE_URL

configOAUTH_ALLOWED_EMAILS

configOAUTH_ALLOWED_UIDS

configOAUTH_ISSUER

🔐 secretREZZED_AGENT_KEY

configSCHEDULER_SA_EMAIL

configWAKE_HOST_URL

Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.

deployPORT

// 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

144/144 tools missing one or more hints — dispatch_get_tasks (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); relay_get_messages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); relay_get_dead_letters (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +141 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.

License file

No license file

Add a LICENSE file (MIT, Apache-2.0, etc.).

No hardcoded API keys

1 live-looking API key in source: 1 Google API key

Move secrets to environment variables (process.env.X) or your secret manager.

Tool test coverage

81/144 tools referenced in tests (56%)

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 (DISPATCHER_WEBHOOK_SECRET → dynamic)

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

Domain consistency

npm scope @cachebash doesn't match GitHub owner rezzedai

Use the same org name across GitHub, npm, and your homepage so users can verify the publisher.

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 7 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/rezzedai-cachebash-9n4wzj?variant=verified)](https://m8ven.ai/mcp/rezzedai-cachebash-9n4wzj)

Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.

commit: 1dc48584581ce1f06d463b370e2734b70712fcfa

code hash: a85ce99c5e5a6e3c3f1b8ac7000277cdb0daeab34177650d13a2b9fcec572aac

verified: 8/17/2026, 7:39:34 PM

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