# Port 402 Memory (mcpb · port402-memory.mcpb)

Memory, inbox and alarm clock for AI agents, paid per call in USDC on Base (x402). No API key.

- Trust score: 46/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- mcpb · `port402-memory.mcpb`: 46/100 (this document), [markdown](https://verifymcp.io/servers/tifdt-port402-memory/port402-memory.md), [page](https://verifymcp.io/servers/tifdt-port402-memory/port402-memory)

## Channel facts

- Registry: `mcpb`
- Package: `https://github.com/Tifdt/port402-memory-mcp/releases/download/v1.2.0/port402-memory.mcpb`
- Transport: `stdio`
- SHA-256: `991012492acb11fbbf67c39bce2c86aaf528fa581bf85547d046b85b008cebfc`

## 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-11-05.

- **Supply Chain Security**: 24/100
  - No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.
  - Known CVEs were checked across the 109 of 109 dependencies we could resolve, so this covers what we could see, not the whole tree.
  - No install/post-install scripts declared.
  - 30 of 109 dependencies flagged as unhealthy.
- **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 (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 460 tokens (~46/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 89/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "memory_delete" implies "delete" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Port 402 Memory MCP server?

Port 402 Memory ships as an MCPB bundle, a single file you download and open in an MCP host that supports MCPB bundles, such as Claude Desktop. The host reads the launch command from the bundle's own manifest, so there is no command to copy. Before opening it, check the file's SHA-256 matches the one the MCP registry declares for it, 991012492acb11fbbf67c39bce2c86aaf528fa581bf85547d046b85b008cebfc; the commands to do that are on this page. If it does not match, do not open it.

- Download bundle: `https://github.com/Tifdt/port402-memory-mcp/releases/download/v1.2.0/port402-memory.mcpb`
- SHA-256: `991012492acb11fbbf67c39bce2c86aaf528fa581bf85547d046b85b008cebfc`

### Verify on macOS / Linux

```bash
echo "991012492acb11fbbf67c39bce2c86aaf528fa581bf85547d046b85b008cebfc  port402-memory.mcpb" | shasum -a 256 -c
```

### Verify on Windows (PowerShell)

```powershell
(Get-FileHash -Algorithm SHA256 .\port402-memory.mcpb).Hash -eq "991012492acb11fbbf67c39bce2c86aaf528fa581bf85547d046b85b008cebfc"
```

## 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-11-04 (score 46, +1)

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

### 2026-11-02 (score 45, +1)

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

### 2026-11-01 (score 44, −1)

- [security regression] Stability: 0.00 → unverified
- [functional regression] Tool coverage: 100% → 67%
- [functional regression] Schema quality: 40 → 46

### 2026-10-31 (score 45)

First indexed and scored.

## MCP tools (10)

### `memory_set` (~66 tokens)

Save a JSON value under a key in your persistent memory ($0.002). Survives restarts and sessions.

Input parameters:

- `key` (string, required): Memory key, e.g. 'notes' or 'project:todo'
- `value`: Any JSON value, max 64 KB

### `memory_get` (~42 tokens)

Read a value back from your persistent memory ($0.001).

Input parameters:

- `key` (string, required): Memory key, e.g. 'notes' or 'project:todo'

### `memory_list` (~20 tokens)

List the keys in your persistent memory ($0.001).

### `memory_delete` (~41 tokens)

Delete a key from your persistent memory ($0.001).

Input parameters:

- `key` (string, required): Memory key, e.g. 'notes' or 'project:todo'

### `memory_export` (~34 tokens)

Export your whole memory as one JSON document, format port402-memory-export/1 ($0.002). Use it for backups.

### `inbox_get_url` (~55 tokens)

Get your inbox URL ($0.002): a secret address anyone (webhooks, other agents, humans) can POST JSON to for free while you're away. rotate=true issues a new one.

Input parameters:

- `rotate` (boolean)

### `inbox_read` (~49 tokens)

Read messages waiting in your inbox, oldest first ($0.001). ack=true removes what you read. Due reminders land here too.

Input parameters:

- `ack` (boolean)
- `limit` (integer)

### `reminder_schedule` (~112 tokens)

Alarm clock ($0.005): schedule a message for later (10 s to 366 days). It lands in your inbox when due, and is POSTed to your https webhook if you give one.

Input parameters:

- `at` (string): ISO 8601 date, alternative to inSeconds
- `inSeconds` (number): Delay in seconds
- `message`: Any JSON, max 16 KB: what you want to be reminded of
- `webhook` (string): Public https URL to POST the reminder to

### `reminder_list` (~17 tokens)

List your pending reminders ($0.001).

### `reminder_cancel` (~24 tokens)

Cancel a pending reminder ($0.001).

Input parameters:

- `id` (string, required)

## Diagnostics

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

## Score history

- 2026-11-05: 46
- 2026-11-04: 46
- 2026-11-03: 45
- 2026-11-02: 45
- 2026-11-01: 44
- 2026-10-31: 45

## Common questions

### What is the Port 402 Memory MCP server?

Port 402 Memory is an MCP server listed in the public MCP registry as io.github.Tifdt/port402-memory. Memory, inbox and alarm clock for AI agents, paid per call in USDC on Base (x402). No API key. This page covers its MCPB bundle (https://github.com/Tifdt/port402-memory-mcp/releases/download/v1.2.0/port402-memory.mcpb).

### Is the Port 402 Memory MCP server safe to use?

Port 402 Memory scores 46 out of 100 on VerifyMCP. 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 Port 402 Memory MCP server expose?

Port 402 Memory exposes 10 tools: memory_set, memory_get, memory_list, memory_delete, memory_export, and 5 more. Their descriptions and schemas cost roughly 460 tokens of context every time the server is loaded.

### What licence is the Port 402 Memory MCP server under?

Port 402 Memory declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the Port 402 Memory MCP server?

VerifyMCP ran 15 checks on Port 402 Memory, covering Known CVEs, Install scripts, Dependency health, Source repository and 11 more. One item could not be completed, a gap on our side rather than a finding about Port 402 Memory: Malware scan. Endpoint Security and Transport & Reachability do not apply to an MCPB bundle, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Repository: https://github.com/Tifdt/port402-memory-mcp
- Website: https://port-402-production.up.railway.app/
- Changelog RSS feed: https://verifymcp.io/servers/tifdt-port402-memory/port402-memory.xml
- Changelog JSON feed: https://verifymcp.io/servers/tifdt-port402-memory/port402-memory/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/tifdt-port402-memory/port402-memory.json
- HTML version of this page: https://verifymcp.io/servers/tifdt-port402-memory/port402-memory