mcpbeat Sign in

Leafle MCP Server

by nanosheep Your server? Claim it
answering

Leafle is answering right now. Last checked moments ago.

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

Uptime history 89 days of history · worst day 93%
89 days agonow
100.0%
Uptime 24h
92 of 92 checks
—
Tools
hidden behind auth
190 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 0 min ago.

run in your terminal
claude mcp add leafle --transport http https://leafle.nanosheep.net/mcp/
Settings → Connectors → Add custom connector, then paste this address
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
{
  "servers": {
    "leafle": {
      "type": "http",
      "url": "https://leafle.nanosheep.net/mcp/"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://leafle.nanosheep.net/mcp/ streamable-http sign-in 187 ms 0 min ago

Alternatives to Leafle

same job, measured the same way
Siftivo
by siftivo

Book recommendations from your reading history, plus your shelves, ratings and series order.

16 tools answering
Present Picker
by thepresentpicker

Gift recommendations matched to the person, the occasion, and your budget.

3 tools answering
Curated
by curated

Keep and share lists of recommendations with your own notes, and read lists from people you trust.

50 tools answering
GapCite
by gapcite

Track AI mentions and recommendations of your business, and find what to fix with GapCite.

answering
Talent-Augmenting Layer
by angelo-leone

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

answering
Epic Fantasy 101 Booklist
by netlify-acenes-of-sparta-the-dragon-slayer

Fantasy book recommendations: ranked reading list of 101 epic fantasy books like the ones you love.

3 tools answering
Semver Checks
by kyungseopk1m

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

535 installs/wk local only
Savee
by savee

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

answering

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 92 of 92 checks got a reply (100.0%), average response time 190 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 in the form 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 190 ms on average, which is faster than 70% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.