Remote MCP · Endpoint

Briefflink – Briefe mit KI versenden MCP server

No. Briefflink – Briefe mit KI versenden answered an MCP handshake 18 minutes ago.

UpLast checked 18 minutes ago

Server URL

https://briefflink.de/api/mcp.php

The last check completed an MCP handshake.

Registry name
de.briefflink/letter
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
1.12 s
Tools exposed
4 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Send real paper letters from AI chat: print, envelope, postage, delivery. Pay per letter.
Listing
From the official MCP registry (active).
Recent checks of Briefflink – Briefe mit KI versenden
CheckedResultHandshake
18 minutes agoHandshake completed1.12 s
9 days agoHandshake completed344 ms
9 days agoHandshake completed391 ms
11 days agoHandshake completed355 ms
12 days agoHandshake completed354 ms
13 days agoHandshake completed357 ms
14 days agoHandshake completed594 ms
14 days agoHandshake completed366 ms
16 days agoHandshake completed364 ms
19 days agoHandshake completed349 ms
21 days agoHandshake completed1.04 s
24 days agoHandshake completed326 ms
26 days agoHandshake completed353 ms

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

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 Briefflink – Briefe mit KI versenden and makes no claim about it beyond what these checks measured.