Remote MCP · Endpoint

janbrennenstuhl.eu MCP server

No. janbrennenstuhl.eu answered an MCP handshake 1 day ago.

UpLast checked 1 day ago

Server URL

https://mcp.janbrennenstuhl.eu/mcp

The last check completed an MCP handshake.

Registry name
eu.janbrennenstuhl/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
37 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 11 checks
Described by its publisher as
Search, read and cite Jan Brennenstuhl's essays on AppSec, identity and agent identity.
Listing
From the official MCP registry (active).
Recent checks of janbrennenstuhl.eu
CheckedResultHandshake
1 day agoHandshake completed37 ms
5 days agoHandshake completed37 ms
16 days agoHandshake completed139 ms
17 days agoHandshake completed35 ms
17 days agoHandshake completed42 ms
19 days agoHandshake completed49 ms
20 days agoHandshake completed47 ms
21 days agoHandshake completed110 ms
22 days agoHandshake completed38 ms
23 days agoHandshake completed74 ms
25 days agoHandshake completed37 ms

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

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