Locker

What locker does

The locker MCP server provides a mailbox and storage system addressed by wallet information. It is intended for agents that need to send or retrieve content through a wallet-linked destination rather than an unspecified shared channel.

The available description identifies two core access patterns. Agents can pay to send using x402, and they can read without payment when they possess the applicable key. The listing does not specify whether mailbox items and stored data use separate operations, how content is structured, or how long data remains available.

How it works

The locker MCP server uses wallet addressing to identify the destination for mailbox or storage activity. A send operation is associated with payment through x402. Reading follows a different access rule: it is free when the agent has the required key.

This creates a split between write and read access. An agent that needs to deliver information should be prepared for the x402 payment step. An agent that needs to retrieve information should have the key associated with the requested content or destination. The supplied material does not describe payment limits, supported currencies, key generation, key rotation, message formats, or error handling.

The description also does not explain whether the server stores arbitrary files, text messages, structured records, or a combination of these. Treat “mailbox + storage” as the supported product scope, while confirming the exact payload model before building an application around it.

Limitations and notes

No README content was available for this listing. As a result, installation commands, transport details, package names, environment variables, authentication setup, tool names, and client-specific instructions cannot be established from the supplied material.

The locker MCP server may fit an agent workflow that needs wallet-addressed delivery with paid sending and key-controlled reading. It is not possible to determine from the listing whether it supports a particular desktop client, editor, command-line host, or deployment platform. Client compatibility should therefore be checked against the server’s current documentation before selection.

The available description does not identify a software license. It also does not document administrative controls, encryption behavior, retention guarantees, delivery notifications, search, deletion, or access auditing. Those omissions are documentation limits rather than confirmed absences from the underlying service.