mcpbeat Sign in

Leafle MCP Server

by nanosheep Your server? Claim it
answering

Leafle is answering right now. Last checked 1 min ago.

Personalised book recommendations, filtered to what's on your public library's shelf right now.

Uptime history 30 days of history · worst day 97%
30 days agonow
100.0%
Uptime 24h
93 of 93 checks
Tools
hidden behind auth
232 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check Leafle every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 1 min ago.

run in your terminal
claude mcp add leafle --transport http https://leafle.nanosheep.net/mcp/
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "leafle": {
      "url": "https://leafle.nanosheep.net/mcp/"
    }
  }
}
~/.codex/config.toml
[mcp_servers.leafle]
url = "https://leafle.nanosheep.net/mcp/"
.cursor/mcp.json
{
  "mcpServers": {
    "leafle": {
      "url": "https://leafle.nanosheep.net/mcp/"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "leafle": {
      "url": "https://leafle.nanosheep.net/mcp/"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://leafle.nanosheep.net/mcp/ streamable-http needs key 212 ms 1 min ago

Alternatives to Leafle

same job, measured the same way
Talent-Augmenting Layer
by angelo-leone

Personalised AI augmentation system — makes you better at your work, not dependent on AI

answering
C
Compensation Professional — compensation library, answers, and wage-compliance data
by compensationprofessional

Read-only access to Compensation Professional's compensation-focused book library, query-shaped...

6 tools answering
Semver Checks
by kyungseopk1m

Detect breaking changes in your TypeScript library's public API and recommend the SemVer bump.

43 installs/wk local only
Savee
by savee

Read your Savee saves, boards and home feed, and search its public library. Read-only.

answering
Siftivo
by siftivo

Search books, authors and series, get recommendations, and manage your own reading shelves.

12 tools answering
What Matters
by blackdogranch

Your personal action-item list — what you owe and what you're owed. AI proposes; you approve.

6 tools answering
Leaf
by readwithleaf

AI assistant integration for Leaf — track books, log reading sessions, and manage your library.

answering
Algolia Search
by mcparmory

Search multiple indices, index data, and get personalized recommendations

293 installs/wk local only

Leafle — questions

Answers built from our own checks of this server.

Why is there no tool list for Leafle?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.
Is Leafle working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 93 of 93 checks got a reply (100.0%), average response time 232 ms. The bar chart above shows every period we have measured.
How do I connect Leafle?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to Leafle?
No API key is involved. Leafle answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is Leafle?
It answers our handshake in 232 ms on average, which is faster than 63% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.