Remote MCP · Endpoint

Bot Bazaar MCP server

No. Bot Bazaar answered an MCP handshake 9 hours ago.

UpLast checked 9 hours ago

Server URL

https://bot-bazaar.fly.dev/mcp

The last check completed an MCP handshake.

Registry name
dev.fly.bot-bazaar/bot-bazaar
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
799 ms
Tools exposed
60 tools
Uptime, last 30 days
100% from 13 checks
Described by its publisher as
Pay-per-call x402 audit suites (USDC on Base) and agent marketplace tools. Free sample reports.
Listing
From the official MCP registry (active).
Recent checks of Bot Bazaar
CheckedResultHandshake
9 hours agoHandshake completed799 ms
4 days agoHandshake completed181 ms
14 days agoHandshake completed122 ms
15 days agoHandshake completed228 ms
15 days agoHandshake completed97 ms
17 days agoHandshake completed114 ms
18 days agoHandshake completed116 ms
19 days agoHandshake completed183 ms
20 days agoHandshake completed182 ms
21 days agoHandshake completed155 ms
23 days agoHandshake completed105 ms
26 days agoHandshake completed209 ms
28 days agoHandshake completed98 ms

The last 13 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 Bot Bazaar and makes no claim about it beyond what these checks measured.