Skip to content

SafePay Check MCP server

com.agentposhq.safepay/checksafepay.agentposhq.comstreamable-httpv0.8.1Scanned

Judges a payment (PayPal, PYUSD or USDC) before an AI agent makes it. Signed proof. Moves no money.

5 tools: 1 do something that can't be undone, 1 change things and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here does something that can't be undone. Govern it.

  • 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 SafePay Check MCP server can do

The SafePay Check MCP server is published by safepay.agentposhq.com, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (safepay_check_payment) and create or change data (1 tool: safepay_verify), but cannot delete data. 3 tools only read.

2 tools bring in text other people can write (safepay_check_payment and safepay_verify_settlement).

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

Its remote endpoint lists its tools without sign-in, and its tools changed once since Anlyon Radar first saw them.

Last scanned Nov 8, 2026, version 0.8.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.

5 tools

Can't be undone 1Claude Code: ask
  • safepay_check_paymentChecks a planned payment before it is made.Reads text others writeNo findings

    Why it is in this group

    • The name "safepay_check_payment" says "payment": a word that usually means money moves, which cannot be taken back.
    • The input carries an amount (input.amount) and a currency, so it moves money.

    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
    Checks a planned payment before it is made. Judges the merchant, amount and task against the account's payment rules, the payee's payment history, a live web check of the merchant and an intent check, and returns allow, hold or block with the reasons, a check id and a signed attestation valid for 15 minutes. Moves no money and stores no payee address or task text, only their hashes.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: true
    • readOnlyHint: false
    • title: Check a payment before paying
Changes things 1Claude Code: ask
  • safepay_verifyVerifies a SafePay seal id (SP-XXXXXXXXXX), a signed receipt or a precheck attestation against SafePay's published Ed25519 key.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
    Verifies a SafePay seal id (SP-XXXXXXXXXX), a signed receipt or a precheck attestation against SafePay's published Ed25519 key. Returns whether it is genuine and intact, and what it states.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Verify a SafePay seal or attestation
Only reads 3Show 3 read-only tools
  • safepay_policyReturns the payment rules this account is judged under, in plain words, with their fingerprint.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns the payment rules this account is judged under, in plain words, with their fingerprint.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Show the payment rules
  • safepay_recent_checksReturns this account's latest payment checks: verdict, merchant, amount and time.No findings

    Why it is in this group

    • The description's first verb is "return": a word for reading.
    Description, as the server wrote it
    Returns this account's latest payment checks: verdict, merchant, amount and time.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false
    • readOnlyHint: true
    • title: Recent checks
  • safepay_verify_settlementReads a Stellar transaction from the public ledger (Horizon) and compares it with a SafePay precheck attestation: whether it succeeded, paid the approved payee, in Circle's USDC, n…Reads text others writeNo findings

    Why it is in this group

    • The description's first verb is "read": a word for reading.

    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
    Reads a Stellar transaction from the public ledger (Horizon) and compares it with a SafePay precheck attestation: whether it succeeded, paid the approved payee, in Circle's USDC, no more than the approved amount, while the check was valid. Returns the findings and a signed result. Reads the ledger only.

    Annotations the server declares

    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
    • readOnlyHint: true
    • title: Check a stablecoin settlement

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 write2
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.

Tools listed without sign-in

Looked at Nov 15, 2026, 13:20 UTC, unchanged since Nov 8, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
2
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • HighThe whole server

    The endpoint served tools/list without credentials, and the list has 2 tools that change things (1 irreversible, 1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://safepay.agentposhq.com/mcp: tools/list returned 5 tools to an anonymous client, including safepay_check_payment (irreversible), safepay_verify (write)

    What this check looks for

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.

  1. Tools1 added.+1 addedView diff

Install

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

claude mcp add --transport http check https://safepay.agentposhq.com/mcp --header 'Authorization: <your-authorization>'
claude mcp add --transport http check https://safepay.agentposhq.com/mcp --header 'Authorization: <your-authorization>'

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__check__safepay_verify_settlement",
      "mcp__check__safepay_policy",
      "mcp__check__safepay_recent_checks"
    ],
    "ask": [
      "mcp__check__safepay_check_payment",
      "mcp__check__safepay_verify"
    ],
    "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 check. Review it before you use it.

Capability tags behind 2 rules
  • mcp__check__safepay_check_payment untrusted-input
  • mcp__check__safepay_verify_settlement 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.agentposhq.safepay/check/verify?hash=9648bf600923d4669080a086b659ba2b98fb943b91acc6e159356e84e0d15df9" | jq -e '.changed == false'

Pinned hash 9648bf600923, from Nov 8, 2026, 04:17 UTC.

Watch

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

https://radar.anlyon.com/servers/com.agentposhq.safepay/check/changes.xml

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

Badge

Anlyon Radar badge for com.agentposhq.safepay/check
[![Anlyon Radar](https://radar.anlyon.com/badge/com.agentposhq.safepay/check.svg)](https://radar.anlyon.com/servers/com.agentposhq.safepay/check)

Source: MCP Registry · repository. Synced Nov 8, 2026, 04:17 UTC.

SafePay Check MCP server: questions and answers

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

Is the SafePay Check MCP server safe?

No scan can promise that. What its definitions show: 5 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 SafePay Check MCP server delete data?

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

Can the SafePay Check MCP server do things that cannot be undone?

Yes. 1 tool can send, pay, publish or merge: safepay_check_payment.

What tools does the SafePay Check MCP server have?

5 tools: 1 irreversible, 1 write, 3 read. safepay_check_payment, safepay_verify, safepay_verify_settlement, safepay_policy and safepay_recent_checks.

Does the SafePay Check MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the SafePay Check MCP server send data to outside services?

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

Has the SafePay Check MCP server changed its tools?

Yes, once since Anlyon Radar started tracking it, most recently on Nov 8, 2026. Every change is on this page and in its Atom feed.