{"id":"felixisaac-whatsapp-mcp-extended","name":"whatsapp-mcp-extended","af_score":57.5,"security_score":38.0,"reliability_score":36.2,"what_it_does":"An extended Model Context Protocol (MCP) server that enables programmatic interaction with WhatsApp via ~41 MCP tools (messaging, media, reactions, editing/deleting, chat history, contacts, group management, polls, presence, profile data, blocklist, and “newsletters/channels”). It also includes a webhook system for incoming events with HMAC-SHA256 signatures and retry/backoff, plus a small webhook UI and supporting components (WhatsApp bridge in Go, SQLite storage).","best_when":"You want a local/self-hosted WhatsApp automation interface for agents and tools (MCP + webhooks) and can manage operational concerns (hosting, secrets, monitoring).","avoid_when":"You cannot secure webhook endpoints/signing secrets, or you need documented, fine-grained rate limiting and robust API contracts for large-scale usage.","last_evaluated":"2026-03-30T15:40:16.404735+00:00","has_mcp":true,"has_api":true,"auth_methods":["MCP server run command (local process)","Webhook verification via HMAC-SHA256 signature (per README)"],"has_free_tier":false,"known_gotchas":["WhatsApp bridging/connectivity issues may cause failures (e.g., QR/authentication flow and “connected” state).","Tool semantics may not be idempotent (e.g., sending messages/reactions) unless the underlying implementation explicitly de-duplicates.","Webhook matching supports regex/contains; incorrect patterns could cause unintended triggers.","History sync/request older messages may be rate/availability dependent; retries may re-deliver events unless consumer deduplicates."],"error_quality":0.0}