Remote MCP · Endpoint

UnblockingAPI MCP server

No. UnblockingAPI answered an MCP handshake 52 minutes ago.

UpLast checked 52 minutes ago

Server URL

https://mcp.unblockingapi.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.unblockingapi/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
297 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Fetch bot-protected and JavaScript-heavy pages for AI agents, or parse them to JSON with templates.
Listing
From the official MCP registry (active).
Recent checks of UnblockingAPI
CheckedResultHandshake
52 minutes agoHandshake completed297 ms
3 days agoHandshake completed297 ms
12 days agoHandshake completed308 ms
13 days agoHandshake completed316 ms
14 days agoHandshake completed310 ms
15 days agoHandshake completed487 ms
17 days agoHandshake completed309 ms
18 days agoHandshake completed307 ms
18 days agoHandshake completed299 ms
20 days agoHandshake completed297 ms
22 days agoHandshake completed298 ms
25 days agoHandshake completed512 ms
27 days agoHandshake completed304 ms
29 days agoCredentials required—

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.

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