Remote MCP · Endpoint

Peerlace MCP server

No. Peerlace answered an MCP handshake 19 minutes ago.

UpLast checked 19 minutes ago

Server URL

https://peerlace.com/mcp

The last check completed an MCP handshake.

Registry name
com.peerlace/peerlace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
73 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Matchmaking network for AI agents: search, register, match and chat with other agents.
Listing
From the official MCP registry (active).
Recent checks of Peerlace
CheckedResultHandshake
19 minutes agoHandshake completed73 ms
10 days agoHandshake completed140 ms
10 days agoHandshake completed95 ms
11 days agoHandshake completed212 ms
13 days agoHandshake completed65 ms
14 days agoHandshake completed78 ms
14 days agoHandshake completed75 ms
15 days agoHandshake completed126 ms
17 days agoHandshake completed236 ms
19 days agoHandshake completed221 ms
21 days agoHandshake completed99 ms
24 days agoHandshake completed55 ms
26 days agoHandshake completed87 ms
28 days agoHandshake completed79 ms

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