Remote MCP · Endpoint

RPV Calculator MCP server

No. RPV Calculator answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://www.rpv-calculator.be/mcp

The last check completed an MCP handshake.

Registry name
io.github.pieterjanscheir/rpv-calculator
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
279 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Belgian procedural indemnity (rechtsplegingsvergoeding) amounts, indexed to the CPI for any date.
Listing
From the official MCP registry (active).
Recent checks of RPV Calculator
CheckedResultHandshake
1 hour agoHandshake completed279 ms
7 hours agoHandshake completed584 ms
2 days agoHandshake completed320 ms
4 days agoHandshake completed223 ms
6 days agoHandshake completed233 ms
9 days agoHandshake completed305 ms
11 days agoHandshake completed238 ms
13 days agoHandshake completed197 ms
15 days agoHandshake completed259 ms
17 days agoHandshake completed181 ms
19 days agoHandshake completed201 ms
21 days agoHandshake completed245 ms
23 days agoHandshake completed236 ms
24 days agoHandshake completed235 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 RPV Calculator and makes no claim about it beyond what these checks measured.