Remote MCP · Endpoint

io.github.cyanheads/congressgov-mcp-server MCP server

No. io.github.cyanheads/congressgov-mcp-server answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://congressgov.caseyjhand.com/mcp

The last check completed an MCP handshake.

Registry name
io.github.cyanheads/congressgov-mcp-server
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
134 ms
Tools exposed
10 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Access U.S. congressional data (bills, votes, members, committees) via MCP.
Repository
https://github.com/cyanheads/congressgov-mcp-server
Listing
From the official MCP registry (active).
Recent checks of io.github.cyanheads/congressgov-mcp-server
CheckedResultHandshake
1 hour agoHandshake completed134 ms
2 days agoHandshake completed88 ms
4 days agoHandshake completed89 ms
5 days agoHandshake completed70 ms
7 days agoHandshake completed82 ms
8 days agoHandshake completed586 ms
9 days agoHandshake completed110 ms
12 days agoHandshake completed75 ms
13 days agoHandshake completed154 ms
15 days agoHandshake completed148 ms
16 days agoHandshake completed225 ms
18 days agoHandshake completed65 ms
19 days agoHandshake completed76 ms
20 days agoHandshake completed68 ms
20 days agoHandshake completed120 ms
21 days agoHandshake completed101 ms
22 days agoHandshake completed84 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.

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 io.github.cyanheads/congressgov-mcp-server and makes no claim about it beyond what these checks measured.