now.mails/mailapi
Mails.now
Is the Mails.now MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-15.
Provision domains, mailboxes, and run email sequencer campaigns via remote MCP.
needs auth probed 2026-11-15 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint:
- Endpoint
- https://mails.now/mcp/mailapi (streamable-http)
- Host
- mails.now
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://mails.now/mcp/mailapi registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server mails.now, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp:use.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://mails.now/mcp
- Registry
- active, updated 2026-11-15 · registry entry
Compare this server with others.
More servers
Servers that mention mails.
- Getlead ad.getle/leads · alive
- CommSync ai.commsync/commsync · needs auth
- Fiber AI ai.fiber/mcp · alive
- MailJunky ai.mailjunky/mcp · needs auth
- ai.powerline/inbox-preview · alive
- ScamVerify Threat Verification ai.scamverify/mcp · no DNS
- Shipstar ai.shipstar/mcp · needs auth
- ai.verifox/email-verifier · alive
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.