Schema | PulseNetwork MCP

PulseNetwork MCP

Describes the environment variables required to run the server.

Name	Required	Description
`PULSEPAY_EVM_KEY`	No	Your own EVM private key. If set, no wallet file is written to disk.
`PULSEPAY_MAX_PER_DAY`	No	Maximum spend per day in USD (default: $5).
`PULSEPAY_MAX_PER_CALL`	No	Maximum spend per call in USD (default: $0.50).

Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.

This server publishes no instructions, or was last inspected before Glama recorded them.

Features and capabilities supported by this server

Protocol revision2025-11-25

Capability	Details
`tools`	{ "listChanged": true }

Functions exposed to the LLM to take actions

Name	Description
pulse_discoverA	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.
pulse_callA	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.
pulse_balanceA	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.
pulse_reportB	FREE — local spend report from this wallet's ledger.
pulse_guardrailA	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.

Interactive templates invoked by user choice

Name	Description
No prompts

Contextual data attached and managed by the client

Name	Description
No resources