AgentPays

dev.agentpaysPublished by agentpays.devOfficial publisherv1.0.0Updated Oct 24, 2026

Payment infrastructure for AI agents: spending rules, approval flows, single-use virtual cards.

VerifiedStreamable HTTPWeb executableFinanceBusiness & Commerce

Overview

AI-generated overview

Lets an assistant manage agent payment infrastructure: spending rules, approval flows, and single-use virtual cards.

What you can do
AgentPays is a remote MCP endpoint that provides payment infrastructure for AI agents. According to its registry description, it covers spending rules, approval flows, and single-use virtual cards, so an assistant can work with payment controls and card issuance through the server's tools. No tool list is published in the manifest, so the exact operations are not documented here.
When to use it
Consider it when an assistant needs to make or control payments on behalf of a user, for example enforcing spending limits, routing purchases through approvals, or issuing single-use virtual cards. It is not useful for assistants that never handle money.
Requirements
A remote streamable HTTP endpoint at agentpays.dev; nothing is installed locally. Authentication is either an Authorization header carrying a Bearer token with an agent API key, or OAuth, which Claude Desktop, Claude.ai, and ChatGPT handle automatically. Network access is required.
Before you install
This server deals with payments and card issuance, so an assistant could spend money or create payment instruments. The Authorization header carries a secret agent API key; treat it as sensitive and prefer OAuth where available. Review spending rules and approval flows before granting access, and confirm what payment data is sent to the third-party service.

Installation

In SourceWeft

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

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.agentpays%2Fagentpays/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "agentpays": {
      "type": "http",
      "url": "https://agentpays.dev/api/mcp"
    }
  }
}

Tools

0
SourceWeft has not read this server's tools yet.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

28% 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 daysRequired25 pts

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

  • Auth declaredRequired10 pts
  • Tools listed15 pts

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

  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

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

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.