Remote MCP · Endpoint

ASAPDevs MCP server

No. ASAPDevs answered an MCP handshake 38 minutes ago.

UpLast checked 38 minutes ago

Server URL

https://asapdevs.it/api/mcp

The last check completed an MCP handshake.

Registry name
it.asapdevs/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
181 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Read-only: ASAPDevs offers, case studies, blog search, pricing and contact (Polish software house).
Listing
From the official MCP registry (active).
Recent checks of ASAPDevs
CheckedResultHandshake
38 minutes agoHandshake completed181 ms
3 days agoHandshake completed169 ms
13 days agoHandshake completed244 ms
13 days agoHandshake completed134 ms
15 days agoHandshake completed129 ms
16 days agoHandshake completed223 ms
17 days agoHandshake completed1.48 s
18 days agoHandshake completed115 ms
18 days agoHandshake completed265 ms
20 days agoHandshake completed334 ms
22 days agoHandshake completed633 ms
25 days agoHandshake completed138 ms
27 days agoHandshake completed229 ms

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