Port 402 Memory

io.github.TifdtPublished by GitHub account Tifdtv1.2.0Updated Nov 1, 2026

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

The publisher's own server: Memory.fit

Overview

AI-generated overview

Paid memory, inbox and reminder service for AI agents, billed per call in USDC on Base through a dedicated wallet key.

What you can do
  • Store, read, list and delete key-value memories, and export them as a signed snapshot
  • Get a secret inbox URL others can post to for free, then read and acknowledge incoming messages
  • Schedule, list and cancel reminders that fire later, optionally via webhook
  • Each call is paid in USDC on Base, with the paying wallet acting as the private namespace
When to use it
Useful when an assistant needs memory that survives sessions, a way to receive messages while it is not running, or scheduled wake-ups, and you are willing to pay small per-call fees in USDC instead of using an account or API key.
Requirements
Runs locally over stdio via npx or the provided desktop bundle, so Node.js is needed. Requires a dedicated Base wallet private key in PORT402_PRIVATE_KEY holding a few USDC, plus network access to the operator's server. Optional PORT402_MAX_USD_PER_CALL sets the per-call spending cap (default 0.01 USD).
Before you install
The server holds a wallet private key that signs payments, so use a dedicated wallet with only a few dollars of USDC. Every tool call spends real money, capped per call by PORT402_MAX_USD_PER_CALL. Stored values are kept unencrypted on the operator's server, so encrypt sensitive data client-side. Tools write, delete and send data, and the inbox URL lets anyone post messages.

Installation

In SourceWeft

  1. Open Port 402 Memory in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

Port 402 Memory — MCP server

A home for AI agents: memory that survives sessions, an inbox others can write to while you're away, and an alarm clock that wakes you up later. No account, no API key: each call is paid in USDC on Base via x402, and the paying wallet is your private namespace.

ToolPrice
memory_set (key, value)$0.002
memory_get (key) — returns updatedAt too$0.001
memory_list$0.001
memory_delete (key)$0.001
memory_export — signed (sha256 + Ed25519)$0.002
inbox_get_url — secret URL anyone can POST to for free$0.002
inbox_read (ack, limit)$0.001
reminder_schedule (inSeconds or at, message, webhook?)$0.005
reminder_list$0.001
reminder_cancel (id)$0.001

Typical loop: schedule a reminder, stop; when it fires (webhook or inbox), read your memory and carry on.

Privacy: values are stored unencrypted on the operator's server; encrypt sensitive values client-side. Key rotation (POST /v1/migrate), retention and shutdown notice: see the service docs.

$1 of USDC ≈ 500 writes or 1,000 reads. Hard cap per call: $0.01 by default (PORT402_MAX_USD_PER_CALL).

Install

Claude Code:

claude mcp add port402-memory -e PORT402_PRIVATE_KEY=0xYOUR_KEY -- npx -y github:Tifdt/port402-memory-mcp

Claude Desktop / Cursor (mcpServers):

json
{ "port402-memory": { "command": "npx", "args": ["-y", "github:Tifdt/port402-memory-mcp"], "env": { "PORT402_PRIVATE_KEY": "0xYOUR_KEY" } } }

Claude Desktop one-click: download port402-memory.mcpb from the latest release and open it.

Use a dedicated wallet with only a few dollars of USDC on Base.

HTTP API (without MCP)

https://port-402-production.up.railway.app — catalog at /pricing.json, /openapi.json, /llms.txt, terms at /terms.

Operated by Faloria — Florian Folio EI (France).

  • MCP Registry name: mcp-name: io.github.Tifdt/port402-memory

Source: README.md at commit 04e1f5a

Tools

0
SourceWeft started this package once in an isolated sandbox, without credentials, to list its tools. That failed: the package type cannot run in the sandbox.

Version history

3
  1. v1.2.0LatestNov 1, 2026
  2. v1.1.0Nov 1, 2026
  3. v1.0.0Oct 31, 2026

Score

40% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts

    Declare a license in the repository or the registry entry.

Other Memory integrations