# Vaultfire Trust Protocol (npm · @vaultfire/mcp-server)

On-chain trust verification and Street Cred for AI agents. ERC-8004, multi-chain.

- Trust score: 66/100 (medium)
- Change this week: +19
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- npm · `@vaultfire/mcp-server`: 66/100 (this document), [markdown](https://verifymcp.io/servers/ghostkey316-vaultfire/vaultfire-mcp-server.md), [page](https://verifymcp.io/servers/ghostkey316-vaultfire/vaultfire-mcp-server)

## Channel facts

- Registry: `npm`
- Package: `@vaultfire/mcp-server`
- Version: `1.0.2`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Supply Chain Security**: 87/100
  - No malware found by supply-chain analysis.
  - Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - Only part of the dependency tree could be resolved (104 of 108), so this covers what we could see, not the whole tree.
- **Provenance & Transparency**: 19/100
  - Repository check failed: the declared repository URL returned HTTP 404.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 95 days ago).
  - Security-disclosure policy not yet verified: we couldn't inspect the source repository.
- **Schema Quality & AI Usability**: 85/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 649 tokens (~72/item across 9 items; 7 tools + 2 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add ghostkey316-vaultfire -- npx -y @vaultfire/mcp-server
```

### Codex

```bash
codex mcp add ghostkey316-vaultfire -- npx -y @vaultfire/mcp-server
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "ghostkey316-vaultfire": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@vaultfire/mcp-server"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add ghostkey316-vaultfire --command npx --arg -y --arg @vaultfire/mcp-server
```

### Hermes

```yaml
mcp_servers:
  ghostkey316-vaultfire:
    command: "npx"
    args: ["-y", "@vaultfire/mcp-server"]
```

### Other

```json
{
  "mcpServers": {
    "ghostkey316-vaultfire": {
      "command": "npx",
      "args": [
        "-y",
        "@vaultfire/mcp-server"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-02 (score 65, +44)

- [security regression] Provenance: unverified → fail
- [security improvement] Install scripts: unverified → pass
- [security improvement] Known CVEs: unverified → partial
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Schema quality: unverified → excellent
- [functional improvement] License: unverified → pass
- [functional improvement] Dependency health: unverified → partial
- [functional improvement] Maintenance: unverified → pass
- [functional improvement] MCP protocol: unverified → pass
- [functional improvement] Stability: unverified → 0.23
- [functional] Licence: MIT

### 2026-08-01 (score 21, −8)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-31 (score 29, −18)

- [security regression] Malware scan: pass → unverified

### 2026-07-30 (score 47, +29)

- [functional improvement] Tool coverage: unverified → 100
- [functional improvement] Schema quality: unverified → 100

### 2026-07-28 (score 18, −29)

- [functional regression] Schema quality: 100 → unverified
- [functional regression] Tool coverage: 100 → unverified

### 2026-07-27 (score 47)

First indexed and scored.

## MCP tools (7)

### `vaultfire_verify_agent` (~125 tokens)

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.

Input parameters:

- `address` (string, required): 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)

### `vaultfire_get_street_cred` (~104 tokens)

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.

Input parameters:

- `address` (string, required): Ethereum address of the AI agent (0x...)
- `chain` (string): Chain to query (default: base)

### `vaultfire_get_agent` (~72 tokens)

Get on-chain identity data for an agent address: agent URI, agent type, registration timestamp, and active status. Returns ERC-8004 compliant identity info.

Input parameters:

- `address` (string, required): Ethereum address of the AI agent (0x...)
- `chain` (string): Chain to query (default: base)

### `vaultfire_get_bonds` (~79 tokens)

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.

Input parameters:

- `address` (string, required): Ethereum address to look up bonds for (0x...)
- `chain` (string): Chain to query (default: base)

### `vaultfire_get_reputation` (~74 tokens)

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.

Input parameters:

- `address` (string, required): Ethereum address of the AI agent (0x...)
- `chain` (string): Chain to query (default: base)

### `vaultfire_discover_agents` (~74 tokens)

Find registered AI agents by capability tags. Returns a list of agent addresses that match the requested capabilities. Capabilities are hashed on-chain.

Input parameters:

- `capabilities` (array, required): Capability tags to search for (e.g., ["code-review", "translation"])
- `chain` (string): Chain to query (default: base)

### `vaultfire_protocol_stats` (~52 tokens)

Get Vaultfire Protocol statistics: total registered agents, total bonds created, total active bond value (in native token), and bridge sync count.

Input parameters:

- `chain` (string): Chain to query (default: base)

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/ghostkey316-vaultfire/vaultfire-mcp-server#diagnostics

## Score history

- 2026-08-03: 66
- 2026-08-02: 65
- 2026-08-01: 21
- 2026-07-31: 29
- 2026-07-30: 47
- 2026-07-28: 18
- 2026-07-27: 47

## Links

- npm package: https://www.npmjs.com/package/@vaultfire/mcp-server
- Socket report: https://socket.dev/npm/package/@vaultfire/mcp-server
- Changelog RSS feed: https://verifymcp.io/servers/ghostkey316-vaultfire/vaultfire-mcp-server/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/ghostkey316-vaultfire/vaultfire-mcp-server/changelog.json
- HTML version of this page: https://verifymcp.io/servers/ghostkey316-vaultfire/vaultfire-mcp-server