mcpdirectory.dev
9,129 servers · updated 23 Sept

Lp Copilot MCP server

community Active last commit 42 d
{
  "mcpServers": {
    "pulsenetwork": {
      "command": "npx",
      "args": [
        "-y",
        "@pulsenetwork/lp-copilot-mcp@latest",
        "mcp"
      ],
      "env": {
        "PULSEPAY_EVM_KEY": "<pulsepay_evm_key>"
      }
    }
  }
}
file .mcp.json (in your project root)install npx -y @pulsenetwork/lp-copilot-mcpversion 0.1.1

What it does

An MCP server that connects AI agents to PulseNetwork, a pay-per-call API catalog of ~900 endpoints across finance, crypto, health, law, travel, and climate. It includes a zero-config wallet on Base that auto-settles USDC payments with built-in spend guardrails enforced client-side.

  • Query APIs across multiple domains (finance, health, safety, travel) without managing API keys or accounts.
  • Check flight delay compensation eligibility, token safety, or product recalls by calling relevant endpoints with automatic payment.
  • Monitor agent spending with built-in balance checks and spend reports while enforcing per-call and daily spend limits.

Tools this server exposes

ToolDoes
pulse_discoverSearch the catalog of ~900 endpoints by keyword to find relevant APIs.
pulse_callCall an endpoint; payment in USDC on Base settles automatically via the x402 protocol.
pulse_balanceDisplay the agent wallet address and current USDC balance on Base.
pulse_reportShow a local spend report of API calls made and costs incurred.
pulse_guardrailDisplay active spend caps (per-call and per-day limits).

Before you enable it

An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.