Remote MCP · Endpoint

VaultRubric MCP server

Yes, as of 2 hours ago: the hostname does not resolve.

DownLast checked 2 hours ago

Server URL

https://vaultrubric.com/mcp

The last check failed: the hostname does not resolve.

Registry name
com.vaultrubric/vaultrubric
Transport
Streamable HTTP
Protocol negotiated
Not measured yet
Handshake latency
—
Tools exposed
11 tools
Uptime, last 30 days
93.3% from 15 checks
Described by its publisher as
Sourced, scored comparisons of crypto exchanges, wallets, savings accounts and brokerages.
Listing
From the official MCP registry (active).
Recent checks of VaultRubric
CheckedResultHandshake
2 hours agoFailed - the hostname does not resolve—
1 day agoHandshake completed177 ms
2 days agoHandshake completed129 ms
3 days agoHandshake completed165 ms
4 days agoHandshake completed283 ms
5 days agoHandshake completed148 ms
6 days agoHandshake completed361 ms
9 days agoHandshake completed252 ms
11 days agoHandshake completed266 ms
14 days agoHandshake completed246 ms
16 days agoHandshake completed303 ms
18 days agoHandshake completed274 ms
20 days agoHandshake completed286 ms
22 days agoHandshake completed264 ms
24 days agoHandshake completed150 ms

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

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