Remote MCP · Endpoint

Congress Member Votes MCP server

No. Congress Member Votes answered an MCP handshake 4 hours ago.

UpLast checked 4 hours ago

Server URL

https://gateway.pipeworx.io/congress-member-votes/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/congress-member-votes
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
138 ms
Tools exposed
47 tools
Uptime, last 30 days
100% from 12 checks
Described by its publisher as
Congress Member Votes -- how each U.S. House member voted, from the U.S. House Clerk's roll-call…
Listing
From the official MCP registry (active).
Recent checks of Congress Member Votes
CheckedResultHandshake
4 hours agoHandshake completed138 ms
3 days agoHandshake completed101 ms
12 days agoHandshake completed136 ms
13 days agoHandshake completed85 ms
14 days agoHandshake completed127 ms
15 days agoHandshake completed425 ms
16 days agoHandshake completed129 ms
17 days agoHandshake completed144 ms
18 days agoHandshake completed176 ms
20 days agoHandshake completed150 ms
22 days agoHandshake completed1.10 s
25 days agoHandshake completed291 ms

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

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