Remote MCP · Endpoint

Peerlytics MCP server

No. Peerlytics answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://peerlytics.xyz/api/mcp

The last check completed an MCP handshake.

Registry name
xyz.peerlytics/peerlytics
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
97 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public Peer protocol activity and settlement receipts on Base. Read-only; no key or wallet.
Listing
From the official MCP registry (active).
Recent checks of Peerlytics
CheckedResultHandshake
2 hours agoHandshake completed97 ms
16 hours agoHandshake completed97 ms
1 day agoHandshake completed101 ms
2 days agoHandshake completed112 ms
4 days agoHandshake completed95 ms
7 days agoHandshake completed112 ms
9 days agoHandshake completed109 ms
12 days agoHandshake completed120 ms
14 days agoHandshake completed93 ms
16 days agoHandshake completed86 ms
18 days agoHandshake completed95 ms
20 days agoHandshake completed92 ms
22 days agoHandshake completed310 ms
23 days agoHandshake completed108 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 Peerlytics and makes no claim about it beyond what these checks measured.