Remote MCP · Endpoint

RegAffairs AI MCP server

No. RegAffairs AI answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.regaffairsai.com/mcp

The last check completed an MCP handshake.

Registry name
com.regaffairsai/regaffairs
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
939 ms
Tools exposed
15 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Cited answers on chemical, food, pharma, device, cosmetic and pesticide rules, linked to sources.
Listing
From the official MCP registry (active).
Recent checks of RegAffairs AI
CheckedResultHandshake
2 hours agoHandshake completed939 ms
1 day agoHandshake completed875 ms
2 days agoHandshake completed937 ms
2 days agoHandshake completed865 ms
4 days agoHandshake completed883 ms
7 days agoHandshake completed863 ms
9 days agoHandshake completed882 ms
12 days agoHandshake completed801 ms
14 days agoHandshake completed435 ms
16 days agoHandshake completed367 ms
18 days agoCredentials required—
20 days agoCredentials required—
22 days agoCredentials required—
24 days agoCredentials required—

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

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