Remote MCP · Endpoint

Beglaubigt MCP server

No. Beglaubigt answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://mcp.beglaubigt.de/mcp

The last check completed an MCP handshake.

Registry name
de.beglaubigt/incorporation
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
469 ms
Tools exposed
1 tool
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Incorporate a German GmbH or UG in chat, then finish and pay on a secure link.
Listing
From the official MCP registry (active).
Recent checks of Beglaubigt
CheckedResultHandshake
1 hour agoHandshake completed469 ms
2 days agoHandshake completed467 ms
4 days agoHandshake completed468 ms
5 days agoHandshake completed465 ms
7 days agoHandshake completed470 ms
8 days agoHandshake completed527 ms
9 days agoHandshake completed470 ms
12 days agoHandshake completed471 ms
13 days agoHandshake completed473 ms
15 days agoHandshake completed465 ms
16 days agoHandshake completed472 ms
18 days agoHandshake completed485 ms
19 days agoHandshake completed472 ms
20 days agoHandshake completed462 ms
20 days agoHandshake completed459 ms
21 days agoHandshake completed475 ms
22 days agoHandshake completed460 ms

The last 17 checks. Full history is kept for 30 days; the all-time counter stands at 17 responding of 17.

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 Beglaubigt and makes no claim about it beyond what these checks measured.