me.leadli/mcp

leadli.me

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

Manage Telegram channels, bots, ad attribution, subscriber reports and landing pages with leadli.me.

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

Streamable HTTP error: Error POSTing to endpoint: {"message":"ACCESS_KEY_INVALID","error":"Unauthorized","statusCode":401}

Endpoint: https://api.leadli.me/api/v1/mcp (streamable-http)
Host: api.leadli.me
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://api.leadli.me/api/v1/mcp --header "Authorization: Bearer …".
Read from the server's public OAuth metadata, without a token. Method.
Website: https://leadli.me/en/guides/mcp-server
Registry: active, updated 2026-11-13 · registry entry

More servers

Servers that mention attribution or subscriber.

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

Stops answering, comes back, tool set or cost changes. One confirmation mail first, a stop link in every mail.

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.