PulseNetwork MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| 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). |
Instructions
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.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
Tools
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. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
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.