Remote MCP · Endpoint

NebenkostenPro MCP server

No. NebenkostenPro answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://nebenkostenpro.de/mcp

The last check completed an MCP handshake.

Registry name
de.nebenkostenpro/nebenkosten
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
433 ms
Tools exposed
9 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
German housing costs: utility costs of 400 cities, property tax rates, housing benefit, deadlines.
Listing
From the official MCP registry (active).
Recent checks of NebenkostenPro
CheckedResultHandshake
1 hour agoHandshake completed433 ms
2 days agoHandshake completed211 ms
4 days agoHandshake completed347 ms
6 days agoHandshake completed330 ms
8 days agoHandshake completed384 ms
10 days agoHandshake completed358 ms
13 days agoHandshake completed350 ms
14 days agoHandshake completed353 ms
16 days agoHandshake completed415 ms
17 days agoHandshake completed338 ms
18 days agoHandshake completed325 ms
21 days agoHandshake completed329 ms
22 days agoHandshake completed328 ms
24 days agoHandshake completed368 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 NebenkostenPro and makes no claim about it beyond what these checks measured.