Local MCP capabilities provider for Expo
VibeDNA Vault is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Encrypted local vault for API keys. Your AI fetches keys on demand and scans code for leaks.
Quickstart
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts VibeDNA Vault as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Is this copy behind the published version?
No parameter schema on file.
[FREE] Check if a named credential exists in the vault before asking the user for it.
No parameter schema on file.
[FREE] Retrieve a credential value from the vault by entry name and field/key name.
No parameter schema on file.
[FREE] List all vault entries - names, categories, field names. No values shown.
No parameter schema on file.
[FREE] Search vault entries by name, category, or notes.
No parameter schema on file.
[FREE] Add a new credential. fields = JSON string e.g. '{\"API_KEY\": \"value\"}'.
No parameter schema on file.
[FREE] Trigger an encrypted backup of the vault now. Returns destination path.
No parameter schema on file.
[FREE] Update fields on an existing entry. fields = JSON dict.
No parameter schema on file.
[FREE] Delete an entry. confirm must equal name exactly (safety check).
No parameter schema on file.
[FREE] Return an entry's fields formatted as KEY=value lines for env loading.
No parameter schema on file.
[FREE] Scan a codebase for plaintext credentials. Checks against vault values
No parameter schema on file.
[FREE] List credentials whose last_rotated timestamp is older than days.
No parameter schema on file.
[FREE] Manually flag a credential as just-rotated. Updates the last_rotated timestamp
No parameter schema on file.
[FREE] Show recent credential-access events. Pass name to filter by entry.
No parameter schema on file.
[FREE] Show recent leak-scan results from the leak ledger.
No parameter schema on file.
[FREE] List available service templates for add_with_template.
No parameter schema on file.
[FREE] Add a credential using a service template. service = key from list_templates
No parameter schema on file.
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install VibeDNA Vault or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (17 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| check_for_update | no tags | |
| credential_exists | no tags | |
| get_credential | no tags | |
| list_credentials | no tags | |
| search_credentials | no tags | |
| add_credential | no tags | |
| backup_vault | no tags | |
| edit_credential | no tags | |
| delete_credential | no tags | |
| export_env | no tags | |
| scan_for_leaks | no tags | |
| check_rotation_due | no tags | |
| mark_rotated | no tags | |
| usage_log | no tags | |
| leak_history | no tags | |
| list_templates | no tags | |
| add_with_template | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 1.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish VibeDNA Vault can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.