Deaddrop
LocalAbout Deaddrop
Deaddrop is an MCP server for sharing secrets through single-use links that expire after access. It encrypts secrets locally and uses USDC payments over x402 for creation; revealing a link is free.
Key features
- 01Create encrypted one-time secret links
- 02Reveal and consume a secret link
- 03Local AES-256-GCM encryption
- 04USDC payment through x402
- 05Secret key remains in link fragment
Use cases
- 01Share an API key with a coworker
- 02Send a secret that should be revealed once
- 03Avoid exposing plaintext to the service
MCP support
The MCP server provides tools to create and reveal DeadDrop secrets. Creating a secret pays in USDC over x402, while revealing one is free and needs no wallet.
Configuration
Local server config is the same for every client. Copy it into your client’s MCP config file.
We haven’t collected a package or remote endpoint for this server. Follow the instructions in the project README.
Tools
Local servers expose tools only once running on your machine, and the maintainer has not provided a tool list.
Details
From the project READMEdeaddrop-mcp
MCP server that lets AI agents (Claude Code, Claude Desktop, anything MCP-capable) share secrets through DeadDrop - self-destructing one-time links, paid per call with USDC over x402.

Two tools:
deaddrop_create_secret- encrypts the secret locally (AES-256-GCM), pays $0.01 in USDC via x402, returns a one-time link. The link works exactly once, then the secret is destroyed.deaddrop_reveal_secret- consumes a one-time link and decrypts locally. Free, no wallet needed.
Zero-knowledge end to end: the AES key is generated in this process and
travels only in the link fragment (#...); the payer wallet key also stays
here. The DeadDrop server only ever sees ciphertext and an x402 payment.
Install
git clone https://github.com/jerrywrongalot-byte/deaddrop-mcp
cd deaddrop-mcp
npm install
Configure
Claude Code:
claude mcp add deaddrop -e DEADDROP_PAYER_KEY=0x<key> -- node /absolute/path/to/deaddrop-mcp/server.mjs
Claude Desktop / any MCP client (.mcp.json / claude_desktop_config.json):
{
"mcpServers": {
"deaddrop": {
"command": "node",
"args": ["/absolute/path/to/deaddrop-mcp/server.mjs"],
"env": { "DEADDROP_PAYER_KEY": "0x<key>" }
}
}
}
Environment
| Variable | Meaning |
|---|---|
DEADDROP_PAYER_KEY | EVM private key holding USDC on Base. Needed only for CREATE (it pays $0.01/secret); reveal works without it. |
DEADDROP_NETWORK | base (default) or base-sepolia for testing. |
DEADDROP_BASE_URL | Override the service URL (defaults to the live service). |
Wallet safety (read this)
- Use a dedicated key with a small USDC balance (a few dollars covers hundreds of secrets), not a main wallet. The key signs real payments.
- Payments are gasless for the payer (EIP-3009): the key needs USDC only, no ETH.
- x402-fetch enforces a max-payment cap (default 0.10 USDC per call), so a rogue or mistyped server URL cannot drain the key.
- The service never receives the key OR the plaintext - see the API's agent-facing spec at /llms.txt.
Example
"Drop this API key for my coworker: sk-live-... - 1 day expiry"
The agent calls deaddrop_create_secret, pays a cent, and hands back
https://deaddrop.../s/<id>#<key>. First open reveals and destroys it;
link previewers can't burn it (reveal is an explicit action).
License
MIT
Comments
New to MCP?
From what the protocol is to installing your first server, these answers cover most first questions.
An open protocol that defines how AI applications connect to external tools and data in a uniform way. Clients talk to the model; MCP servers provide tools, resources and prompt templates. They exchange standard messages, so one server can be reused by many clients.