Remote MCP · Endpoint

Fairplug (sandbox) MCP server

No. Fairplug (sandbox) answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://fairplug-mcp.fairplughq.workers.dev/sandbox/mcp

The last check completed an MCP handshake.

Registry name
io.github.FairPlugHQ/fairplug-mcp
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
299 ms
Tools exposed
2 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Disclosure-first sponsored offers for AI assistants. Free read-only sandbox, fictional data.
Listing
From the official MCP registry (active).
Recent checks of Fairplug (sandbox)
CheckedResultHandshake
43 minutes agoHandshake completed299 ms
8 days agoHandshake completed525 ms
9 days agoHandshake completed399 ms
11 days agoHandshake completed527 ms
12 days agoHandshake completed391 ms
13 days agoHandshake completed325 ms
14 days agoHandshake completed227 ms
14 days agoHandshake completed442 ms
16 days agoHandshake completed304 ms
19 days agoHandshake completed336 ms
21 days agoHandshake completed381 ms
24 days agoHandshake completed210 ms
26 days agoHandshake completed347 ms
28 days agoHandshake completed411 ms

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

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