mcpcost

ai.delivr/delivr

Delivr

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

Person-level intent, audiences, website visitors and campaign results from your Delivr account.

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

Streamable HTTP error: Error POSTing to endpoint: {"error":"no credential presented"}
Endpoint
https://api.delivr.ai/mcp (streamable-http)
Host
api.delivr.ai
Getting access
OAuth without dynamic client registration. Ask the publisher for a client id first; with it, a client can run the consent.
Authorization server auth.delivr.ai, PKCE S256, grants authorization_code, refresh_token.
Scopes identity:read audiences:read audiences:write campaigns:read campaigns:write data_sources:read domains:read domains:write exports:read exports:write fields:read integrations:read lists:read lists:write members:read members:write topics:read topics:write intent:read projects:write.
Read from the server's public OAuth metadata, without a token. Method.
Website
https://docs.delivr.ai/docs/connect-mcp
Registry
active, updated 2026-11-09 · registry entry

Compare this server with others.

More servers

Servers that mention delivr.

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.