Remote MCP · Endpoint

Oravan MCP server

No. Oravan answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://oravan.org/api/mcp/mcp

The last check completed an MCP handshake.

Registry name
org.oravan/mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
175 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Nonpartisan U.S. Congress data: bill decodes, rep lookup, bilingual EN/ES, read-only, no accounts.
Listing
From the official MCP registry (active).
Recent checks of Oravan
CheckedResultHandshake
1 hour agoHandshake completed175 ms
2 days agoHandshake completed86 ms
4 days agoHandshake completed125 ms
5 days agoHandshake completed219 ms
7 days agoHandshake completed95 ms
8 days agoHandshake completed89 ms
9 days agoHandshake completed260 ms
12 days agoHandshake completed300 ms
13 days agoHandshake completed120 ms
15 days agoHandshake completed114 ms
17 days agoHandshake completed3.44 s
18 days agoHandshake completed121 ms
19 days agoHandshake completed123 ms
20 days agoHandshake completed154 ms
21 days agoHandshake completed117 ms
21 days agoHandshake completed120 ms
23 days agoHandshake completed107 ms

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

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