Remote MCP · Endpoint

Riksflödet MCP server

No. Riksflödet answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://riksflodet.se/mcp

The last check completed an MCP handshake.

Registry name
se.riksflodet/riksflodet
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.45 s
Tools exposed
8 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Sveriges riksdag: vem sa vad, hur röstade ledamöter och partier — med källänkar.
Listing
From the official MCP registry (active).
Recent checks of Riksflödet
CheckedResultHandshake
1 hour agoHandshake completed1.45 s
2 days agoHandshake completed163 ms
4 days agoHandshake completed181 ms
6 days agoHandshake completed144 ms
8 days agoHandshake completed152 ms
10 days agoHandshake completed132 ms
12 days agoHandshake completed154 ms
14 days agoHandshake completed142 ms
15 days agoHandshake completed146 ms
16 days agoHandshake completed299 ms
17 days agoHandshake completed191 ms
20 days agoHandshake completed146 ms
22 days agoHandshake completed146 ms
23 days agoHandshake completed370 ms

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