Remote MCP · Endpoint

Peer MCP server

No. Peer answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://mcp.peer.xyz/mcp

The last check completed an MCP handshake.

Registry name
io.github.zkp2p/peer
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
59 ms
Tools exposed
97 tools
Uptime, last 30 days
100% from 18 checks
Described by its publisher as
Read Peer protocol, market, checkout, and Peer Cash data through one MCP server.
Listing
From the official MCP registry (active).
Recent checks of Peer
CheckedResultHandshake
2 hours agoHandshake completed59 ms
1 day agoHandshake completed54 ms
3 days agoHandshake completed57 ms
3 days agoHandshake completed52 ms
4 days agoHandshake completed62 ms
5 days agoHandshake completed93 ms
7 days agoHandshake completed180 ms
10 days agoHandshake completed86 ms
12 days agoHandshake completed61 ms
15 days agoHandshake completed62 ms
17 days agoHandshake completed69 ms
19 days agoHandshake completed58 ms
21 days agoHandshake completed77 ms
23 days agoHandshake completed152 ms
25 days agoHandshake completed113 ms
26 days agoHandshake completed57 ms
28 days agoHandshake completed57 ms
29 days agoHandshake completed43 ms

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

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