io.github.proteuscrypto/wapliss
Wapliss WhatsApp
Is the Wapliss WhatsApp MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-12.
Read, summarize and send your own WhatsApp messages from AI assistants (OAuth 2.1).
needs auth probed 2026-11-14 · unchanged since 2026-11-12 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Unauthorized: Bearer token is required. Authenticate via OA- Endpoint
- https://wapliss.com/mcp/v1 (streamable-http)
- Host
- wapliss.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://wapliss.com/mcp/v1 registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server wapliss.com, PKCE S256, grants authorization_code, refresh_token.
Scopes wapliss:mcp whatsapp:read whatsapp:write.
Read from the server's public OAuth metadata, without a token. Method. - Repository
- https://github.com/proteuscrypto/wapliss-for-m365-copilot
- Website
- https://wapliss.com/integrations
- Registry
- active, updated 2026-11-12 · registry entry
Compare this server with others.
More servers
Servers that mention whatsapp.
- DarkFunnels ai.darkfunnels/whatsapp-sales-agent · needs auth
- DarkFunnels documentation ai.darkfunnels/docs · alive
- Fine Structure ai.finestructure/fine-structure · alive
- ai.izap/whatsapp · needs auth
- ai.kontato/kontato · needs auth
- Talpy Aya — AI recruiter (WhatsApp interviews) ai.talpy/aya · alive
- NudgeBell app.nudgebell/reminders · needs auth
- TBit app.tbit/tbit · needs auth
Badge for the README
The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.
A mail when this server changes
Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.
For the publisher
- The server answers HTTP 401 to an unauthenticated initialize, so the probe cannot list its tools. That is correct for a private server. Some public servers answer initialize and tools/list without credentials and ask for auth on tool calls only; those get a token count here.
Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.