Remote MCP · Endpoint

SaaSCity MCP server

No. SaaSCity answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://saascity.io/api/mcp

The last check completed an MCP handshake.

Registry name
io.saascity/saascity
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
323 ms
Tools exposed
23 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Audit your site, pick from 1,600+ launch directories by DR and link type, and list on SaaSCity.
Listing
From the official MCP registry (active).
Recent checks of SaaSCity
CheckedResultHandshake
43 minutes agoHandshake completed323 ms
8 days agoHandshake completed181 ms
9 days agoHandshake completed323 ms
11 days agoHandshake completed327 ms
12 days agoHandshake completed446 ms
13 days agoHandshake completed315 ms
14 days agoHandshake completed139 ms
14 days agoHandshake completed372 ms
16 days agoHandshake completed193 ms
19 days agoHandshake completed313 ms
21 days agoHandshake completed334 ms
24 days agoHandshake completed483 ms
26 days agoHandshake completed137 ms
28 days agoHandshake completed312 ms

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

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