paypulse
Supports agent-to-agent payments through Binance x402 and provides account and market data via Binance's MCP endpoint.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@paypulseList the available paid services and their prices."
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
PayPulse
Agent-to-agent payments on Binance x402.
The payment rail is HTTP 402 Payment Required → preview → sign → replay → deliver the resource. MCP is account / market-data context, not settle.
Live default. Paper HMAC delivery is opt-in (PAYPULSE_MODE=paper). Live never silently paper-fills.
Dual-rail Agent OS
Rail | Role | What PayPulse actually does |
x402 | Pay for an HTTP resource | Seller returns x402 v2 |
MCP | Account / market data | Probes |
Documented x402 default daily cap: USD20/day (x402DailyLimit). Live quota is read from baw wallet settings when available. Confirm in the Binance App.
Related MCP server: ln-church-agent
Quick start
npm install
npm test
npm run demo:paper # full 402 → HMAC sign → deliver + risk reject
npm run demo # live: honest PENDING + risk reject (no fake fills)
npm run dev # dashboard http://127.0.0.1:5174 (API + /svc on the same port)Copy .env.example to .env if you want to change caps or payTo addresses.
Live buyer (optional)
Install Agentic Wallet CLI:
npm i -g @binance/agentic-walletbaw auth signinthenbaw wallet status --jsonPAYPULSE_MODE=live npm run demo— preview/sign when the wallet is ready; resource stays unpaid until a B402 merchant verifies.
Scripts
Script | Purpose |
| Live smoke: ≥2 A2A attempts + ≥1 over-cap reject |
| Paper smoke: two delivered resources + 1 reject |
| Vite UI + |
| Standalone API on :8787 |
| MCP stdio tools for Claude/Cursor |
| Protocol, risk, paper loop |
|
|
x402 flow
Buyer GET /svc/market-brief
← 402 + PaymentRequired { x402Version: 2, accepts[] }
preview (paper HMAC option, or baw x402-payment preview)
confirm
sign (paper HMAC, or baw x402-payment sign → PAYMENT-SIGNATURE)
replay GET /svc/market-brief + PAYMENT-SIGNATURE
← 200 + body + PAYMENT-RESPONSE.txHash (paper)
← 402 unpaid (live without B402 merchant)Paid resources (in-process and on the dev server):
GET /svc/market-brief— $5 USDTGET /svc/signal-pack— $8 USDCGET /svc/oversize-audit— $25 (risk-rejected)
Sellers have payTo addresses (BSC). Override with PAYPULSE_PAYTO_*.
MCP tools
POST /mcp (dev server) or npm run mcp (stdio):
paypulse_list_servicespaypulse_preview_paymentpaypulse_confirm_paymentpaypulse_ledger
Safety
No Binance API secrets in
.env. MCP auth is OAuth in the host. Wallet sign isbaw.No withdrawals.
Kill-switch and size/daily/live-quota gates run before sign.
Live mode refuses paper HMAC.
See AGENT_OS_NOTES.md, JUDGE.md, DEMO.md.
Disclaimer
Not financial advice. Paper delivery is local. Live on-chain settle needs a signed-in Agentic Wallet and a B402-onboarded merchant to /verify+/settle. The $20/day figure is a documented default, not an SLA.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections. Dates show when Glama detected each change.
No tool schema history has been recorded yet.
This server cannot be installed
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Related MCP Connectors
Discover machine-payable APIs, probe x402 payment terms, and run seller operations. Non-custodial.
Agent x402 Paywall MCP — Coinbase HTTP 402 protocol + on-chain settlement. Agents pay per-call
x402 paywall layer for creator sites and agents: paid content, pricing, reputation, ledger.
Pay-per-call x402 gateway: agent tools, OpenAI-compatible LLM, market data, RPC, security audits.
Related MCP Servers
AlicenseNot gradedqualityBmaintenanceEnables AI agents to autonomously pay for and discover services using HPP USDC.e over the x402 protocol, without API keys or manual signing.148Apache 2.0- AlicenseNot gradedqualityAmaintenanceA buyer-side HTTP 402 runtime and agent-commerce surface inspector for autonomous agents, enabling inspection of paid-action surfaces and execution of payment loops.MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, pay for, and sell HTTP APIs using the x402 micropayment protocol, with USDC settlement on Base mainnet. Includes tools for payment requirements, paying and fetching resources, building seller configurations, and monitoring revenue.4281MIT
- AlicenseNot gradedqualityCmaintenanceEnables AI agents to discover, query, and pay for HTTP endpoints and MCP tools using Stellar USDC/SEP-41 stablecoins through a federated P2P bazaar catalog and x402 payment facilitator.Apache 2.0
Latest Blog Posts
- Who's Calling? MCP Hosts Are an Identity Blind Spot (And the Spec Knows It)By Om-Shree-0709 on .mcpAgent IdentityOAuth 2.1
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/herewegoagain4436-creator/paypulse-binance-agent-os'
If you have feedback or need assistance with the MCP directory API, please join our Discord server