wa-bridge (xbirimensah/whatsapp-bridge) 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

wa-bridge

A self-hosted WhatsApp bridge that exposes a stdio MCP server with ~20 tools for reading conversations, sending messages, managing groups, contacts, and aliases, enabling AI agents to operate WhatsApp directly.

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

xbirimensah

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

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
1 flow detected: API_TOKEN. We can’t prove the destination matches the brand the credential belongs to.
🔐
You'll be asked for 10 credentials: API_TOKEN, AUTOREPLY_LLM_API_KEY, AUTOREPLY_NOTIFY_WEBHOOK_TOKEN, AUTOREPLY_SLACK_BOT_TOKEN, AUTOREPLY_TELEGRAM_BOT_TOKEN, AUTOREPLY_TOKEN, AUTOREPLY_WA_API_TOKEN, OPENAI_API_KEY, WEBHOOK_TOKEN, WHATSAPP_BRIDGE_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// known CVEs in dependencies2 low

Disclosed vulnerabilities in this server's declared npm dependencies (via OSV). Whether each is reachable depends on the installed versions.

lowfastify@5.8.5GHSA-3m5p-2c4r-xxw2

fastify vulnerable to X-Forwarded-* spoofing under trustProxy hop-count

lowfastify@5.8.5GHSA-w2qp-rph6-63g4

fastify vulnerable to schema validation bypass via root primitive coercion mismatch

Depend on this server? Get alerted when its CVEs change.Watch this server free →
// 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.
🔐 secretAPI_TOKENgenerates and writes it to .env
configAUTOREPLY_ALLOW_GROUP_AUTOgroup chats are never auto-answered unless AUTOREPLY_ALLOW_GROUP_AUTO=1, and even then only when the operator is explicitly @-mentioned
configAUTOREPLY_AUTO_SEND_COOLDOWN_MSan auto-send already happened in this chat within AUTOREPLY_AUTO_SEND_COOLDOWN_MS (default 10 min)
configAUTOREPLY_CLAUDE_BIN
configAUTOREPLY_CODEX_BIN
configAUTOREPLY_DATA_DIR
configAUTOREPLY_DEFAULT_SESSION
configAUTOREPLY_HISTORY_MESSAGE_LIMIT
configAUTOREPLY_HOST
🔐 secretAUTOREPLY_LLM_API_KEYANTHROPIC_API_KEY or AUTOREPLY_LLM_API_KEY
configAUTOREPLY_LLM_BASE_URL
configAUTOREPLY_LLM_MODEL
configAUTOREPLY_LLM_PROVIDER
configAUTOREPLY_MIN_CONFIDENCEconfidence < AUTOREPLY_MIN_CONFIDENCE
configAUTOREPLY_MODEL
configAUTOREPLY_NOTIFY_CHANNEL
configAUTOREPLY_NOTIFY_WA_SESSION
configAUTOREPLY_NOTIFY_WA_TO
🔐 secretAUTOREPLY_NOTIFY_WEBHOOK_TOKEN
configAUTOREPLY_NOTIFY_WEBHOOK_URL
configAUTOREPLY_PERSONAL_CONTEXT_LIMIT
configAUTOREPLY_PERSONAL_CONTEXT_MAX_CHARS
configAUTOREPLY_PORT
configAUTOREPLY_SECOND_BRAIN_ROOT
🔐 secretAUTOREPLY_SLACK_BOT_TOKEN
configAUTOREPLY_SLACK_CHANNEL
configAUTOREPLY_SLACK_WEBHOOK_URL
configAUTOREPLY_STYLE_CORPUS_PATH
🔐 secretAUTOREPLY_TELEGRAM_BOT_TOKEN
configAUTOREPLY_TELEGRAM_CHAT_ID
🔐 secretAUTOREPLY_TOKEN
configAUTOREPLY_WA_API_BASE
🔐 secretAUTOREPLY_WA_API_TOKEN
configAUTOREPLY_YT_TRANSCRIPT_SCRIPT
configHOSTUse 0.0.0.0 only behind a reverse proxy. Set WA_ALLOW_PUBLIC=1 to override the loopback guard.
🔐 secretOPENAI_API_KEYmodel + OPENAI_API_KEY (key optional for local endpoints)
configPYTHON_BIN
configWA_BACKUP_DIR
configWA_BACKUP_KEEP
configWA_CONTACTS_TSV
configWA_DB_PATH
configWA_FORCE_HISTORY_SYNC_ON_RESTORE
configWA_FORCE_REDUMP
configWA_TZdetects your system timezone and writes it as to .env (e.g. Europe/Berlin)
configWA_UPDATE_BRANCH
🔐 secretWEBHOOK_TOKENIf is set, it arrives as Authorization: Bearer <token> so the receiver can verify origin. Three attempts, 1s/3s backoff, 5s timeout per attempt. Outbound sends do not fire the webhook.
configWEBHOOK_URLPings the configured WEBHOOK_URL
configWHATSAPP_BRIDGE_BASE
🔐 secretWHATSAPP_BRIDGE_TOKEN
configWHATSAPP_BRIDGE_URL
configEMBEDDING_PROVIDER
configVOYAGE_EMBEDDING_MODEL
configOPENAI_EMBEDDING_MODEL
Deployment configuration, supplied by whoever hosts the server. Users are not asked for these.
deployPORT
deploySUPABASE_URL
deploySUPABASE_SERVICE_ROLE_KEY
// 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 — list_sessions (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_conversations (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); read_conversation (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.

Tool test coverage

Only 0/20 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 sent to a request target we could not resolve (API_TOKEN → 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.

Dependency freshness

1/8 production deps stale: qrcode-terminal@2022-06-25 (4.2y)

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 4 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/xbirimensah/whatsapp-bridge)](https://m8ven.ai/mcp/xbirimensah/whatsapp-bridge)
Shows your grade and updates automatically. Prefer no grade? Append ?variant=verified to the badge URL.
commit: 4f10035da2c592a6b29168a30c2b01461bf8ad62
code hash: 6314624529047b85eef8dad8d480b8dcf391b7849bcca0748b9eff65f165b3de
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