Remote MCP · Endpoint

Regulations.gov MCP server

No. Regulations.gov answered an MCP handshake 44 minutes ago.

UpLast checked 44 minutes ago

Server URL

https://regulations-gov.1102tools.com/mcp

The last check completed an MCP handshake.

Registry name
com.1102tools/regulations-gov-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
648 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Regulations.gov readiness, rulemaking dockets, documents, comments, and comment periods. 9 tools.
Listing
From the official MCP registry (active).
Recent checks of Regulations.gov
CheckedResultHandshake
44 minutes agoHandshake completed648 ms
3 days agoHandshake completed442 ms
12 days agoHandshake completed498 ms
13 days agoHandshake completed379 ms
14 days agoHandshake completed405 ms
15 days agoHandshake completed307 ms
16 days agoHandshake completed357 ms
17 days agoHandshake completed382 ms
18 days agoHandshake completed384 ms
19 days agoHandshake completed455 ms
22 days agoHandshake completed422 ms
25 days agoHandshake completed387 ms
27 days agoHandshake completed534 ms

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

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