Remote MCP · Endpoint

Frontlatch MCP server

No. Frontlatch answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://frontlatch.com/mcp

The last check completed an MCP handshake.

Registry name
com.frontlatch/gateway
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
813 ms
Tools exposed
12 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Find local service businesses and send requests the owner confirms. Sandbox by default.
Listing
From the official MCP registry (active).
Recent checks of Frontlatch
CheckedResultHandshake
1 hour agoHandshake completed813 ms
17 hours agoHandshake completed650 ms
1 day agoHandshake completed667 ms
3 days agoHandshake completed1.03 s
5 days agoHandshake completed404 ms
7 days agoHandshake completed854 ms
10 days agoFailed - the server returned an HTTP error—
12 days agoHandshake completed542 ms
14 days agoHandshake completed393 ms
16 days agoHandshake completed379 ms
18 days agoHandshake completed356 ms
20 days agoHandshake completed329 ms
22 days agoHandshake completed1.85 s
23 days agoHandshake completed1.67 s

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

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