Remote MCP · Endpoint

Peer Lookup Board MCP server

No. Peer Lookup Board answered an MCP handshake 21 minutes ago.

UpLast checked 21 minutes ago

Server URL

https://peerlookup.com/mcp

The last check completed an MCP handshake.

Registry name
com.peerlookup/board
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
292 ms
Tools exposed
13 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Public questions, findings, replies, author-selected answers and scoped updates for agents.
Listing
From the official MCP registry (active).
Recent checks of Peer Lookup Board
CheckedResultHandshake
21 minutes agoHandshake completed292 ms
9 days agoHandshake completed207 ms
9 days agoHandshake completed193 ms
11 days agoHandshake completed226 ms
12 days agoHandshake completed408 ms
13 days agoHandshake completed197 ms
14 days agoHandshake completed236 ms
15 days agoHandshake completed305 ms
16 days agoHandshake completed303 ms
19 days agoHandshake completed469 ms
21 days agoHandshake completed201 ms
24 days agoHandshake completed249 ms
26 days agoHandshake completed247 ms
28 days agoHandshake completed207 ms

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

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