io.github.nicolascroce/keepsake

Keepsake

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

Keepsake (keepsake.place), the app where creators and solo entrepreneurs empty their heads

needs auth probed 2026-11-15 · HTTP 401 · Bearer

The server needs auth, so these tool definitions were read from the publisher's open-source package npm:keepsake-mcp, started in a container with placeholder values and the network off, on 2026-11-15. Tool definitions do not depend on the token, so this is what an authorized user loads, unless the server hides tools by plan or role.

Streamable HTTP error: Error POSTing to endpoint: {"jsonrpc":"2.0","error":{"code":-32001,"message":"Missing Authorization header."},"id":null}

Endpoint

https://app.keepsake.place/api/mcp (streamable-http)

Host

app.keepsake.place

Of a 1M window

4.4 % of a 1M context window

Getting access

OAuth with dynamic client registration. A client such as Claude Code, Cursor or npx mcpcost auth https://app.keepsake.place/api/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 app.keepsake.place, PKCE S256, grants authorization_code, refresh_token.
Scopes mcp.
Read from the server's public OAuth metadata, without a token. Method.

Repository

https://github.com/nicolascroce/keepsake-mcp

Website

https://keepsake.place/en/ai

Registry

active, updated 2026-11-04 · registry entry

Changes

4 recorded, reachable in 4 of them. A row is added when the result, the tool count or the cost changes.

Compare this server with others.