Waha (npm) MCP Server

waha-mcp npm v3.0.0

Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

MCP server for WAHA (WhatsApp HTTP API)

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 63

Each tool and what it can reach — statically extracted from the published source.

  • waha_forward_messagenetwork egress
  • ask_user_via_whatsappno sensitive capability
  • waha_add_group_participantsno sensitive capability
  • waha_add_label_to_chatno sensitive capability
  • waha_archive_chatno sensitive capability
  • waha_block_contactno sensitive capability
  • waha_check_auth_statusno sensitive capability
  • waha_check_number_existsno sensitive capability
  • waha_clear_chatno sensitive capability
  • waha_create_groupno sensitive capability
Show 53 more tools ↓
  • waha_create_labelno sensitive capability
  • waha_create_sessionno sensitive capability
  • waha_delete_chatno sensitive capability
  • waha_delete_labelno sensitive capability
  • waha_delete_messageno sensitive capability
  • waha_delete_sessionno sensitive capability
  • waha_demote_group_participantno sensitive capability
  • waha_edit_messageno sensitive capability
  • waha_get_chatno sensitive capability
  • waha_get_contactno sensitive capability
  • waha_get_contactsno sensitive capability
  • waha_get_groupno sensitive capability
  • waha_get_group_invite_codeno sensitive capability
  • waha_get_group_participantsno sensitive capability
  • waha_get_labelsno sensitive capability
  • waha_get_messagesno sensitive capability
  • waha_get_presenceno sensitive capability
  • waha_get_profile_pictureno sensitive capability
  • waha_get_qr_codeno sensitive capability
  • waha_get_sessionno sensitive capability
  • waha_leave_groupno sensitive capability
  • waha_list_chatsno sensitive capability
  • waha_list_groupsno sensitive capability
  • waha_list_sessionsno sensitive capability
  • waha_logout_sessionno sensitive capability
  • waha_mark_as_readno sensitive capability
  • waha_mute_chatno sensitive capability
  • waha_pin_chatno sensitive capability
  • waha_promote_group_participantno sensitive capability
  • waha_react_to_messageno sensitive capability
  • waha_remove_group_participantsno sensitive capability
  • waha_remove_label_from_chatno sensitive capability
  • waha_request_pairing_codeno sensitive capability
  • waha_restart_sessionno sensitive capability
  • waha_revoke_group_inviteno sensitive capability
  • waha_send_contactno sensitive capability
  • waha_send_fileno sensitive capability
  • waha_send_imageno sensitive capability
  • waha_send_locationno sensitive capability
  • waha_send_pollno sensitive capability
  • waha_send_statusno sensitive capability
  • waha_send_textno sensitive capability
  • waha_send_videono sensitive capability
  • waha_send_voiceno sensitive capability
  • waha_set_presenceno sensitive capability
  • waha_star_messageno sensitive capability
  • waha_start_sessionno sensitive capability
  • waha_start_typingno sensitive capability
  • waha_stop_sessionno sensitive capability
  • waha_stop_typingno sensitive capability
  • waha_update_group_descriptionno sensitive capability
  • waha_update_group_pictureno sensitive capability
  • waha_update_group_subjectno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v3.0.0 latest A 95/100 0 1.13.0 2026-09-08

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/waha-mcp/badge.svg)](https://mcptrustchecker.com/registry/waha-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/waha-mcp"><img src="https://mcptrustchecker.com/registry/waha-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/waha-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan waha-mcp --online

Use the free API → How scoring works

Other implementations of Waha 2

Independent packages implementing the same tool, scanned with the same engine. Compare all 3 side by side →

More in Developer Tools