Remote MCP · Endpoint

Toolaby docs MCP server

No. Toolaby docs answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://toolaby.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.toolaby/docs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
224 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Search and read Toolaby's docs: payments, licences and paywalls for Chrome extensions.
Listing
From the official MCP registry (active).
Recent checks of Toolaby docs
CheckedResultHandshake
6 hours agoHandshake completed224 ms
3 days agoHandshake completed203 ms
12 days agoHandshake completed202 ms
13 days agoHandshake completed284 ms
14 days agoHandshake completed195 ms
15 days agoHandshake completed296 ms
16 days agoHandshake completed181 ms
17 days agoHandshake completed687 ms
18 days agoHandshake completed228 ms
20 days agoHandshake completed177 ms
22 days agoHandshake completed198 ms
25 days agoHandshake completed209 ms
27 days agoHandshake completed198 ms
29 days agoHandshake completed208 ms

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

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 Toolaby docs and makes no claim about it beyond what these checks measured.