Skip to content

AgentPay MCP server

com.myuiaf/agentpaymyuiaf.comstreamable-httpv1.0.1Scanned

Let agents pay for third-party APIs per call from one prepaid wallet. Charged only on success.

4 tools: 2 change things and 2 only read.

Tools: 0 delete, 0 irreversible, 2 write, 2 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Sign-in required, OAuth metadata published. Remote posture

With Anlyon

2 tools here change things. Govern them.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the AgentPay MCP server can do

The AgentPay MCP server is published by myuiaf.com, a domain the MCP Registry verified. It has 4 tools. It can create or change data (2 tools: call_route and wallet_balance), but cannot delete data. 2 tools only read.

1 tool brings in text other people can write (call_route).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint asks for sign-in and publishes OAuth metadata.

Last scanned Nov 8, 2026, version 1.0.1.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

4 tools

Changes things 2Claude Code: ask
  • call_routeCall a paid API through AgentPay.Reads text others writeNo findings

    Why it is in this group

    • The name "call_route" says "call": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    Call a paid API through AgentPay. Spends the route's price from the prepaid wallet, but only if the API answers 2xx within the route's time limit; errors, timeouts and retries with the same idempotency_key are free. The API's own key is added by AgentPay and never shown to the agent.

    Annotations the server declares

    • title: Call a paid API
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
  • wallet_balanceThe prepaid wallet balance shared by Freshness Validator, AgentPay and AgentCache, and how much is held for calls in progress.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    The prepaid wallet balance shared by Freshness Validator, AgentPay and AgentCache, and how much is held for calls in progress. Free.

    Annotations the server declares

    • title: Check wallet balance
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
Only reads 2Show 2 read-only tools
  • list_routesList the paid APIs (routes) this agent can call through AgentPay, with each route's price per successful call and time limit.No findings

    Why it is in this group

    • The name "list_routes" says "list": a word for reading.
    Description, as the server wrote it
    List the paid APIs (routes) this agent can call through AgentPay, with each route's price per successful call and time limit. Free.

    Annotations the server declares

    • title: List paid APIs
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
  • list_transactionsRecent AgentPay calls (and AgentCache hits) with status, price charged and timing, newest first.No findings

    Why it is in this group

    • The name "list_transactions" says "list": a word for reading.
    Description, as the server wrote it
    Recent AgentPay calls (and AgentCache hits) with status, price charged and timing, newest first. Free.

    Annotations the server declares

    • title: List recent calls
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Sign-in required, OAuth metadata published

Looked at Nov 16, 2026, 14:20 UTC, unchanged since Nov 9, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
401
tools/list served without credentials
no
Tools that change things, listed without credentials
0
Protocol version
not observed
WWW-Authenticate on 401
yes
resource_metadata in WWW-Authenticate
https://agentpay.myuiaf.com/.well-known/oauth-protected-resource/mcp
RFC 9728 protected resource metadata
https://agentpay.myuiaf.com/.well-known/oauth-protected-resource/mcp
Authorization servers
https://api.myuiaf.com
Legacy HTTP+SSE transport
no
Dynamic client registration
yes
Client ID metadata documents
yes

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 1.0.1. Values in angle brackets are yours to fill in.

claude mcp add --transport http agentpay https://agentpay.myuiaf.com/mcp
claude mcp add --transport http agentpay https://agentpay.myuiaf.com/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__agentpay__list_routes",
      "mcp__agentpay__list_transactions"
    ],
    "ask": [
      "mcp__agentpay__call_route",
      "mcp__agentpay__wallet_balance"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as agentpay. Review it before you use it.

Capability tags behind 1 rule
  • mcp__agentpay__call_route untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.myuiaf/agentpay/verify?hash=455e86be9691da35fd272326af5e06f4e2a6527ff6be9cafc5f06431b59b116c" | jq -e '.changed == false'

Pinned hash 455e86be9691, from Nov 8, 2026, 08:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.myuiaf/agentpay/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.myuiaf/agentpay
[![Anlyon Radar](https://radar.anlyon.com/badge/com.myuiaf/agentpay.svg)](https://radar.anlyon.com/servers/com.myuiaf/agentpay)

Source: MCP Registry. Synced Nov 13, 2026, 01:17 UTC.

AgentPay MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the AgentPay MCP server safe?

No scan can promise that. What its definitions show: 4 tools, 2 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the AgentPay MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the AgentPay MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the AgentPay MCP server have?

4 tools: 2 write, 2 read. call_route, wallet_balance, list_routes and list_transactions.

Does the AgentPay MCP server need sign-in or OAuth?

Yes. Its remote endpoint answered 401 without credentials, and it publishes OAuth protected resource metadata (RFC 9728); its authorization server supports dynamic client registration.

Does the AgentPay MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the AgentPay MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 8, 2026.