Remote MCP · Endpoint

eBilanz Fabrik MCP server

No. eBilanz Fabrik answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://app.ebilanzfabrik.de/mcp

The last check completed an MCP handshake.

Registry name
de.ebilanzfabrik/ebilanz-fabrik
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
289 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
E-Bilanz and Offenlegung for small German GmbH/UG: products, prices, eligibility.
Listing
From the official MCP registry (active).
Recent checks of eBilanz Fabrik
CheckedResultHandshake
1 hour agoHandshake completed289 ms
8 days agoHandshake completed362 ms
9 days agoHandshake completed295 ms
11 days agoHandshake completed292 ms
12 days agoHandshake completed295 ms
13 days agoHandshake completed293 ms
14 days agoHandshake completed299 ms
14 days agoHandshake completed295 ms
16 days agoHandshake completed838 ms
19 days agoHandshake completed312 ms
21 days agoHandshake completed294 ms
24 days agoHandshake completed289 ms
26 days agoHandshake completed287 ms
28 days agoHandshake completed325 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 eBilanz Fabrik and makes no claim about it beyond what these checks measured.