PayPal, guarded runs on your own machine — the client starts it, so there is no endpoint to ping. 77 installs a week from npm. Last commit 9 Nov 2026.
PayPal's Agent Toolkit with limits on refunds and the owner's Approve/Deny above them.
We read the source, 19 h ago · rules 995398eba69f
Found in continuous integration, deployment or infrastructure files, or in a neighbouring package of the same monorepo. None of this is installed when you add the server: it describes how the project is built and released. We list it because a leaked key in a build pipeline is still a real problem, but it is not something this server does on your machine.
p = subprocess.run([ffmpeg, "-i", path], capture_output=True, text=True)
with open(os.path.join(HERE, args.script)) as f:
spawnSync(process.execPath, ['-e', script], { input: JSON.stringify({ url: target.url, headers: headers(), body: envelopeOf(err, { tags: { origin }, level: 'fatal' }) }), timeout: 4000, stdio: ['pipe', 'ignore', 'ignore'] });
const API = "https://api.telegram.org";
"bytecode": "0x60a0604052348015600e575f80fd5b50604051610c37380380610c37833981016040819052602b916061565b6001600160a01b0381166051576040516301f30c8760e21b815260040160405180910390fd5b6001600160a01b0316608052608c565b5f602082840312156070575f80fd5b81516001600160a01b03811681146085575f8…
body.innerHTML = what + `<p>Sign in to your Fizzl wallet first; you come back here afterwards.</p><div class="row"><a class="btn pri" href="/?connect=${encodeURIComponent(rid)}">Sign in</a></div>`;
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Today is the operative word: we check PayPal, guarded every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.
This server runs on your own machine — install it with the package manager and the client starts it for you. Package name taken from the official registry entry.
claude mcp add paypal-guard -e 'PAYPAL_CLIENT_ID=<PAYPAL_CLIENT_ID>' -e 'PAYPAL_CLIENT_SECRET=<PAYPAL_CLIENT_SECRET>' -- npx -y fizzl-paypal-guard-mcp
{
"mcpServers": {
"paypal-guard": {
"command": "npx",
"args": [
"-y",
"fizzl-paypal-guard-mcp"
],
"env": {
"PAYPAL_CLIENT_ID": "<PAYPAL_CLIENT_ID>",
"PAYPAL_CLIENT_SECRET": "<PAYPAL_CLIENT_SECRET>"
}
}
}
}
[mcp_servers.paypal-guard]
command = "npx"
args = ["-y", "fizzl-paypal-guard-mcp"]
env = { PAYPAL_CLIENT_ID = "<PAYPAL_CLIENT_ID>", PAYPAL_CLIENT_SECRET = "<PAYPAL_CLIENT_SECRET>" }
{
"mcpServers": {
"paypal-guard": {
"command": "npx",
"args": [
"-y",
"fizzl-paypal-guard-mcp"
],
"env": {
"PAYPAL_CLIENT_ID": "<PAYPAL_CLIENT_ID>",
"PAYPAL_CLIENT_SECRET": "<PAYPAL_CLIENT_SECRET>"
}
}
}
}
{
"servers": {
"paypal-guard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"fizzl-paypal-guard-mcp"
],
"env": {
"PAYPAL_CLIENT_ID": "<PAYPAL_CLIENT_ID>",
"PAYPAL_CLIENT_SECRET": "<PAYPAL_CLIENT_SECRET>"
}
}
}
}
Put your own values in place of
<PAYPAL_CLIENT_ID> (Client ID of your PayPal REST app (developer.paypal.com)), <PAYPAL_CLIENT_SECRET> (Secret of your PayPal REST app).
The author’s registry entry marks them as required.
Optional settings from the registry entry, left out of the block above:
PAYPAL_ENVIRONMENT (SANDBOX (default) or PRODUCTION), LIMIT_REFUND (Most per refund without asking you (default 25.00)), LIMIT_REFUND_PER_DAY (Refunds a day in total (default 100.00)), LIMIT_REFUNDS_PER_DAY (Number of refunds a day (default 10)), LIMIT_CURRENCY (Currency of the limits (default USD)), GUARD_POLICY (Other rules as JSON, e.g. {"dispute":"deny","stop":"ask"}), FIZZL_AGENT_KEY (Approvals in the Fizzl Agent Wallet (Telegram + dashboard): an agent key awk_… from wallet.fizzl.eu), TELEGRAM_BOT_TOKEN (Approvals through your own Telegram bot), TELEGRAM_CHAT_ID (Your Telegram chat id (approvals go only there)), APPROVAL_IN_CHAT (off to never ask in the chat app (MCP elicitation)), APPROVAL_MINUTES (How long you have to answer (default 10)).
Wallet for AI agents with on-chain spending limits and owner approval over the limit
Agent wallet with limits: pays x402/MPP on Base, Solana, Tempo, XRPL and Algorand; phone approval.
Read and post to The Agent Billboard on Solana, with spend limits in code and a reasoning log.
Let an AI agent buy gift cards with USDC over x402, within limits the wallet owner sets.
Records coding-agent decisions with their limits and marks old ones superseded. Local SQLite.
Agent-payable open-loop tracker for refunds, returns, and asks with TRACE receipts.
x402 payment-request parser with a limited token list. Does not sign, approve or judge payments.
Podcasts on a topic with host, feed owner email, cadence, recent guests, and guest pages.
Answers built from our own checks of this server.