Remote MCP · Endpoint

Legislation MCP server

No. Legislation answered an MCP handshake 54 minutes ago.

UpLast checked 54 minutes ago

Server URL

https://mcp.delilahusa.com/

The last check completed an MCP handshake.

Registry name
com.delilahusa/legislation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
763 ms
Tools exposed
41 tools
Uptime, last 30 days
100% from 16 checks
Described by its publisher as
U.S. bills, roll-call votes, legislators and 2026 elections for all 50 states, D.C. and Congress.
Listing
From the official MCP registry (active).
Recent checks of Legislation
CheckedResultHandshake
54 minutes agoHandshake completed763 ms
2 days agoHandshake completed199 ms
4 days agoHandshake completed278 ms
5 days agoHandshake completed154 ms
7 days agoHandshake completed138 ms
8 days agoHandshake completed137 ms
9 days agoHandshake completed630 ms
12 days agoHandshake completed96 ms
13 days agoHandshake completed191 ms
15 days agoHandshake completed149 ms
17 days agoHandshake completed174 ms
18 days agoHandshake completed97 ms
19 days agoHandshake completed96 ms
20 days agoHandshake completed240 ms
21 days agoHandshake completed129 ms
21 days agoHandshake completed133 ms

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

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