← Back to Skills Marketplace
up2itnow

AgentPay MCP

by up2itnow · GitHub ↗ · v1.0.0 · MIT-0
cross-platform ⚠ suspicious
299
Downloads
0
Stars
0
Active Installs
1
Versions
Install in OpenClaw
/install agentpay-mcp
Description
MCP server that gives AI agents the ability to make payments, manage budgets, and handle billing -- directly from Claude Desktop, Cursor, Cline, or any MCP-c...
README (SKILL.md)

AgentPay MCP

Payment layer for AI agents via Model Context Protocol. AgentPay MCP gives your AI agent the ability to make payments, track spending, and manage payment channels -- without leaving the agent runtime.

Works with Claude Desktop, Cursor, Cline, Windsurf, and any MCP-compatible environment.

What It Does

  • Make payments: Send USDC on Polygon directly from agent tool calls
  • Budget management: Hard spending limits enforced per-session and per-day
  • Payment channels: Open Handshake58-style channels for sub-cent micropayments
  • CCTP bridge: Cross-chain USDC settlement (Ethereum, Base, Polygon, Arbitrum)
  • Non-custodial: Agent holds its own keys -- no third-party custody

Installation

npm install -g agentpay-mcp

Add to your MCP config (~/.config/claude/mcp.json or equivalent):

{
  "mcpServers": {
    "agentpay": {
      "command": "agentpay-mcp",
      "env": {
        "AGENT_PRIVATE_KEY": "0x...",
        "RPC_URL": "https://polygon-rpc.com",
        "MAX_TX_USDC": "25",
        "MAX_DAILY_USDC": "500"
      }
    }
  }
}

Tools Exposed

Tool Description
pay Send USDC to an address (enforces spend limits)
check_balance Query agent wallet balance
get_spending Current session and daily spend totals
open_channel Open a micropayment channel (Handshake58 compatible)
pay_channel Issue a signed payment voucher (zero gas)
close_channel Settle and reclaim unused channel funds
bridge_usdc Cross-chain USDC via CCTP

Usage Example

In Claude Desktop with AgentPay MCP configured:

"Pay 5 USDC to 0xABC...123 for the API call results"

The agent calls pay(to="0xABC...123", amount=5, token="USDC"). If within limits, it executes immediately. If over limits, it returns a request for human approval.

Environment Variables

Variable Required Description
AGENT_PRIVATE_KEY Yes Agent's signing key (0x-prefixed)
RPC_URL Yes Polygon JSON-RPC endpoint
MAX_TX_USDC No Per-transaction limit in USDC (default: 25)
MAX_DAILY_USDC No Daily spending limit in USDC (default: 500)

GitHub

https://github.com/AI-Agent-Economy/agentpay-mcp

License

MIT

Usage Guidance
This skill gives an agent the ability to sign and send real cryptocurrency transactions. Before installing: (1) Do not provision your main wallet private key. Prefer a dedicated signing key or a constrained account funded only with a small test balance. (2) Require and verify human approval flows in your agent runtime for any payment above a tiny threshold. (3) Inspect the npm package and GitHub repository the SKILL.md references (pin a specific release/tag and review code) before running npm install -g. (4) Avoid storing private keys in plaintext config files; consider hardware signers or remote signing services that limit scope. (5) If you decide to proceed, set conservative MAX_TX_USDC and MAX_DAILY_USDC env values, run the package in an isolated environment, and audit logs for unexpected activity. Because this skill bundle contains no code to review, you cannot verify what the installed package will do — that uncertainty is the main reason this is flagged as suspicious.
Capability Analysis
Type: OpenClaw Skill Name: agentpay-mcp Version: 1.0.0 The skill facilitates automated USDC payments on the Polygon network and requires a raw AGENT_PRIVATE_KEY in environment variables, which is a high-risk security practice for AI agents. It exposes powerful tools for financial transactions such as 'pay', 'open_channel', and 'bridge_usdc' in SKILL.md. While these capabilities align with the stated purpose of a payment MCP, the requirement for sensitive credentials and the potential for unauthorized fund movement via the external 'agentpay-mcp' npm package makes this skill inherently risky.
Capability Assessment
Purpose & Capability
The skill is a payment/MCP server and therefore legitimately needs a signing key (AGENT_PRIVATE_KEY), an RPC endpoint (RPC_URL), and a Node runtime; those requirements are consistent with the stated functionality. Minor inconsistency: the skill is instruction-only in the registry (no code supplied or install spec), yet the SKILL.md instructs users to npm install -g agentpay-mcp and to modify MCP config files.
Instruction Scope
SKILL.md instructs storing the agent private key and RPC URL in MCP config or environment variables and adding a global npm binary to MCP server config (~/.config/claude/mcp.json). That places long‑lived signing material in a file/env accessible to the agent runtime and any processes that read that config. Because the skill describes autonomous payments, those instructions expand the agent's ability to create and sign transactions without additional checks unless external approvals are enforced.
Install Mechanism
The skill includes an npm install command and a GitHub URL in SKILL.md but provides no install spec or packaged code in the registry for review. There is no pinned release, checksum, or provenance provided in the skill bundle, so the actual code that would be installed cannot be audited from this skill entry alone.
Credentials
Requesting AGENT_PRIVATE_KEY and RPC_URL is proportionate for a payment tool, but AGENT_PRIVATE_KEY is extremely sensitive. The SKILL.md also recommends placing the key in MCP config or env vars — practices that increase exposure. No secondary mitigations (hardware signer, read-only/subkeys, or explicit human-approval gating) are mandated by the instructions.
Persistence & Privilege
The skill does not request always: true and does not claim to modify other skills, which is good. However, agent runtimes typically allow autonomous invocation by default; combined with the ability to sign transactions using a provided private key, autonomous invocation materially increases risk unless the agent runtime enforces explicit human approvals or very strict spend limits.
How to Use
  1. Make sure OpenClaw is installed (local or Docker)
  2. Run the install command in chat: /install agentpay-mcp
  3. After installation, invoke the skill by name or use /agentpay-mcp
  4. Provide required inputs per the skill's parameter spec and get structured output
Version History
v1.0.0
Initial listing: Payment layer for AI agents via Model Context Protocol
Metadata
Slug agentpay-mcp
Version 1.0.0
License MIT-0
All-time Installs 0
Active Installs 0
Total Versions 1
Frequently Asked Questions

What is AgentPay MCP?

MCP server that gives AI agents the ability to make payments, manage budgets, and handle billing -- directly from Claude Desktop, Cursor, Cline, or any MCP-c... It is an AI Agent Skill for Claude Code / OpenClaw, with 299 downloads so far.

How do I install AgentPay MCP?

Run "/install agentpay-mcp" in the OpenClaw or Claude Code chat to install it in one step — no extra setup required.

Is AgentPay MCP free?

Yes, AgentPay MCP is completely free, licensed under MIT-0. You can download, install and use it at no cost.

Which platforms does AgentPay MCP support?

AgentPay MCP is cross-platform and runs anywhere OpenClaw / Claude Code is available (cross-platform).

Who created AgentPay MCP?

It is built and maintained by up2itnow (@up2itnow); the current version is v1.0.0.

💬 Comments