Remote MCP · Endpoint

Peerlytics Data MCP server

No. Peerlytics Data answered an MCP handshake 23 minutes ago.

UpLast checked 23 minutes ago

Server URL

https://peerlytics.xyz/api/mcp/data

The last check completed an MCP handshake.

Registry name
xyz.peerlytics/peerlytics-data
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
3 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Peer protocol seller-rate and liquidity history on Base. Paid aggregate reads via x402 USDC.
Listing
From the official MCP registry (active).
Recent checks of Peerlytics Data
CheckedResultHandshake
23 minutes agoHandshake completed106 ms
9 days agoHandshake completed93 ms
10 days agoHandshake completed575 ms
11 days agoHandshake completed95 ms
12 days agoHandshake completed122 ms
14 days agoHandshake completed88 ms
14 days agoHandshake completed73 ms
15 days agoHandshake completed92 ms
17 days agoHandshake completed98 ms
19 days agoHandshake completed119 ms
21 days agoHandshake completed91 ms
24 days agoHandshake completed158 ms
26 days agoHandshake completed315 ms
28 days agoHandshake completed101 ms

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

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