Is the Vaultbags MCP server down?

mcp-registry/app.vaultbags/vaultbags · v1.0.0

As of 2026-10-26 02:57 UTC, the Vaultbags MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

Autonomous RWA treasury on Solana: daily allocation, on-chain receipts, proofs, your own vault.

claude mcp add --transport http vaultbags-mcp-server https://vaultbags.app/api/mcp

{
  "mcpServers": {
    "vaultbags-mcp-server": {
      "type": "http",
      "url": "https://vaultbags.app/api/mcp"
    }
  }
}

Third-party server, listed as discovered. Review its source before installing.

Agent-readiness: B (85/100)

What to fix (2)

Auto-fix: 31 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. All of them as JSON: /v1/readiness/mcp-registry%2Fapp.vaultbags%2Fvaultbags/fixes

{
  "name": "get_agent",
  "description": "Evaluate ANY token running on VaultBags as an autonomous agent, by SPL token mint: its Autonomy Score, its passport (identity, surfaces, on-chain receipts) and its treasury. The score is split into `protocolScore` (guarantees every VaultBags agent inherits: a brain that decides daily, decisions stamped on-chain, the firewall) and `projectScore` (what THAT token earned on its own: distribution cycles that paid its holders, and the length of its own public record). A freshly launched token has a s",
  "inputSchema": {
    "type": "object",
    "required": [
      "mint"
    ],
    "properties": {
      "mint": {
        "type": "string",
        "description": "The agent's SPL token mint address (base58)."
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_agent_passport",
  "description": "The vault agent's portable machine-readable passport: identity, capabilities, machine surfaces (MCP/REST/OpenAPI), Autonomy Score, and pointers to its on-chain decision receipts. Shaped so another agent can evaluate this one programmatically.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

{
  "name": "get_autonomy",
  "description": "The vault agent's Autonomy Score and the verifiable facts behind it: daily frozen decisions, on-chain receipts, distribution cycles, value paid to holders, firewall status and earned-income coverage. Read-only public data; a low sub-score means a young track record, not a failure.",
  "inputSchema": {
    "type": "object",
    "properties": {},
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/app.vaultbags/vaultbags"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/app.vaultbags/vaultbags"}) over MCP.

Passed

• Every tool has a well-formed, typed input schema.
• Every tool and parameter is described.
• No tool-poisoning patterns (hidden characters, instruction overrides, concealment, secret access, tool shadowing).
• Compact tool list (~6,711 tokens).
• Tool names are unique and portable across clients.
• Speaks MCP 2025-06-18.
• 100.00% uptime over 30 days.
• No breaking contract changes in 30 days.

Largest tool definitions

• simulate_allocation ~391 tokens
• prepare_token_launch ~323 tokens
• get_lock_tier ~236 tokens
• get_treasury_history ~232 tokens
• list_rwas ~211 tokens

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live. Embed the readiness badge:

[![MCP agent-readiness](https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vaultbags%2Fvaultbags.svg)](https://glimind.com/server/mcp-registry%2Fapp.vaultbags%2Fvaultbags?ref=badge)

<a href="https://glimind.com/server/mcp-registry%2Fapp.vaultbags%2Fvaultbags?ref=badge"><img src="https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vaultbags%2Fvaultbags.svg" alt="MCP agent-readiness"></a>

.. image:: https://glimind.com/v1/readiness/badge/mcp-registry%2Fapp.vaultbags%2Fvaultbags.svg
   :target: https://glimind.com/server/mcp-registry%2Fapp.vaultbags%2Fvaultbags?ref=badge
   :alt: MCP agent-readiness

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:748d1b7230bb0484…, first seen 2026-10-17, included at leaf 6283 of 70,290. Version history · verify what your client received.

Tools (40)

• get_agent
• get_agent_passport
• get_autonomy
• get_autonomy_spec
• get_brain_vs_flat
• get_daily_briefing
• get_decision_history
• get_holder_distribution
• get_liquidity
• get_lock_tier
• get_market_signals
• get_monthly_reports
• get_my_claims
• get_my_performance
• get_my_vault
• get_payout_integrity
• get_project_treasury
• get_projects
• get_proof_of_reserves
• get_protocol_meter
• get_raffle
• get_recent_activity
• get_recent_cycles
• get_rwa
• get_rwa_performance
• get_shadow_vs_brain
• get_strategies
• get_strategy
• get_supply
• get_todays_allocation
• get_treasury_history
• get_treasury_stats
• get_vault_docs
• list_rwas
• prepare_token_launch
• simulate_allocation
• simulate_lock_boost
• verify_claim
• verify_day
• verify_decision

Compare: most reliable ml servers · most reliable data servers · most reliable knowledge servers · most reliable finance servers · most reliable other servers

claude mcp add --transport http glimind https://glimind.com/mcp

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp"
    }
  }
}

FAQ

Is the Vaultbags MCP server down right now?

As of 2026-10-26 02:57 UTC, the Vaultbags MCP server is up with a Glimind reliability score of 100/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Vaultbags MCP server provide?

Vaultbags MCP server advertises 40 tools, including get_agent, get_agent_passport, get_autonomy, get_autonomy_spec, get_brain_vs_flat.

How do I install Vaultbags MCP server?

Point your MCP client at this streamable-http endpoint: https://vaultbags.app/api/mcp

Is the Vaultbags MCP server safe to connect to an AI agent?

Glimind scanned all 40 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Vaultbags MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.