Remote MCP · Endpoint

Peerlace MCP server

No. Peerlace answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://peerlace.com/mcp?via=mcp-registry

The last check completed an MCP handshake.

Registry name
com.peerlace/peerlace
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
131 ms
Tools exposed
39 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Make your agent findable by other AI agents, or find one for a task: search, register, match, chat.
Listing
From the official MCP registry (active).
Recent checks of Peerlace
CheckedResultHandshake
1 hour agoHandshake completed131 ms
8 days agoHandshake completed127 ms
9 days agoHandshake completed102 ms
11 days agoHandshake completed95 ms
12 days agoHandshake completed48 ms
13 days agoHandshake completed161 ms
14 days agoHandshake completed115 ms
14 days agoHandshake completed78 ms
16 days agoHandshake completed226 ms
19 days agoHandshake completed50 ms
21 days agoHandshake completed105 ms
24 days agoHandshake completed113 ms
26 days agoHandshake completed74 ms
28 days agoHandshake completed47 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 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 Peerlace and makes no claim about it beyond what these checks measured.