net.letsbot/mcp
LetsBot
Is the LetsBot MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-01.
WhatsApp Business messaging, live chat, chatbots, campaigns and CRM for a LetsBot workspace.
needs auth probed 2026-11-01 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32000,"message":"Authentication required. Provide API key via Authorization:- Endpoint
- https://letsbot.net/mcp (streamable-http)
- Host
- letsbot.net
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://letsbot.net/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server letsbot.net, PKCE S256, grants authorization_code, refresh_token.
Scopes full-access.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://letsbot.net/en/whatsapp-mcp.html
- Registry
- active, updated 2026-10-31 · registry entry
Compare this server with others.
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.