Remote MCP · Endpoint

RevExOS MCP server

No. RevExOS answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://revexos.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.revexos/revexos
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
102 ms
Tools exposed
8 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Quote-to-cash tools: parse invoices and POs, match POs to invoices, collection emails, billing math.
Listing
From the official MCP registry (active).
Recent checks of RevExOS
CheckedResultHandshake
1 hour agoHandshake completed102 ms
16 hours agoHandshake completed105 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed82 ms
6 days agoHandshake completed74 ms
9 days agoHandshake completed796 ms
11 days agoHandshake completed144 ms
13 days agoHandshake completed117 ms
15 days agoHandshake completed789 ms
17 days agoHandshake completed870 ms
19 days agoHandshake completed103 ms
21 days agoHandshake completed767 ms
23 days agoHandshake completed82 ms
24 days agoHandshake completed1.09 s
25 days agoHandshake completed77 ms

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

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