waxum-mcp (imtaqin/waxum-mcp) is an MCP server listed on the M8ven Trust Index. It scores 71 out of 100, grade C. It declares 7 tools. No publisher has claimed this listing.

Back to MCP Trust IndexM8ven
C
Caution
71/100

waxum-mcp

MCP server for WhatsApp that exposes send, read, and media management tools through the waxum REST API gateway, enabling any MCP client to interact with WhatsApp chats and media over stdio.

→ imtaqin/waxum-mcp· listed on glama

Caution. Specific findings reduced this grade. They are listed on the page. 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

imtaqin

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

Glamanot scored here

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
⚠️
Tool descriptions don’t match what handlers do
1 tool describes read intent but its handler mutates — download_media (line 35: mkdir(ctx.mediaDir, { recursive: true }))
✅
No credential exfiltration, no sensitive file access, no obfuscation
Static analysis found nothing flowing your secrets to unexpected places.
🔐
You'll be asked for 1 credential: WAXUM_TOKEN
These are read from process.env at runtime. Make sure you trust where they’ll be sent.
// tools this server exposes7 tools

These names and descriptions are the publisher's own, read from the source code. We print them as written. Our assessment is the findings above, not this list.

download_media

Download a media message (image, video, audio, document, or sticker) to local disk. Pass the `media` object exactly as returned by get_messages. Returns the saved file path and metadata — read the file at that path to inspect its contents.

get_messages

Read message history for a chat or group. Without `q`, returns the most recent messages newest-first. With `q`, full-text searches that keyword within the chat instead. Each message includes the sender's push_name (display name) and, for media messages, a `media` object — pass that whole object to d…

list_chats

List or search known WhatsApp contacts (1:1 chats), with their JID, phone number, and push_name — use this to find a contact's JID by name before sending to or reading from it.

list_groups

List WhatsApp groups this session is a participant of, with their JIDs, subjects, and member lists — use this to find a group's JID by name before sending to or reading from it.

send_file

Send a local file (image, video, audio, document, or sticker) to a WhatsApp contact or group. The file kind is inferred from its mimetype (override with `mimetype` for files with no/wrong extension) and routed to the matching WhatsApp message type automatically.

send_message

Send a plain text message to a WhatsApp contact or group. `to` is a JID (e.g. "6281234567890@s.whatsapp.net" for a contact, "1234567890@g.us" for a group) — use list_groups or list_chats to find one by name.

session_status

Check whether the WhatsApp session is connected and logged in, and get its phone number / display name. Call this first if a send or read fails — the session may be disconnected or not yet paired (pairing/QR setup is done directly against waxum, not through this MCP server).

// 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.
configWAXUM_DATABASE_URLthe MCP server zero-config and restart-safe. Set to
configWAXUM_MEDIA_DIR
configWAXUM_MODETwo ways to point this server at waxum, chosen by (or
configWAXUM_PORT
🔐 secretWAXUM_TOKEN
configWAXUM_WORKDIRSpawn mode uses SQLite by default at <>/waxum.db, keeping
// 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

7/7 tools missing one or more hints — download_media (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); get_messages (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint); list_chats (missing: readOnlyHint, destructiveHint, idempotentHint, openWorldHint), +4 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.

Descriptions match behaviour

1 tool describes read intent but its handler mutates — download_media (line 35: mkdir(ctx.mediaDir, { recursive: true }))

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

Tool inputs are validated

6/7 tool handlers declare input schemas (86%)

Declare an inputSchema with zod/joi/yup on every tool definition.

License file

No license file

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

Tests exist

No test files found

Add tests that exercise each declared tool.

Tool description accuracy

download_media: 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 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/imtaqin/waxum-mcp?variant=verified)](https://m8ven.ai/mcp/imtaqin/waxum-mcp)
Shows verification status without the grade. Want the grade badge instead? Remove ?variant=verified from the URL.
commit: 567c4cb52eb2be6fac6cfb9799e00f3058ddfd5f
code hash: dfa6e07e4f350b9c7940fe4dcfa71cd21bc8b84cf6adf225d12a1f1e1964f2a3
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