Vaultfire Trust Protocol
NPM · @VAULTFIRE/MCP-SERVER · SCANNED SEP 20
On-chain trust verification and Street Cred for AI agents. ERC-8004, multi-chain.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 32 of 105 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 143 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability87
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 649 tokens (~72/item across 9 items; 7 tools + 2 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Vaultfire Trust Protocol MCP server?
Vaultfire Trust Protocol runs locally as an npm package, launched with npx -y @vaultfire/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @vaultfire/mcp-server
claude mcp add ghostkey316-vaultfire -- npx -y @vaultfire/mcp-server
{
"mcpServers": {
"ghostkey316-vaultfire": {
"command": "npx",
"args": [
"-y",
"@vaultfire/mcp-server"
]
}
}
} {
"servers": {
"ghostkey316-vaultfire": {
"command": "npx",
"args": [
"-y",
"@vaultfire/mcp-server"
]
}
}
} codex mcp add ghostkey316-vaultfire -- npx -y @vaultfire/mcp-server
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ghostkey316-vaultfire": {
"type": "local",
"command": [
"npx",
"-y",
"@vaultfire/mcp-server"
],
"enabled": true
}
}
} openclaw mcp add ghostkey316-vaultfire --command npx --arg -y --arg @vaultfire/mcp-server
mcp_servers:
ghostkey316-vaultfire:
command: "npx"
args: ["-y", "@vaultfire/mcp-server"] {
"McpServers": {
"ghostkey316-vaultfire": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@vaultfire/mcp-server"
]
}
}
} assistant mcp add ghostkey316-vaultfire -t stdio -c npx -a -y @vaultfire/mcp-server
{
"mcpServers": {
"ghostkey316-vaultfire": {
"command": "npx",
"args": [
"-y",
"@vaultfire/mcp-server"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 −3
- Stability: pass → 0.80 functional
- 15 Sept 26 +1
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Sept 26 −3
- Stability: pass → 0.80 functional
- 8 Sept 26 0
- Stability: 0.97 → pass security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed npm/@vaultfire/mcp-server@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 105 packages
| Packages resolved | 105 |
|---|---|
| Stale | 32 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
vaultfire_discover_agents ~74
Find registered AI agents by capability tags. Returns a list of agent addresses that match the requested capabilities. Capabilities are hashed on-chain.
| Name | Type | Req | Description |
|---|---|---|---|
| capabilities | array | yes | Capability tags to search for (e.g., ["code-review", "translation"]) |
| chain | string | – | Chain to query (default: base) |
No output schema declared.
No examples provided.
vaultfire_get_agent ~72
Get on-chain identity data for an agent address: agent URI, agent type, registration timestamp, and active status. Returns ERC-8004 compliant identity info.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the AI agent (0x...) |
| chain | string | – | Chain to query (default: base) |
No output schema declared.
No examples provided.
vaultfire_get_bonds ~79
Get all partnership bonds for an address. Returns bond IDs and full bond details including partner addresses, partnership type, stake amount (in ETH/native token), creation date, and active status.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address to look up bonds for (0x...) |
| chain | string | – | Chain to query (default: base) |
No output schema declared.
No examples provided.
vaultfire_get_reputation ~74
Get reputation data for an agent: average rating, total feedback count, verified feedback count, and percentage of verified feedback. Ratings are stored on-chain from real interactions.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the AI agent (0x...) |
| chain | string | – | Chain to query (default: base) |
No output schema declared.
No examples provided.
vaultfire_get_street_cred ~104
Get the Street Cred score (0-95) and tier for an agent address. Tiers: Unranked (0), Bronze (1-30), Silver (31-55), Gold (56-75), Platinum (76-95). Also returns the score breakdown showing how each component contributes.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the AI agent (0x...) |
| chain | string | – | Chain to query (default: base) |
No output schema declared.
No examples provided.
vaultfire_protocol_stats ~52
Get Vaultfire Protocol statistics: total registered agents, total bonds created, total active bond value (in native token), and bridge sync count.
| Name | Type | Req | Description |
|---|---|---|---|
| chain | string | – | Chain to query (default: base) |
No output schema declared.
No examples provided.
vaultfire_verify_agent ~125
Full trust verification for an AI agent address: checks on-chain identity (ERC-8004), partnership bonds, Street Cred score (0-95), reputation data, and cross-chain bridge recognition. Returns a trusted/untrusted verdict with reason. Use this before interacting with an unknown agent.
| Name | Type | Req | Description |
|---|---|---|---|
| address | string | yes | Ethereum address of the AI agent to verify (0x...) |
| chain | string | – | Chain to query (default: base) |
| minScore | number | – | Minimum Street Cred score to be considered trusted (default: 20, max: 95) |
No output schema declared.
No examples provided.
What is the Vaultfire Trust Protocol MCP server?
Vaultfire Trust Protocol is an MCP server listed in the public MCP registry as io.github.Ghostkey316/vaultfire. On-chain trust verification and Street Cred for AI agents. ERC-8004, multi-chain. This page covers its npm package (@vaultfire/mcp-server).
Is the Vaultfire Trust Protocol MCP server safe to use?
Vaultfire Trust Protocol scores 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Vaultfire Trust Protocol MCP server expose?
Vaultfire Trust Protocol exposes 7 tools: vaultfire_verify_agent, vaultfire_get_street_cred, vaultfire_get_agent, vaultfire_get_bonds, vaultfire_get_reputation, and 2 more. Their descriptions and schemas cost roughly 580 tokens of context every time the server is loaded.
Is the Vaultfire Trust Protocol MCP server still maintained?
Vaultfire Trust Protocol is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Vaultfire Trust Protocol MCP server under?
Vaultfire Trust Protocol declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.