Remote MCP · Endpoint

Vextorium MCP server

Yes, as of 6 hours ago: the server returned an HTTP error.

DownLast checked 6 hours ago

Server URL

https://api.vextorium.com/mcp

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

Registry name
com.vextorium.api/vextorium
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
3 tools
Uptime, last 30 days
84.6% from 13 checks
Described by its publisher as
244 pay-per-call AI APIs: crypto, DeFi, markets, official data, compliance and developer tools.
Listing
From the official MCP registry (active).
Recent checks of Vextorium
CheckedResultHandshake
6 hours agoFailed - the server returned an HTTP error—
2 days agoHandshake completed949 ms
5 days agoHandshake completed394 ms
7 days agoHandshake completed440 ms
9 days agoHandshake completed393 ms
11 days agoFailed - the server returned an HTTP error—
13 days agoHandshake completed378 ms
15 days agoHandshake completed407 ms
17 days agoHandshake completed406 ms
18 days agoHandshake completed395 ms
20 days agoHandshake completed314 ms
21 days agoHandshake completed362 ms
23 days agoHandshake completed375 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 Vextorium and makes no claim about it beyond what these checks measured.