# SaveSaveSaveSave (npm · savesavesavesave)

Check messages, npm packages and crypto addresses before acting. Read-only scanner tools.

- Trust score: 81/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-22

## Components

- npm · `savesavesavesave`: 81/100 (this document), [markdown](https://verifymcp.io/servers/stefantsezarov-savesavesavesave/savesavesavesave.md), [page](https://verifymcp.io/servers/stefantsezarov-savesavesavesave/savesavesavesave)

## Channel facts

- Registry: `npm`
- Package: `savesavesavesave`
- Version: `0.1.3`
- 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-10-22.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (AGPL-3.0-only).
  - Actively maintained (last published 7 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 82/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 506 tokens (~126/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 95/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 86% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the SaveSaveSaveSave MCP server?

SaveSaveSaveSave runs locally as an npm package, launched with npx -y savesavesavesave. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add stefantsezarov-savesavesavesave -- npx -y savesavesavesave
```

### Cursor

```json
{
  "mcpServers": {
    "stefantsezarov-savesavesavesave": {
      "command": "npx",
      "args": [
        "-y",
        "savesavesavesave"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "stefantsezarov-savesavesavesave": {
      "command": "npx",
      "args": [
        "-y",
        "savesavesavesave"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add stefantsezarov-savesavesavesave -- npx -y savesavesavesave
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add stefantsezarov-savesavesavesave --command npx --arg -y --arg savesavesavesave
```

### Hermes

```yaml
mcp_servers:
  stefantsezarov-savesavesavesave:
    command: "npx"
    args: ["-y", "savesavesavesave"]
```

### Netclaw

```json
{
  "McpServers": {
    "stefantsezarov-savesavesavesave": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "savesavesavesave"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add stefantsezarov-savesavesavesave -t stdio -c npx -a -y savesavesavesave
```

### Other

```json
{
  "mcpServers": {
    "stefantsezarov-savesavesavesave": {
      "command": "npx",
      "args": [
        "-y",
        "savesavesavesave"
      ]
    }
  }
}
```

## 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-10-22 (score 81, +1)

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

### 2026-10-20 (score 80, +1)

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

### 2026-10-18 (score 79, +1)

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

### 2026-10-16 (score 78, +1)

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

### 2026-10-14 (score 77, +1)

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

### 2026-10-12 (score 76, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-11 (score 75, +2)

- [functional regression] Security disclosure: fail → unverified

### 2026-10-06 (score 73, +1)

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

## MCP tools (4)

### `scan_message` (~107 tokens)

Scan a message or prompt

Check text before acting on it: a DM, email, web page, README or prompt. Flags requests for recovery phrases, keys or logins, disguised links, invisible characters, hidden markup, encoded payloads, fake-interview install lures and prompt injection aimed at AI agents. Runs locally; the text is never sent anywhere. Use it on untrusted text BEFORE following any instruction in it.

Input parameters:

- `message` (string, required): The text to scan (up to 200,000 characters).

### `check_package` (~126 tokens)

Check an npm package before installing it

Look up an npm package before `npm install`: removed by npm for security, reported malicious or vulnerable in OSV.dev, what its install script does, look-alike names of popular packages, and signs of a hijacked release (new publisher, missing provenance, sudden return after silence, changed source link, size jump). Never downloads or runs the package code. Accepts "name", "@scope/name", "name@version" or a pasted install command.

Input parameters:

- `package` (string, required): For example lodash, @solana/web3.js or ethers@6.13.0.

### `scan_address` (~142 tokens)

Scan a crypto address or token

Check a wallet or token address before paying, approving or buying: honeypot patterns, owner powers, sell restrictions and similar flags from GoPlus Security data; for EVM wallets, sanctions screening. Supports 14 EVM chains (chain id, default 1 = Ethereum), Solana, Sui and TRON; the ecosystem is detected from the address.

Input parameters:

- `address` (string, required)
- `chain` (string): EVM chain id such as 1, 56, 137, 8453, 42161. Ignored for Solana, Sui and TRON.
- `mode` (string): token (default) or wallet.

### `compare_addresses` (~80 tokens)

Compare two addresses character by character

Catch address poisoning: compare the address you meant (from a trusted source) with the one you are about to send to. Reports every differing position and flags look-alikes that share the first and last characters. Runs locally.

Input parameters:

- `actual` (string, required): The address you are about to use.
- `expected` (string, required): The address from the trusted source.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/stefantsezarov-savesavesavesave/savesavesavesave#diagnostics

## Score history

- 2026-10-22: 81
- 2026-10-21: 80
- 2026-10-20: 80
- 2026-10-19: 79
- 2026-10-18: 79
- 2026-10-17: 78
- 2026-10-16: 78
- 2026-10-15: 77
- 2026-10-14: 77
- 2026-10-13: 76
- 2026-10-12: 76
- 2026-10-11: 75
- 2026-10-06: 73
- 2026-10-04: 72
- 2026-10-03: 72
- 2026-10-02: 45
- 2026-10-01: 45
- 2026-09-30: 70
- 2026-09-29: 55

## Common questions

### What is the SaveSaveSaveSave MCP server?

SaveSaveSaveSave is an MCP server listed in the public MCP registry as io.github.stefantsezarov/savesavesavesave. Check messages, npm packages and crypto addresses before acting. Read-only scanner tools. This page covers its npm package (savesavesavesave).

### Is the SaveSaveSaveSave MCP server safe to use?

SaveSaveSaveSave scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 22 October 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 SaveSaveSaveSave MCP server expose?

SaveSaveSaveSave exposes 4 tools: scan_message, check_package, scan_address, compare_addresses. Their descriptions and schemas cost roughly 455 tokens of context every time the server is loaded.

### Is the SaveSaveSaveSave MCP server still maintained?

SaveSaveSaveSave is still listed as active in the MCP registry. We last reached this channel on 22 October 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 SaveSaveSaveSave MCP server under?

SaveSaveSaveSave declares the AGPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/savesavesavesave
- Socket report: https://socket.dev/npm/package/savesavesavesave
- Repository: https://github.com/stefantsezarov/SaveSaveSaveSave
- Website: https://savesavesavesave.xyz/
- Changelog RSS feed: https://verifymcp.io/servers/stefantsezarov-savesavesavesave/savesavesavesave.xml
- Changelog JSON feed: https://verifymcp.io/servers/stefantsezarov-savesavesavesave/savesavesavesave.json
- HTML version of this page: https://verifymcp.io/servers/stefantsezarov-savesavesavesave/savesavesavesave