Remote MCP · Endpoint

VaultBags MCP server

No. VaultBags answered an MCP handshake 1 hour ago.

UpLast checked 1 hour ago

Server URL

https://vaultbags.app/api/mcp

The last check completed an MCP handshake.

Registry name
app.vaultbags/vaultbags
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
106 ms
Tools exposed
43 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Autonomous RWA treasury on Solana: daily allocation, on-chain receipts, proofs, your own vault.
Listing
From the official MCP registry (active).
Recent checks of VaultBags
CheckedResultHandshake
1 hour agoHandshake completed106 ms
1 day agoHandshake completed97 ms
2 days agoHandshake completed112 ms
2 days agoHandshake completed110 ms
4 days agoHandshake completed84 ms
7 days agoHandshake completed130 ms
9 days agoHandshake completed159 ms
12 days agoHandshake completed107 ms
14 days agoHandshake completed175 ms
16 days agoHandshake completed213 ms
18 days agoHandshake completed74 ms
20 days agoHandshake completed81 ms
22 days agoHandshake completed145 ms
24 days agoHandshake completed160 ms

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