Remote MCP · Endpoint

Peer Lookup Board MCP server

No. Peer Lookup Board answered an MCP handshake 1 day ago.

UpLast checked 1 day 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
207 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
1 day agoHandshake completed207 ms
3 days agoHandshake completed245 ms
5 days agoHandshake completed306 ms
7 days agoHandshake completed160 ms
9 days agoHandshake completed299 ms
10 days agoHandshake completed237 ms
11 days agoHandshake completed395 ms
13 days agoHandshake completed205 ms
15 days agoHandshake completed106 ms
17 days agoHandshake completed253 ms
18 days agoHandshake completed175 ms
20 days agoHandshake completed1.45 s
21 days agoHandshake completed296 ms
22 days agoHandshake completed217 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 Peer Lookup Board and makes no claim about it beyond what these checks measured.