io.github.Yolofmeister-git/deckly
Deckly
Is the Deckly MCP server down? No. It is up and needs auth (HTTP 401), probed 2026-11-06.
Design presentations, landing pages and social ads with Deckly's tools, then share or export PDF.
needs auth probed 2026-11-14 · unchanged since 2026-11-06 · HTTP 401 · Bearer
Streamable HTTP error: Error POSTing to endpoint: {"detail":"Missing token: send Authorization: Bearer <access_token>.","code":"auth_token_missing"}- Endpoint
- https://deckly-backend.onrender.com/mcp (streamable-http)
- Host
- deckly-backend.onrender.com
- Getting access
- OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://deckly-backend.onrender.com/mcp registers itself and opens the consent page; the publisher has nothing to set up for you. The publisher's guide to getting access.
Authorization server deckly-backend.onrender.com, PKCE S256, grants authorization_code.
Scopes deckly.
Read from the server's public OAuth metadata, without a token. Method. - Website
- https://www.decklyai.com/developers
- Registry
- active, updated 2026-11-04 · registry entry
- Changes
- 2 recorded, reachable in 2 of them. A row is added when the result, the tool count or the cost changes.
Compare this server with others.
More servers
Servers that mention presentations or landing.
- Presentations.AI ai.presentations/presentations-ai · needs auth
- ai.simplepages/simplepages · needs auth
- Slideless ai.slideless/mcp · needs auth
- ai.smithery/IndianAppGuy-magicslide-mcp · not found
- ai.smithery/IndianAppGuy-magicslide-mcp-actual-test · not found
- Twistly ai.twistly/mcp · needs auth
- WebAnatomy ai.webanatomy/webanatomy · server error
- FormEdge app.formedge/formedge · needs auth
History
We add a row when the result changes. A server with no change keeps its last row.
| Probed | Result | Init | Tools | Claude | o200k |
|---|---|---|---|---|---|
| 2026-11-06 11:23 | needs auth | ||||
| 2026-11-05 11:23 | needs auth |
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.