Agentpay

io.github.kar69-96Published by GitHub account kar69-96v0.1.8Updated Oct 24, 2026

AI agent payments with human approval. Local-first, encrypted credentials, budget controls.

The publisher's own server: AgentPay — Pay-per-call AI Microservices

VerifiedSTDIODesktop onlyFinanceBusiness & Commerce

Overview

AI-generated overview

Agentpay is a local MCP server for AI agent payments with human approval, using encrypted credentials and budget controls.

What you can do
Enables an assistant to carry out purchases on the user's behalf, with human approval required before payment execution, according to the registry description. Keeps payment credentials encrypted locally and applies budget controls to spending. Uses an Anthropic API key for browser navigation during checkout. No individual tools are listed in the manifest, so the exact operations are not documented here.
When to use it
Consider it when you want an assistant to handle online checkout or purchasing tasks while keeping credentials local, requiring human sign-off, and enforcing spending limits.
Requirements
Runs as a local process on the user's desktop via the npm package @useagentpay/mcp-server over stdio. Needs the AGENTPAY_PASSPHRASE secret to decrypt credentials during purchase execution and the ANTHROPIC_API_KEY secret for browser navigation during checkout. No authentication is declared.
Before you install
Requires two secrets: AGENTPAY_PASSPHRASE and ANTHROPIC_API_KEY. It can spend real money through purchases, so budget controls and human approval should be verified before use. It handles payment credentials, which are decrypted locally during purchase execution. Desktop only; no web execution.

Installation

In SourceWeft

  1. Open Agentpay 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. v0.1.8LatestSep 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.

Other Agentpay integrations