Remote MCP · Endpoint

Sidequest MCP server

No. Sidequest answered an MCP handshake 2 hours ago.

UpLast checked 2 hours ago

Server URL

https://saltcrate-sidequest.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
com.saltcrate/sidequest
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
2.99 s
Tools exposed
6 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
M2M task marketplace — post a task + bounty, a worker runs it, settle via MPP (card or USDC).
Listing
From the official MCP registry (active).
Recent checks of Sidequest
CheckedResultHandshake
2 hours agoHandshake completed2.99 s
13 hours agoHandshake completed71 ms
1 day agoHandshake completed60 ms
2 days agoHandshake completed148 ms
4 days agoHandshake completed86 ms
4 days agoHandshake completed2.96 s
5 days agoHandshake completed64 ms
7 days agoHandshake completed68 ms
9 days agoHandshake completed59 ms
11 days agoHandshake completed52 ms
14 days agoHandshake completed65 ms
16 days agoHandshake completed59 ms
18 days agoHandshake completed59 ms
20 days agoHandshake completed83 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 Sidequest and makes no claim about it beyond what these checks measured.