Remote MCP · Endpoint

Stophy MCP server

No. Stophy answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://api.stophy.dev/mcp

The last check completed an MCP handshake.

Registry name
io.github.stophydotdev/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
26 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Web scraping API for AI agents.
Repository
https://github.com/stophydotdev/mcp.git
Listing
From the official MCP registry (active).
Recent checks of Stophy
CheckedResultHandshake
5 hours agoHandshake completed26 ms
2 days agoHandshake completed22 ms
4 days agoHandshake completed28 ms
6 days agoHandshake completed30 ms
8 days agoHandshake completed21 ms
10 days agoHandshake completed20 ms
12 days agoHandshake completed31 ms
13 days agoHandshake completed28 ms
14 days agoHandshake completed24 ms
15 days agoHandshake completed22 ms
18 days agoHandshake completed21 ms
20 days agoHandshake completed27 ms
21 days agoHandshake completed21 ms
23 days agoHandshake completed26 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 Stophy and makes no claim about it beyond what these checks measured.