Remote MCP · Endpoint

Pflegegradpunkte MCP server

No. Pflegegradpunkte answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://pflegegradpunkte.de/mcp?src=mcp

The last check completed an MCP handshake.

Registry name
de.pflegegradpunkte/pflegegradpunkte
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
473 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Pflegegrad-Punkte nach SGB XI berechnen: Begutachtungsfragen, Punkte je Bereich, belegte Fakten.
Listing
From the official MCP registry (active).
Recent checks of Pflegegradpunkte
CheckedResultHandshake
1 hour agoHandshake completed473 ms
1 day agoHandshake completed425 ms
2 days agoHandshake completed437 ms
2 days agoHandshake completed416 ms
4 days agoHandshake completed345 ms
6 days agoHandshake completed410 ms
9 days agoHandshake completed424 ms
11 days agoHandshake completed435 ms
14 days agoHandshake completed322 ms
16 days agoHandshake completed417 ms
18 days agoHandshake completed342 ms
20 days agoHandshake completed425 ms
22 days agoHandshake completed339 ms
23 days agoHandshake completed336 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 Pflegegradpunkte and makes no claim about it beyond what these checks measured.