Remote MCP · Endpoint

Jan Linketscher MCP server

No. Jan Linketscher answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://janlinketscher.com/api/mcp

The last check completed an MCP handshake.

Registry name
com.janlinketscher/site
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
74 ms
Tools exposed
7 tools
Uptime, last 30 days
100% from 15 checks
Described by its publisher as
Profile and essays of Jan Linketscher (i22, Bonn), full-text search, and booking a call.
Listing
From the official MCP registry (active).
Recent checks of Jan Linketscher
CheckedResultHandshake
2 hours agoHandshake completed74 ms
1 day agoHandshake completed81 ms
2 days agoHandshake completed71 ms
3 days agoHandshake completed130 ms
3 days agoHandshake completed70 ms
5 days agoHandshake completed110 ms
7 days agoHandshake completed105 ms
10 days agoHandshake completed92 ms
12 days agoHandshake completed127 ms
14 days agoHandshake completed167 ms
17 days agoHandshake completed65 ms
19 days agoHandshake completed96 ms
21 days agoHandshake completed111 ms
23 days agoHandshake completed71 ms
24 days agoHandshake completed149 ms

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

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