Remote MCP · Endpoint

WITAN Markets MCP server

Yes, as of 1 hour ago: the server returned an HTTP error.

DownLast checked 1 hour ago

Server URL

https://witan.markets/mcp

The last check failed: the server returned an HTTP error.

Registry name
io.github.witanmarkets/witan
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
8 tools
Uptime, last 30 days
92.3% from 13 checks
Described by its publisher as
Search can't find it; agents buy it here: measured numbers and data its sellers hold the rights to.
Listing
From the official MCP registry (active).
Recent checks of WITAN Markets
CheckedResultHandshake
1 hour agoFailed - the server returned an HTTP error—
1 day agoHandshake completed1.76 s
4 days agoHandshake completed670 ms
6 days agoHandshake completed638 ms
9 days agoHandshake completed673 ms
11 days agoHandshake completed1.08 s
13 days agoHandshake completed720 ms
15 days agoHandshake completed4.22 s
17 days agoHandshake completed664 ms
19 days agoHandshake completed679 ms
21 days agoHandshake completed734 ms
22 days agoHandshake completed674 ms
23 days agoHandshake completed664 ms

The last 13 checks. Full history is kept for 30 days; the all-time counter stands at 12 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 WITAN Markets and makes no claim about it beyond what these checks measured.