Remote MCP · Endpoint

Basedworld Agent HQ MCP server

Yes, as of 5 hours ago: the request timed out.

DownLast checked 5 hours ago

Server URL

https://basedworld.fly.dev/mcp

The last check failed: the request timed out.

Registry name
dev.fly.basedworld/market
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
9 tools
Uptime, last 30 days
42.9% from 14 checks
Described by its publisher as
Find public creator tools, work and conversation. Read-only; no wallet, posting or payment.
Listing
From the official MCP registry (active).
Recent checks of Basedworld Agent HQ
CheckedResultHandshake
5 hours agoFailed - the request timed out—
9 days agoFailed - the request timed out—
10 days agoFailed - the request timed out—
11 days agoFailed - the request timed out—
12 days agoFailed - the request timed out—
14 days agoFailed - the request timed out—
14 days agoFailed - the request timed out—
15 days agoFailed - the request timed out—
17 days agoHandshake completed48 ms
19 days agoHandshake completed64 ms
21 days agoHandshake completed41 ms
24 days agoHandshake completed41 ms
26 days agoHandshake completed49 ms
28 days agoHandshake completed41 ms

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

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