Agent Pay

io.github.joepangalloPublished by GitHub account joepangallov1.1.2Updated Oct 30, 2026

Payment gateway for AI agents with tool discovery, provisioning, metering, and reliability tools.

VerifiedSTDIODesktop onlyFinanceDeveloper Tools

Overview

AI-generated overview

Local MCP server that connects an AI assistant to an AgentPay payment gateway for tool discovery, provisioning, metering and reliability checks.

What you can do
  • Discover and provision tools through the AgentPay payment gateway
  • Meter usage and handle payment-related gateway operations
  • Inspect reliability endpoints such as circuit breakers, health metrics and configuration
  • Run locally over stdio as an npm package
When to use it
Useful when an assistant needs to reach an AgentPay gateway to discover, provision or meter paid tools, or to check gateway health and circuit-breaker state. Not needed if you do not use AgentPay.
Requirements
Runs as a local process via the npm package mcp-server-agentpay over stdio, on desktop only. Requires an AgentPay gateway key in AGENTPAY_GATEWAY_KEY; the optional AGENTPAY_ADMIN_KEY unlocks reliability endpoints. AGENTPAY_URL sets the API endpoint.
Before you install
Two secrets are involved: AGENTPAY_GATEWAY_KEY (required) and AGENTPAY_ADMIN_KEY, which grants access to configuration and reliability controls. The server is tied to a payment gateway, so provisioning and metering may involve real charges; confirm spending limits before use. No tools are listed in the manifest, so review what it can do before enabling.

Installation

In SourceWeft

  1. Open Agent Pay in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

This repository has no README.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v1.1.2LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.