Click on "Deploy 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., "@PulseNetwork MCP Check if a 5-hour delayed flight from FRA to JFK qualifies for EU261 compensation."
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.
Give your AI agent a wallet and 900+ pay-per-call intelligence APIs.
A local MCP server that connects any MCP host (Cursor, Claude Code, Claude Desktop, …) to PulseNetwork — 74 intelligence verticals covering finance, crypto, health, law, travel, climate, safety, and more. No accounts, no API keys: every endpoint is paid per call in USDC on Base via the x402 protocol.
{ "mcpServers": { "pulsenetwork": { "command": "npx", "args": ["-y", "@pulsenetwork/mcp", "mcp"] } } }Tool | Cost | What it does |
| FREE | Search the full catalog (~900 endpoints) by keyword |
| pays the listed price | Call an endpoint; payment settles automatically |
| FREE | Wallet address + USDC balance |
| FREE | Local spend report |
| FREE | Show active spend caps |
Related MCP server: navi-x402-mcp
On first run the server generates a wallet (standard BIP-39 phrase, imports into
MetaMask/Rabby) and prints the address. Fund it with a few dollars of USDC on Base
and paid calls just work. The recovery phrase is stored at ~/.pulsepay/wallet.json
(file mode 600) — back it up. Prefer your own key? Set PULSEPAY_EVM_KEY and nothing
is written to disk.
Guardrails run in code, before anything is signed — a confused or prompt-injected agent cannot bypass them:
$0.50 per call / $5 per day by default (change in ~/.pulsepay/config.json or via
PULSEPAY_MAX_PER_CALL / PULSEPAY_MAX_PER_DAY)
The model has no tool to raise caps — only you can, by editing the file
The wallet only pays *.theaslangroupllc.com (the PulseNetwork fleet) — nothing else
Prices are checked against the endpoint's live 402 challenge, not a cached catalog
Unpriceable calls are blocked, not waved through (fail-closed)
"Check if a 5-hour delayed flight from FRA to JFK qualifies for EU261 compensation."
"Is this token safe? 0x… on Base — run a safety scan before I ape."
"Any product recalls for 'baby teether' in the EU this year?"
"What's my agent wallet's balance and what did it spend this week?"
Most endpoints cost $0.01–$0.25. The agent discovers for free, quotes the price, and pays only when you ask it to.
MIT © The Aslan Group LLC. Terms: https://pulse.theaslangroupllc.com/terms.html
FREE — the local wallet address and its USDC balance on Base. If the balance is 0, paid calls will fail: give the user the address so they can fund it.
Inputs: no named parameters.
PAID — call a PulseNetwork endpoint, paying its listed price in USDC on Base from the local wallet. Spend caps are enforced in code before signing; if a call is blocked by a guardrail, do NOT retry or attempt to route around it — tell the user. Only *.theaslangroupllc.com hosts are payable. Quote the price to the user before calling when the request is theirs.
Inputs: path (required), vertical (required), params.
FREE — search the PulseNetwork catalog (74 verticals, ~900 endpoints). Returns matching endpoints with price, params, and description. Always discover before calling; prefer the cheapest endpoint that answers the question.
Inputs: limit, query, vertical.
FREE — show the active spend caps. Caps can only be changed by the USER editing the config file (or env vars) — there is deliberately no tool to raise them.
Inputs: no named parameters.
FREE — local spend report from this wallet's ledger.
Inputs: days.
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
Scored across 5 tools
Each tool has a clearly distinct purpose: discovering endpoints, executing paid calls, checking wallet balance, viewing spend reports, and inspecting guardrails. There is no overlap or ambiguity between them.
All tools share the 'pulse_' prefix, creating a recognizable pattern, but the suffixes mix verbs (call, discover) and nouns (report, guardrail, balance). The inconsistency is minor and does not impede comprehension.
With 5 tools, the set is well-scoped for its purpose: a paid API gateway needs discovery, execution, balance, reporting, and safety checks. Every tool earns its place.
The toolset covers the full user workflow: discover an endpoint, check price and balance, call it, monitor spend via report, and verify caps. The deliberate absence of a guardrail-raising tool is a security feature, not a gap.
Market data and web intelligence for AI agents, paid per call in USDC on Base via x402.
30 pay-per-call APIs for AI agents: compliance, trade, safety, web, data. USDC on Base via x402.
17 pay-per-call web, finance, legal and onchain tools for AI agents. USDC on Base via x402/MPP.
Pay-per-call data APIs for AI agents. USDC on Base via x402. 33 tools, no signup.