Remote MCP · Endpoint

FrankKi MCP server

No. FrankKi answered an MCP handshake 11 hours ago.

UpLast checked 11 hours ago

Server URL

https://mcp.frankki.app/

The last check completed an MCP handshake.

Registry name
app.frankki/letters
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
288 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
The agentic layer of letters. Agents send real printed mail worldwide, German compliance built in.
Listing
From the official MCP registry (active).
Recent checks of FrankKi
CheckedResultHandshake
11 hours agoHandshake completed288 ms
2 days agoHandshake completed290 ms
4 days agoHandshake completed315 ms
6 days agoHandshake completed286 ms
7 days agoHandshake completed292 ms
8 days agoHandshake completed354 ms
9 days agoHandshake completed291 ms
12 days agoHandshake completed286 ms
14 days agoHandshake completed304 ms
15 days agoHandshake completed325 ms
16 days agoHandshake completed333 ms
18 days agoHandshake completed301 ms
19 days agoHandshake completed306 ms
19 days agoHandshake completed337 ms
20 days agoHandshake completed304 ms
21 days agoHandshake completed294 ms
23 days agoHandshake completed294 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 FrankKi and makes no claim about it beyond what these checks measured.