Remote MCP · Endpoint

Shelfclub MCP server

No. Shelfclub answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.shelfclub.app/mcp

The last check completed an MCP handshake.

Registry name
app.shelfclub/books
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search a catalog of 1.7 million books and find books by mood, vibe, pace or genre. Read-only.
Website
https://shelfclub.app/
Listing
From the official MCP registry (active).
Recent checks of Shelfclub
CheckedResultHandshake
1 hour agoHandshake completed97 ms
11 hours agoHandshake completed102 ms
1 day agoHandshake completed126 ms
2 days agoHandshake completed96 ms
4 days agoHandshake completed96 ms
7 days agoHandshake completed130 ms
9 days agoHandshake completed100 ms
12 days agoHandshake completed98 ms
14 days agoHandshake completed101 ms
16 days agoHandshake completed98 ms
18 days agoHandshake completed94 ms
20 days agoHandshake completed88 ms
22 days agoHandshake completed94 ms
23 days agoHandshake completed168 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Related

All hosted MCP serversGlide connector for AI assistantsGlide for AI agents

Listing data comes from the official MCP registry. Glide is not affiliated with Shelfclub and makes no claim about it beyond what these checks measured.