HTTP 402 has been in the spec for decades with almost nothing behind it; the interesting bet here is that agents are the use case that finally makes it real. What you get is small and specific — a wallet, in the session, able to settle a payment when a service asks for one. The obvious consequence is that a component of your agent stack now holds spendable funds, so the key handling and the balance you fund it with are decisions, not details.
An MCP server that carries a Solana wallet for an AI agent, so the agent can pay for services that respond with HTTP 402. On first run it generates a wallet and prints the public key, the balance in lamports and SOL, and any recent transactions; on later runs it loads the existing private key from the system keyring.
- A wallet the agent can pay from, generated on first launch and reloaded from the keyring afterwards
- Payment for services that answer with HTTP 402, driven from inside the MCP session rather than out of band
- Wallet state on startup — public key, balance in lamports alongside the SOL figure, and recent transactions with explorer links
- A working checkpoint before you wire it into a client: run the server in a terminal and read the wallet information it prints
No account signup — the wallet is created locally and the private key is stored in the system keyring. The README's install line names `latinum-wallet-mcp`, which PyPI does not have. To run from source: create a virtualenv, install `requirements.txt`, then `python3 -m latinum_wallet_mcp.server_stdio`. The pyproject name is `latinum-wallet-mcp` (0.0.30) with the entry point `latinum-wallet-mcp`. Since it holds a spendable key, treat the machine it runs on accordingly.