Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

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.

46 Trust /100

Last scanned (5 hours ago)

Scores higher than 76% of MCPB servers

Category Memory and Knowledge

Trust breakdown (7 categories)

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 Security24
  • 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.Unverified
  • Known CVEs were checked across the 109 of 109 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • No install/post-install scripts declared.Pass
  • 30 of 109 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency45
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 460 tokens (~46/item across 10 items; 10 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage89
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • 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. See how to fix → Fail
  • An AI judge read all 10 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
Changelog

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.

  • 4 Nov 26 +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.

  • 2 Nov 26 +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.

  • 1 Nov 26 −1
    • Stability: 0.00 → unverified ▼ security
    • Tool coverage: 100% → 67% ▼ functional
    • Schema quality: 40 → 46 ▼ functional
  • 31 Oct 26 45

    First indexed and scored.

Diagnostics

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 5 Nov 2026 · Analysed mcpb/https://github.com/Tifdt/port402-memory-mcp/releases/download/v1.2.0/port402-memory.mcpb

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem mcpb
Reason No attestation published

Background: How many MCP packages publish verified provenance →

Dependencies 109 packages
Packages resolved 109
Stale 30
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 10 exposed · ~460 tokens

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 →

Tool Tokens
inbox_get_url ~55

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.

NameTypeReqDescription
rotateboolean––

No output schema declared.

No examples provided.

inbox_read ~49

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

NameTypeReqDescription
ackboolean––
limitinteger––

No output schema declared.

No examples provided.

memory_delete ~41

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

NameTypeReqDescription
keystringyesMemory key, e.g. 'notes' or 'project:todo'

No output schema declared.

No examples provided.

memory_export ~34

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

memory_get ~42

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

NameTypeReqDescription
keystringyesMemory key, e.g. 'notes' or 'project:todo'

No output schema declared.

No examples provided.

memory_list ~20

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

memory_set ~66

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

NameTypeReqDescription
keystringyesMemory key, e.g. 'notes' or 'project:todo'
value––Any JSON value, max 64 KB

No output schema declared.

No examples provided.

reminder_cancel ~24

Cancel a pending reminder ($0.001).

NameTypeReqDescription
idstringyes–

No output schema declared.

No examples provided.

reminder_list ~17

List your pending reminders ($0.001).

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

reminder_schedule ~112

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.

NameTypeReqDescription
atstring–ISO 8601 date, alternative to inSeconds
inSecondsnumber–Delay in seconds
message––Any JSON, max 16 KB: what you want to be reminded of
webhookstring–Public https URL to POST the reminder to

No output schema declared.

No examples provided.

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.

mcpb · port402-memory.mcpb

Download bundle

Check the download matches the SHA-256 the MCP registry declares before you open it. If it does not match, do not open the file.

SHA-256

991012492acb11fbbf67c39bce2c86aaf528fa581bf85547d046b85b008cebfc

macOS / Linux

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

Windows (PowerShell)

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

Run it in the folder you saved the bundle to, then open the file with an MCPB-capable host such as Claude Desktop.

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.