Remote MCP · Endpoint

Loppee MCP server

No. Loppee answered an MCP handshake 5 hours ago.

UpLast checked 5 hours ago

Server URL

https://loppee.com/mcp/discovery

The last check completed an MCP handshake.

Registry name
com.loppee/loppee
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
135 ms
Tools exposed
5 tools
Uptime, last 30 days
100% from 17 checks
Described by its publisher as
Agent-first US business trust registry with neutral Trust Cards and published evidence.
Listing
From the official MCP registry (active).
Recent checks of Loppee
CheckedResultHandshake
5 hours agoHandshake completed135 ms
2 days agoHandshake completed156 ms
4 days agoHandshake completed249 ms
5 days agoHandshake completed159 ms
7 days agoHandshake completed145 ms
8 days agoHandshake completed154 ms
9 days agoHandshake completed141 ms
12 days agoHandshake completed170 ms
13 days agoHandshake completed128 ms
15 days agoHandshake completed151 ms
16 days agoHandshake completed130 ms
17 days agoHandshake completed136 ms
18 days agoHandshake completed145 ms
19 days agoHandshake completed128 ms
20 days agoHandshake completed140 ms
21 days agoHandshake completed4.38 s
22 days agoHandshake completed160 ms

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

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