Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AgentPay

NPM · @AGENTPAYXYZ/MCP-SERVER · 2 COMPONENTS · SCANNED SEP 20

Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits.

Available components

remote · api.agentpay.so 32 npm · @agentpayxyz/mcp-server 36
0 this week 36 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 31 of 95 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency35
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
  • License check failed: the license (BSL-1.1; AGPL-3.0 after 2029-01-01) isn't a recognized OSI-approved license. See how to fix → Fail
  • Actively maintained (last published 11 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar) that our sandbox does not supply, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

Install

How do I install the AgentPay MCP server?

AgentPay runs locally as an npm package, launched with npx -y @agentpayxyz/mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · @agentpayxyz/mcp-server

# add to Claude Code
claude mcp add rumblingb-agentpay -- npx -y @agentpayxyz/mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "rumblingb-agentpay": {
      "command": "npx",
      "args": [
        "-y",
        "@agentpayxyz/mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "rumblingb-agentpay": {
      "command": "npx",
      "args": [
        "-y",
        "@agentpayxyz/mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add rumblingb-agentpay -- npx -y @agentpayxyz/mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "rumblingb-agentpay": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@agentpayxyz/mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add rumblingb-agentpay --command npx --arg -y --arg @agentpayxyz/mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  rumblingb-agentpay:
    command: "npx"
    args: ["-y", "@agentpayxyz/mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "rumblingb-agentpay": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@agentpayxyz/mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add rumblingb-agentpay -t stdio -c npx -a -y @agentpayxyz/mcp-server
// mcp.json
{
  "mcpServers": {
    "rumblingb-agentpay": {
      "command": "npx",
      "args": [
        "-y",
        "@agentpayxyz/mcp-server"
      ]
    }
  }
}
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 28 Aug 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 27 Aug 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 13 Aug 26 0
    • Security disclosure: unverified → pass ▲ functional
  • 12 Aug 26 0
    • Security disclosure: pass → unverified ▼ functional
  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • Known CVEs: partial → pass ▲ security
    • Security disclosure: fail → pass ▲ functional
    • Dependency health: partial → 0.85 functional
  • 5 Aug 26 0
    • CVE-2026-69207 no longer affects this package ▲ security
    • Known CVEs: fail → partial ▲ security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 20 Sept 2026 · Analysed npm/@agentpayxyz/mcp-server@0.2.0

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 95 packages
Packages resolved 95
Stale 31
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Common questions

What is the AgentPay MCP server?

AgentPay is an MCP server listed in the public MCP registry as io.github.Rumblingb/agentpay. Agent payments, API key vaulting, and governed mandates. Agents spend within user-defined limits. This page covers its npm package (@agentpayxyz/mcp-server).

Is the AgentPay MCP server safe to use?

AgentPay scores 36 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 20 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

Is the AgentPay MCP server still maintained?

AgentPay is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.