mcpcost

io.github.Nodium-io/whatsapp

Nodium WhatsApp

Is the Nodium WhatsApp MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-11.

Operate WhatsApp from an agent: read conversations and contacts, send messages, by API key.

needs auth probed 2026-11-14 · unchanged since 2026-11-11 · HTTP 401 · Bearer

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","id":null,"error":{"code":-32600,"message":"Authorization: Bearer <your Nodium API key (nod_…
Endpoint
https://nodium.io/api/v1/mcp (streamable-http)
Host
nodium.io
Getting access
A key or token from the publisher, sent in the Authorization header (Bearer). The server publishes no OAuth metadata. Store the key once: npx mcpcost auth https://nodium.io/api/v1/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method.
Repository
https://github.com/Nodium-io/sdk
Website
https://nodium.io/en/docs/api/guide/mcp
Registry
active, updated 2026-11-10 · registry entry

Compare this server with others.

More servers

Servers that mention whatsapp.

Badge for the README

mcpcost: needs auth

The result of the latest probe, the tool count and the token cost. The feed has an entry for every probe that changed them.

Atom feed

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

Fixed something? Probe it now, with the same steps as the daily run. This page updates with the next daily run.