Remote MCP · Endpoint

Isbn MCP server

No. Isbn answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://gateway.pipeworx.io/isbn/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/isbn
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
198 ms
Tools exposed
46 tools
Uptime, last 30 days
94.4% from 18 checks
Described by its publisher as
ISBN validation & conversion MCP.
Listing
From the official MCP registry (active).
Recent checks of Isbn
CheckedResultHandshake
2 hours agoHandshake completed198 ms
22 hours agoHandshake completed158 ms
2 days agoHandshake completed202 ms
3 days agoHandshake completed109 ms
4 days agoHandshake completed60 ms
5 days agoHandshake completed120 ms
6 days agoHandshake completed78 ms
8 days agoHandshake completed128 ms
11 days agoHandshake completed58 ms
13 days agoHandshake completed1.77 s
16 days agoHandshake completed69 ms
18 days agoHandshake completed63 ms
20 days agoHandshake completed65 ms
22 days agoHandshake completed67 ms
24 days agoFailed - the request timed out—
26 days agoHandshake completed47 ms
27 days agoHandshake completed58 ms
29 days agoHandshake completed49 ms

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

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.

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