Remote MCP · Endpoint

monit.rs MCP server

No. monit.rs answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://monit.rs/integrations/mcp

The last check completed an MCP handshake.

Registry name
rs.monit/monit-rs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
352 ms
Tools exposed
22 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Schema-aware API monitoring: diff OpenAPI specs for breaking changes, manage endpoints.
Website
https://monit.rs/
Listing
From the official MCP registry (active).
Recent checks of monit.rs
CheckedResultHandshake
1 hour agoHandshake completed352 ms
2 days agoHandshake completed404 ms
5 days agoHandshake completed349 ms
7 days agoHandshake completed393 ms
9 days agoHandshake completed418 ms
11 days agoHandshake completed378 ms
13 days agoHandshake completed345 ms
15 days agoHandshake completed429 ms
17 days agoHandshake completed334 ms
19 days agoHandshake completed299 ms
20 days agoHandshake completed368 ms
21 days agoHandshake completed329 ms
23 days agoHandshake completed307 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.

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