Remote MCP · Endpoint

RSolution.cz MCP server

No. RSolution.cz answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://rsolution.cz/mcp

The last check completed an MCP handshake.

Registry name
cz.rsolution/verejny
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
937 ms
Tools exposed
4 tools
Uptime, last 30 days
93.8% from 16 checks
Described by its publisher as
Služby, ceník a dostupnost českého vývojáře interních systémů; napis_mi pošle poptávku.
Listing
From the official MCP registry (active).
Recent checks of RSolution.cz
CheckedResultHandshake
1 hour agoHandshake completed937 ms
6 hours agoHandshake completed540 ms
2 days agoHandshake completed604 ms
4 days agoHandshake completed869 ms
7 days agoHandshake completed1.09 s
9 days agoHandshake completed899 ms
11 days agoHandshake completed919 ms
13 days agoHandshake completed558 ms
15 days agoHandshake completed618 ms
17 days agoFailed - the connection was refused or dropped—
19 days agoHandshake completed708 ms
21 days agoHandshake completed572 ms
23 days agoHandshake completed892 ms
24 days agoHandshake completed562 ms
25 days agoHandshake completed576 ms
27 days agoHandshake completed942 ms

The last 16 checks. Full history is kept for 30 days; the all-time counter stands at 15 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 RSolution.cz and makes no claim about it beyond what these checks measured.