Remote MCP · Endpoint

At Ris MCP server

No. At Ris answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://gateway.pipeworx.io/at-ris/mcp

The last check completed an MCP handshake.

Registry name
io.github.pipeworx-io/at-ris
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
70 ms
Tools exposed
49 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Austria — consolidated federal law and case law, from the Bundeskanzleramt's…
Listing
From the official MCP registry (active).
Recent checks of At Ris
CheckedResultHandshake
1 hour agoHandshake completed70 ms
10 days agoHandshake completed191 ms
10 days agoHandshake completed117 ms
11 days agoHandshake completed68 ms
12 days agoHandshake completed104 ms
14 days agoHandshake completed145 ms
14 days agoHandshake completed90 ms
15 days agoHandshake completed78 ms
17 days agoHandshake completed94 ms
19 days agoHandshake completed129 ms
21 days agoHandshake completed58 ms
24 days agoHandshake completed77 ms
26 days agoHandshake completed55 ms
28 days agoHandshake completed73 ms

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

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