Most of the surface is what any payments account needs: create, log in, fund, send, get paid, read history. The call that changes what an agent can do is pay_and_get_402_protected_url, which settles a paywalled request from the managed account and returns the content — a machine buying access with nobody in the loop. Read send_money's own condition before treating a send as final: money sent to an email or phone that is never claimed returns to the sender after 3 days. And note where custody sits, because get_private_key_of_wallet exists at all — the key is retrievable through the service rather than held only by you.
A managed Solana payments client with 11 tools covering wallet creation and one-time-password login, funding, sending, payment links, wallet and transaction reads, private key retrieval and paying a 402-protected URL.
- Wallet creation and login in one flow: get_wallet_and_otp creates a wallet for an email address or sends a one-time password to it, and login_with_otp connects using the code that arrived by email.
- Funding both ways: fund_my_wallet returns a link for adding a chosen amount by credit card, or the wallet's Solana address for funding on chain.
- Sending with a claim window: send_money sends to an email, a phone number or a Solana wallet, with its description stating that money a new user does not claim within 3 days returns to the sender.
- Getting paid: request_payment_link creates a payment link payable by credit card or any Solana token, automatically converted to USDC, carrying a description, logo, notification email, webhook and return URLs.
- Reading the account: get_wallet_info returns the Solana address, balance and token detail, get_wallet_history returns funds received and sent with dates, and get_transaction_state returns one transaction's state from its Solana transaction id.
- Machine-payable URLs: pay_and_get_402_protected_url pays an HTTP 402-protected URL from the managed account and returns the result.
- Key custody: get_private_key_of_wallet retrieves the wallet's private key through the secured P-Link app.
An email address you can read, since wallet creation and login both run through a one-time password sent to it, and a P-Link API key passed to the server at startup.
One command plus a key — npx plink-mcp-server --apikey=abcdef123456, then supply credentials