Skip to content

MCP servers › app.vaultbags › vaultbags

MCP server · registry snapshot 2026-10-23 · last tested 2026-10-23

app.vaultbags/vaultbags

Autonomous RWA treasury on Solana: daily allocation, on-chain receipts, proofs, your own vault. — the publisher's description

1 of 2 record checks metRead-only · tools listed 2026-10-23Topic: finance-and-payments · AI-classifiedversion 1.0.0streamable HTTP40 tools

Summary

app.vaultbags/vaultbags is a remote MCP server listed in the official MCP registry at version 1.0.0. On 2026-10-23 ProtocolProbe connected to it in read-only mode and read its inventory: 40 tools, 6 resources and 6 prompts.

Record checks

1 of 2 record checks met · 7 do not apply

  • met: Registry entry is active and says how to run it
  • not met: Source repository link opens
  • not applicable: Repository is not archived
  • not applicable: Code pushed to the repository in the 90 days before our check
  • not applicable: Repository publishes a security policy (SECURITY.md)
  • not applicable: Package names its licence with a standard (SPDX) identifier
  • not applicable: The version the registry lists can be installed and is not withdrawn
  • not applicable: npm package carries build provenance (attestation)
  • not applicable: No known critical or high advisory in the package or its dependencies
  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository

From public records, not a safety rating. Each check with its reason · Is it safe to install?

Key facts

Runs
remote (hosted by the publisher)
Transport
streamable HTTP
Sign-in
none needed to open a session
Tools
40
Described as changing data
1 of 40 toolsAI-classified
Topic
finance-and-paymentsAI-classified
Last tested
2026-10-23

Add to your client

Worth knowing before you connect it

  • 1 tool is described as changing something (prepare_token_launch): our AI model's reading of the descriptions, not something we tested, and the server opened a session without any credential. We did not call it.

Each line comes from a section below, with its source and date.

How fresh this is

Live-tested
yes, a real session (not a text-only review)
Last tested
2026-10-23
Mode
read-only (no tool calls)
Latest version
1.0.0, published 2026-10-10 (registry, as of the 2026-10-23 snapshot)
First listed version
2026-10-10 (earliest version still in the registry; older removed versions would be earlier)
Registry data
snapshot 2026-10-23
Package and repository
checked 2026-10-22
Engine
mcp-runtime-engine@0.1.0 · sdk@1.32.0

Changes since the last refresh

New in the registry: not in the list of 2026-10-04, listed on 2026-10-23 with version 1.0.0 (published 2026-10-10).

Source: the official MCP Registry list on 2026-10-04 and on 2026-10-23.

What it is

What does this server offer?

Observed inventory
40tools
6resources
6prompts

1 of 40 tools are described as changing something (creating, editing, deleting, sending or running).

  • get_todays_allocationreads or searches

    “Today's RWA buy proportions (gold / S&P 500 / US treasuries), the 23-43% band, whether the decision is frozen for the day, the plain-English rationale, and the on-chain receipt transaction if already…”

    Takes no inputs.

  • get_daily_briefingon 5 other serversreads or searches

    “Today's public Daily Vault Briefing: a short market note explaining why the vault is buying in today's proportions, plus the weights and the on-chain receipt transaction.”

    Takes no inputs.

  • get_treasury_statsreads or searches

    “Live treasury statistics: per-asset balances and USD values (gold, S&P 500, US treasuries), total vault value, total paid to holders and fees processed.”

    Takes no inputs.

  • get_decision_historyreads or searches

    “Recent daily allocation decisions, newest first: date, weights, rationale and the on-chain receipt transaction of each day that was stamped.”

    1 input
    • daysinteger“How many recent days to return (default 14, max 30).”
  • get_market_signalson 2 other serversreads or searches

    “The quantitative market signals behind today's allocation: real yields, breakeven inflation, the dollar trend, gold momentum, credit spreads, volatility (VIX), S&P momentum, the 10Y yield, the 10Y-2Y…”

    Takes no inputs.

  • get_brain_vs_flatreads or searches

    “The honest track record: did following the vault's daily Smart Allocation line beat a fixed even 33/33/33 split?”

    Takes no inputs.

  • simulate_allocationcalculates or converts

    “Run the vault's allocation model on YOUR market inputs and get back the buy proportions it would choose (gold / S&P 500 / US treasuries), the per-asset convictions, and a plain-English rationale, alw…”

    10 inputs
    • realYieldnumber“10-year real (TIPS) yield, percent (e.g.”
    • breakevenInflnumber“10-year breakeven inflation, percent.”
    • dxyChangePctnumber“Broad US dollar index percent change over ~1 month.”
    • goldMomentumPctnumber“Gold price percent change (recent trend).”
    • hyOasnumber“US High Yield credit spread (OAS), percent.”
    • vixnumber“CBOE volatility index (VIX) level.”
    • spx30dPctnumber“S&P 500 percent change over ~1 month.”
    • tenYearnumber“10-year Treasury nominal yield, percent.”
    • curve10y2ynumber“10-year minus 2-year Treasury spread, percent.”
    • fearGreednumber“Crypto Fear & Greed index, 0 to 100.”
  • prepare_token_launchon 1 other servergenerates contentdescribed as changing data

    “Draft a Bags token launch with VaultBags preconfigured, for a person to finish and sign.”

    5 inputs, 3 required
    • namestringrequired“Token name, 1 to 32 characters.”
    • symbolstringrequired“Ticker, 1 to 10 letters or digits (a leading $ is dropped).”
    • descriptionstringrequired“What the token is, 1 to 1000 characters.”
    • websitestring“Optional https address.”
    • twitterstring“Optional X handle or profile address.”
  • get_projectson 5 other serversreads or searches

    “Every treasury currently running on VaultBags (any Bags token can integrate, not just $VAULT).”

    Takes no inputs.

  • get_project_treasuryreads or searches

    “One integrated project's live treasury by SPL token mint: the claimable pool and lock-boost pool real-world-asset holdings and USD values, the distribution split, and total fees processed.”

    1 input, 1 required
    • mintstringrequired“The project's SPL token mint address (base58).”
  • get_agenton 63 other serversreads or searches

    “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.”

    1 input, 1 required
    • mintstringrequired“The agent's SPL token mint address (base58).”
  • get_vault_docsreads or searches

    “Condensed protocol documentation: how the vault works, the 70/20/10 distribution, Smart Allocation, locking, claiming, and links to the live surfaces.”

    Takes no inputs.

Show 28 more tools
  • list_rwasreads or searches

    “A curated, on-chain-certified registry of openly transferable tokenized real-world assets on Solana (tokenized gold, US Treasuries, and US equities/ETFs from issuers like Backed/xStocks, Ondo and oro…”

    2 inputs
    • categorystring“Filter by asset category.”
    • issuerstring“Filter by issuer id.”
  • get_rwareads or searches

    “Look up one tokenized real-world asset by its symbol (e.g.”

    1 input, 1 required
    • querystringrequired“A token symbol (case-insensitive) or an exact Solana mint address.”
  • get_protocol_meterreads or searches

    “The Meter: one consolidated snapshot of the protocol's live, receipt-backed numbers.”

    Takes no inputs.

  • get_autonomyreads or searches

    “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.”

    Takes no inputs.

  • get_agent_passporton 3 other serversreads or searches

    “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.”

    Takes no inputs.

  • get_rwa_performancereads or searches

    “The vault's REAL position performance per RWA (gold, S&P 500, US treasuries) since purchase: cost basis, average cost, current value and return, in both USD and SOL terms, reconstructed from actual o…”

    Takes no inputs.

  • get_shadow_vs_brainreads or searches

    “The shadow analyst scoreboard: every day a language model makes its own allocation call from the same market signals as the deterministic model plus the day's headlines, and this measures it against …”

    Takes no inputs.

  • get_recent_cyclesreads or searches

    “The latest distribution cycles across every integrated project: SOL processed, whether all swaps succeeded, and the on-chain distribution transaction receipt for each.”

    1 input
    • limitinteger“How many recent cycles to return (default 5).”
  • get_monthly_reportsreads or searches

    “The agent's closed books: one report per calendar month with fees claimed, cycles run, real-world assets distributed, value claimed by holders, decisions frozen and stamped, and its own settled earni…”

    1 input
    • monthsinteger“How many recent months to return (default 12).”
  • get_treasury_historyon 1 other serverreads or searches

    “The treasury's value over time: per-sample total USD and the balance and USD value of gold, the S&P 500 and US treasuries.”

    2 inputs
    • daysinteger“Window length in days (default 30, max 365).”
    • pointsinteger“How many samples to return across that window (default 60, max 200).”
  • get_holder_distributionon 1 other serverreads or searches

    “Who holds the token, in aggregate: the number of distinct holding WALLETS (not token accounts, with the protocol's own wallets and the pools excluded), how that changed over the last day and week, ho…”

    Takes no inputs.

  • get_recent_activityon 3 other serversreads or searches

    “Recent trading in aggregate over the last 24 hours and 7 days: trades, buys, sells, distinct buyers, distinct sellers and distinct traders (a wallet that both bought and sold counts once, so traders …”

    Takes no inputs.

  • get_payout_integrityreads or searches

    “Every holder payout the protocol has ever recorded, looked up on Solana and counted: confirmed by the chain, rejected by it, or no longer carried in the answering node's history.”

    Takes no inputs.

  • get_lock_tierreads or searches

    “The visible tier of a lock.”

    2 inputs
    • daysinteger“A lock term in days, to ask which tier it would reach.”
    • walletstring“A Solana wallet address, to ask which tier it currently holds.”
  • get_proof_of_reservesreads or searches

    “Proof of Reserves: the named on-chain wallets that hold the vault's real-world assets, the certified issuer behind each asset (Backed/xStocks, Ondo, oro), live on-chain balances and USD values, plus …”

    Takes no inputs.

  • “Verify one holder claim against the on-chain Merkle root.”

    1 input, 1 required
    • txstringrequired“The claim's Solana transaction signature (base58).”
  • simulate_lock_boostcalculates or converts

    “Estimate the lock boost with live data: what percentage of circulating $VAULT is locked right now, the shared boost multiplier that fraction produces (the same formula the payout cron uses, capped at…”

    1 input
    • amountnumber“Whole $VAULT tokens you are considering locking.”
  • verify_day

    “Verify a whole day of the claim ledger against its stamped Merkle root, no transaction needed.”

    1 input
    • periodstring“UTC day as YYYY-MM-DD.”
  • get_autonomy_specreads or searches

    “The Autonomy Score's own rules, published so the number can be recomputed rather than believed: every dimension with its weight and scope, the formula behind each 0-100 sub-score, which public endpoi…”

    Takes no inputs.

  • verify_decisionon 4 other servers

    “Verify one daily allocation decision against the hash stamped on-chain that day.”

    1 input
    • datestring“UTC date as YYYY-MM-DD.”
  • get_liquidityon 3 other serversreads or searches

    “The liquidity this protocol has built into its own pool, and whether any of it can be taken back out.”

    Takes no inputs.

  • get_supplyon 2 other serversreads or searches

    “The token's supply, both of the numbers that legitimately carry that name, because picking the wrong one silently produces a wrong percentage.”

    Takes no inputs.

  • get_rafflereads or searches

    “The public state of the holder raffle: whether a draw is open, the window it covers, the weighted ticket total, how many wallets are in it, what is being given away, and the claim grace period.”

    Takes no inputs.

  • get_strategiesreads or searches

    “Every vault strategy: the four presets (Classic, Growth, Hard Money, Income) plus each distinct strategy a live project has frozen.”

    Takes no inputs.

  • get_strategyon 13 other serversreads or searches

    “One vault strategy in depth: its signed asset selection (mint, symbol, category, base weight), which tokens adopted it, and its recent daily decisions with the per-day weights, convictions and on-cha…”

    1 input, 1 required
    • strategystringrequired“A preset id (classic, growth, hard-money, income) or a 64-hex strategy key.”
  • get_my_vaultreads or searches

    “Your own $VAULT position, for the wallet you signed in with: what you can claim right now in gold, the S&P 500 and US Treasuries (tokens and USD), your share of holdings, how much is locked and your …”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_my_claimsreads or searches

    “Your own claim history in $VAULT, for the wallet you signed in with: how many claims, the total and average value at claim time, how many included the lock boost, your first, latest and largest.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

  • get_my_performanceon 3 other serversreads or searches

    “How your own $VAULT position has done so far, for the wallet you signed in with: what it has earned in RWAs, for how long, at what measured pace, and what locking would add at today's lock levels.”

    Publisher declares: read-only yes · destructive no · idempotent yes · open-world no

    Takes no inputs.

Each quoted sentence is the first sentence of the publisher’s own description. The kind of tool and the “changes data” mark are our AI model’s reading of that description, not something we tested: two differently worded runs had to agree, otherwise no label is shown, and nobody has checked them by hand. A tool without the “changes data” mark is described as only reading, searching or calculating, or the two runs did not agree. No tool was called. Read the publisher’s full description before relying on it. “Publisher declares” lists the hints the server itself sends with the tool (MCP annotations: read-only, destructive, idempotent, open-world); they are the publisher's claims, not checked by us. Inputs are the parameters in the tool's own input schema: name, declared type, whether it is required, and the first sentence of its description. Read 2026-10-23.

How well are its tools described?

Features #4 and #5

How clearly this server's own tool descriptions say what a tool does, and how consistent its tool list is. The first part is an AI model's yes/no reading of each description; the second part is counted. We do not turn it into a grade.

Descriptions

AI reading of each description

Says what the tool does
100% of 40 tools
Says what it returns
100% of 40 tools
States limits, defaults or errors
8% of 39 tools
Says when to use it
3% of 39 tools
Items covered per tool
2.1 of 4 on average

Counted from the listing

Parameters with a description
100% of 32
Tools with a description
100% of 40
Typical description length
483 characters

The tool set

Counted from the listing

Tools
40
Size of the list
about 6,971 tokens for an agent to load (characters ÷ 4)
Naming
40 of 40 names use snake_case

AI reading: easy to mix up

No pair found.

The AI items cover 40 of 40 tools: for a tool where two differently worded runs disagreed, that item is left out. They were not checked by hand, and no tool was called. “Easy to mix up” means two tools whose names or descriptions overlap without saying how they differ; the AI found none. We do not rate whether the tool set is complete or whether side effects are spelled out, because our AI reading of those was not reliable enough.

How do I add it to my client?

Config from the registry entry

From the remote endpoint (Streamable HTTP)

We connected to this URL on 2026-10-23 (a read-only session: no tool was called).

Add to CursorAn install link in the format Cursor documents, holding the Cursor config below.

Claude Desktop or claude.ai
Settings → Connectors → Add custom connector, then paste:
https://vaultbags.app/api/mcp
Cursor · .cursor/mcp.json in a project, or ~/.cursor/mcp.json
{
  "mcpServers": {
    "vaultbags": {
      "url": "https://vaultbags.app/api/mcp"
    }
  }
}
VS Code · .vscode/mcp.json
{
  "servers": {
    "vaultbags": {
      "type": "http",
      "url": "https://vaultbags.app/api/mcp"
    }
  }
}
VS Code (command line) · Bash or zsh terminal (macOS, Linux)
code --add-mcp '{"name":"vaultbags","type":"http","url":"https://vaultbags.app/api/mcp"}'
Claude Code
claude mcp add --transport http vaultbags https://vaultbags.app/api/mcp
Try it in the MCP Inspector · runs on your machine, opens in your browser · Node 22.19+
npx @modelcontextprotocol/inspector@2.11.0 --server-url https://vaultbags.app/api/mcp --transport http
  • The server runs on the operator's infrastructure; it may ask you to sign in when you first connect.
  • The MCP Inspector lists the server's tools, resources and prompts; a tool you call there runs for real.

Built from the server's registry entry with each client's documented format (checked 2026-10-14; the Cursor link and the VS Code command 2026-10-19; the MCP Inspector command 2026-10-21). Values in < > are yours to fill in; this page never contains a key. Where the server needs a setting the entry does not declare, it can still fail to start.

Does the registry listing match what we found?

Feature #6

The registry verifies a package once, when it is published, and does not re-check it. A difference below is about the listing, not a judgement of the publisher.

Registry saysWe foundResultSource · date
Remote endpoint vaultbags.app/api/mcpSession openedmatchesour test · 2026-10-23
No credential declared as requiredOpened a session without any credentialmatchesour test · 2026-10-23

Choosing

Record checks

Public records · not a safety rating

1 of 2 record checks met · 7 do not apply

  • Not ranked by downloads: a remote server publishes no download figure
  • Not ranked by stars: no public GitHub repository
  • MetRegistry entry is active and says how to run itActive, with a package or a remote address.
  • Not metSource repository link opensThe registry entry gives no repository link.
  • Does not applyRepository is not archivedNo public GitHub repository to read.
  • Does not applyCode pushed to the repository in the 90 days before our checkNo public GitHub repository to read.
  • Does not applyRepository publishes a security policy (SECURITY.md)No public GitHub repository to read.
  • Does not applyPackage names its licence with a standard (SPDX) identifierRemote server: it ships no package.
  • Does not applyThe version the registry lists can be installed and is not withdrawnRemote server: it ships no package.
  • Does not applynpm package carries build provenance (attestation)Remote server: it ships no package.
  • Does not applyNo known critical or high advisory in the package or its dependenciesRemote server: it ships no package.

Read from public records only: the registry entry, npm/PyPI, GitHub and advisory databases, checked 2026-10-22. No tool was called. Only “met” and “not met” are counted, so the total differs between servers; a check that does not apply or that we could not run is listed, never counted against it. It is not a safety rating. How each check works · Leaderboards

Common questions about app.vaultbags/vaultbags

Answered from the data above

Is app.vaultbags/vaultbags safe to install?

We do not rate servers as safe or unsafe. 1 of its 2 applicable record checks are met (facts from public records, each listed on this page). What the records show: 1 of its tools describes changing data (our AI model's reading of the descriptions). These are facts with their sources on this page, not a safety guarantee, and we did not run its tools.

Does app.vaultbags/vaultbags need an API key or sign-in?

It opened a session without any credential on 2026-10-23. The registry entry declares no required credential; no declaration is not a guarantee.

Has app.vaultbags/vaultbags been security tested?

Partly. 5 of the 16 checks that apply to it were exercised. We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security verdict is published before verification.

What can app.vaultbags/vaultbags do?

It lists 40 tools. In our AI model's reading of their descriptions (two runs had to agree, nobody checked it by hand), they include tools that read or search, generate content and calculate or convert. We did not call any tool, so this describes the text, not the behaviour.

Can app.vaultbags/vaultbags change or delete data?

1 of its tools says in its description that it creates, edits, deletes, sends or runs something (our AI model's reading). We did not call any tool, so we cannot say what actually happens.

Found this page useful?

Anonymous · no sign-in

A quick, anonymous reaction — no account, no email. One per kind from your browser. The tally updates when the page is next refreshed, and it is only a rough count, never a safety rating or a measured number of people.

Similar servers

Same topic · AI-read

Active servers whose topic is also “finance-and-payments” and that have at least one tool of the same kind; most kinds in common first, then most GitHub stars. The topic and the tool kinds are an AI model's reading of the publishers' descriptions, not checked by hand. Similar is not a recommendation.

Compare with another server

Side by side: registry entry, our read-only session, the tools and the 18 classification fields. Same values as each page; no score.

Security testing

What did we test, and what did we leave out?

18 checks · features #1, #2

Not probed (we call no server's tools)

We connected and read what the server declares, but did not call its tools: ProtocolProbe calls no server's tools for anything it publishes. This is our choice, not a block by the server. No security score is given; a check we did not run is never counted as passed.

The 18 checks at a glanceour test · 2026-10-23
  1. Inventory: exercised
  2. Hidden instructions: exercised
  3. Real execution: not run · our policy
  4. Secret leak: not run · nothing to check it against
  5. Internal addresses: not run · our policy
  6. Unconfirmed changes: not run · our policy
  7. Bad input: not run · our policy
  8. Model requests: not run · nothing to check it against
  9. Sensitive questions: not run · nothing to check it against
  10. Folder boundary: not run · our policy
  11. Log leaks: not run · nothing to check it against
  12. Hidden content: exercised
  13. Fake assistant turns: exercised
  14. Token passthrough: not applicable
  15. Token audience: not applicable
  16. Sign-in redirect: not run · our policy
  17. Consent handling: not testable from outside
  18. Sign-in metadata: exercised

5 exercised11 not run (reason given)2 not applicable

Each check ends in exactly one state: exercised, not run (with the reason), or not applicable (with the reason). 5 of the 16 checks that apply to it were exercised. We do not publish security-check outcomes for named servers.

Exercised · 5
  • 1Inventory
    tool-list
    Reads the declared tools, resources and prompts.exercised
  • 2Hidden instructions
    description-poisoning
    Looks for hidden instructions in tool descriptions.exercised
  • 12Hidden content
    audience-hiding
    Checks resources that hide content from the user.exercised
  • 13Fake assistant turns
    fake-assistant-turn
    Checks prompts that pose as the assistant's own words.exercised
  • 18Sign-in metadata
    oauth-url-scheme
    Checks the published sign-in metadata for unsafe URLs.exercised
Not run, with the reason · 11
  • 3Real execution
    real-execution
    Calls a tool and checks what really happens.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 4Secret leak
    canary-leak
    Plants a fake secret and checks whether it leaks.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 5Internal addresses
    ssrf
    Checks whether a tool can be steered to internal addresses.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 6Unconfirmed changes
    write-without-confirmation
    Checks whether tools that change data act without asking.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 7Bad input
    error-handling
    Sends bad input and watches how the server answers.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 8Model requests
    sampling
    Checks whether the server asks the client's model to act for it.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 9Sensitive questions
    elicitation-sensitive-data
    Checks whether the server asks users for sensitive data.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 10Folder boundary
    root-boundary
    Checks whether the server reaches outside the folders it was given.This check calls the server's tools. ProtocolProbe calls no server's tools for anything it publishes; an operator can run this check on their own server with our self-test command.not run · our policy
  • 11Log leaks
    logging-side-channel
    Checks whether log messages carry data they should not.This check needs at least one successful tool call to have something to check, and no tool was called.not run · nothing to check it against
  • 16Sign-in redirect
    open-redirect
    Checks the sign-in redirect for abuse.Testing the sign-in redirect means sending probes to the operator's sign-in service, which we do not do.not run · our policy
  • 17Consent handling
    confused-deputy
    Checks consent handling when one service acts for another.Depends on the operator's own consent screen, which differs per server and cannot be tested from outside.not testable from outside
Does not apply to this server · 2
  • 14Token passthrough
    token-passthrough
    Checks whether the server forwards a user's token to other services.The server opened a session without sign-in, so there is no token flow to check.not applicable
  • 15Token audience
    token-audience-validation
    Checks whether tokens meant for another service are accepted.The server opened a session without sign-in, so there is no token flow to check.not applicable

Source: our own test, 2026-10-23, mcp-runtime-engine@0.1.0. Which checks count and why follows our published scoring model.

What happened during the test?

Feature #8

The steps in order, as the test record holds them.

  1. 0 msStarted a read-only session with the server's remote endpoint
  2. 839 msConnected after 0 redirects. No credential was sent or needed.
  3. Read the inventory: 40 tools, 6 resources, 6 prompts.
  4. 15,898 msFinished: 5 checks exercised.

Reference

How is it classified?

18 fields

One value per field, each with its source. Fields written by AI models are marked. A field with no value says why.

TopicAI-classified
AI-classified · 2026-10-23
Pricing modelAI-classified
no value
No value: the AI answer was held back because the quoted text did not clearly support it.
Programming language
does not apply
no existing GitHub repository (server declares no repository link, so there is nothing to fetch)
Hosting type
registry · 2026-10-23
MCP capability
prompts, resources, tools
our test · 2026-10-23
Transport
streamable HTTP
registry · 2026-10-23
Required credentials
none declared
registry · no declaration is not a guarantee
Package registry
does not apply
remote-only server: no package is shipped, so there is no package registry
Freshness
0–30 days
registry updatedAt · 2026-10-23
Lifecycle status
registry · 2026-10-23
License class
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Integrity hash
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Signature / provenance
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Dependency advisories
does not apply
ships no package, so there are no dependencies to audit
Popularity
does not apply
remote-only server: ships no package, so there is nothing to look up in a package registry
Publisher signals
not stated
no readable GitHub owner to describe
Maintenance
does not apply
server declares no repository link, so there is nothing to fetch
Environment
the publisher's infrastructure
where it runs, from the hosting type

“Not stated” means the source did not state it; “does not apply” means it does not apply to this kind of server; “our limit” means our own lookup failed. A linked value opens the directory filtered to the same value.

Cite or correct this page

Sources and corrections

Suggested citation

ProtocolProbe. “app.vaultbags/vaultbags: MCP server record.” Data checked 2026-10-23. https://protocolprobe.com/mcp/servers/app.vaultbags/vaultbags

Figures are valid for the date shown. Our facts on this page are CC BY 4.0: reuse them with a link and the check date. Quoted text (the publisher’s descriptions, website quotes, tool names) is not ours to license.

As JSON: this record in the API · API documentation.

Badge for your README

ProtocolProbe: 1 of 2 record checks met

[![ProtocolProbe](https://protocolprobe.com/api/v1/badge/app.vaultbags/vaultbags)](https://protocolprobe.com/mcp/servers/app.vaultbags/vaultbags)

It shows this server's record-check count: facts from public records, no tool called. It is not a security rating or a pass. It links here and updates after each data reload.

Something wrong, or is this yours?

If a fact here is wrong, tell us and we will re-check it. If you operate this server, you can run our checks on it yourself with the free self-test command; we call no server’s tools ourselves for anything shown here.

Write to hello@protocolprobe.com · corrections log · methodology