Remote MCP · Endpoint

apiwatch MCP server

No. apiwatch answered an MCP handshake 42 minutes ago.

UpLast checked 42 minutes ago

Server URL

https://apiwatch.reignventures.co/mcp

The last check completed an MCP handshake.

Registry name
io.github.ReignVentures/apiwatch
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.01 s
Tools exposed
7 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Is this model or API still safe to call? Retirement and breaking change dates, with the fix.
Listing
From the official MCP registry (active).
Recent checks of apiwatch
CheckedResultHandshake
42 minutes agoHandshake completed1.01 s
3 days agoHandshake completed174 ms
12 days agoHandshake completed142 ms
12 days agoHandshake completed133 ms
14 days agoHandshake completed89 ms
15 days agoHandshake completed569 ms
16 days agoHandshake completed106 ms
17 days agoHandshake completed154 ms
18 days agoHandshake completed149 ms
19 days agoHandshake completed122 ms
22 days agoHandshake completed173 ms
25 days agoHandshake completed127 ms
27 days agoHandshake completed201 ms

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

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