is.lantern/lantern
Lantern
Is the Lantern MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-10-26.
Lantern is an AI visibility platform for ecommerce brands.
needs auth probed 2026-11-14 · unchanged since 2026-10-26 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"message":"Authorization: Bearer <token> header is required.","error":"Unauthorized","statusCode":401}- Endpoint
- https://agent.lantern.is/agent/mcp (streamable-http)
- Host
- agent.lantern.is
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://agent.lantern.is/agent/mcp registers itself and opens the consent page; the publisher has nothing to set up for you.
Authorization server agent.lantern.is, PKCE S256, grants authorization_code, refresh_token.
Scopes read:findings read:rankings draft:content draft:reddit publish:website publish:reddit edit:website delegated:ui manage:internal-content manage:brand-voice provision:prospects manage:history-imports manage:curated-opportunities manage:prompts.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://lantern.is/claude-plugin
- Registry
- active, updated 2026-10-15 · registry entry
Compare this server with others.
More servers
Servers that mention lantern.
- Paper Lantern ai.paperlantern/code · needs auth
- Manekami — digital shrine & omikuji io.github.dio6742/manekami · alive
- FluxProof io.github.equinoxaifinance-rgb/fluxproof · alive
- ProofFetch — Cited Web Evidence io.github.equinoxaifinance-rgb/proof-fetch · alive
- Carrier Ledger dev.workers.neoaethel.carrier-ledger/carrier-ledger · alive
- Spectacular Atlas com.spectacularatlas/events · alive
- io.github.lanternrow/tiktok-organic-mcp · alive
- io.github.lanternrow/facebook-pages-mcp · 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.