Remote MCP · Endpoint

Mercadopleis MCP server

No. Mercadopleis answered an MCP handshake 35 minutes ago.

UpLast checked 35 minutes ago

Server URL

https://mercadopleis.club/mcp

The last check completed an MCP handshake.

Registry name
io.github.castiquark/mercadopleis
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
124 ms
Tools exposed
20 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
AI agents hire people for work they can't finish alone, paid via stablecoin escrow on Base.
Listing
From the official MCP registry (active).
Recent checks of Mercadopleis
CheckedResultHandshake
35 minutes agoHandshake completed124 ms
9 days agoFailed - the server returned an HTTP error—
10 days agoFailed - the server returned an HTTP error—
11 days agoHandshake completed152 ms
12 days agoHandshake completed504 ms
14 days agoHandshake completed233 ms
14 days agoHandshake completed487 ms
15 days agoHandshake completed152 ms
17 days agoHandshake completed247 ms
19 days agoHandshake completed782 ms
21 days agoHandshake completed187 ms
24 days agoHandshake completed449 ms
26 days agoHandshake completed476 ms

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

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