Skip to content

check-payment-recipient MCP server

dev.kgninja/check-payment-recipientkgninja.devstreamable-httpv0.2.0Scanned

Payment safety check for AI agents before signing. $0.05 per check; $0.50 batch (20). Via x402.

5 tools: 2 do something that can't be undone and 3 only read.

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

Tools listed without sign-in. Remote posture

With Anlyon

2 tools here do something that can't be undone. 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 check-payment-recipient MCP server can do

The check-payment-recipient MCP server is published by kgninja.dev, a domain the MCP Registry verified. It has 5 tools. It can do things that cannot be undone, such as sending, paying or publishing (check_payment_recipient and check_payment_batch), but cannot delete data. 3 tools only read.

None of its tools reads private data, brings in text other people write, or sends data out.

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 2 times since Anlyon Radar first saw them.

Last scanned Nov 21, 2026, version 0.2.0.

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 2Claude Code: ask
  • check_payment_batchPaid ($0.50, x402 v2 exact).No findings

    Why it is in this group

    • The name "check_payment_batch" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Paid ($0.50, x402 v2 exact). Checks 1-20 items in one call and returns per-item results and a summary. Invalid batch requests (malformed body, missing or invalid batch idempotency_key, or items other than an array of 1-20 entries) are refused before payment and incur no charge. An invalid item in an otherwise valid paid batch returns INPUT_ERROR as part of the paid result. The batch price still applies. Checks require EVM-format recipient addresses. XNO on nano:mainnet can pay for checks where enabled. A Nano-format recipient returns INPUT_ERROR before payment in a single check, or as an item error in a paid batch. Replay the same request with the same batch idempotency_key to retrieve the stored result without a new payment.
  • check_payment_recipientPaid ($0.05, x402 v2 exact).No findings

    Why it is in this group

    • The name "check_payment_recipient" says "payment": a word that usually means money moves, which cannot be taken back.
    Description, as the server wrote it
    Paid ($0.05, x402 v2 exact). Returns allow / escalate / block with reasons, evidence and a verifiable receipt. Single-check validation errors return INPUT_ERROR before payment and incur no charge. Checks require EVM-format recipient addresses. XNO on nano:mainnet can pay for checks where enabled. A Nano-format recipient returns INPUT_ERROR before payment in a single check, or as an item error in a paid batch. Replay the same request with the same idempotency_key to retrieve the stored receipt without a new payment.
Only reads 3Show 3 read-only tools
  • get_receiptFree: fetch a stored receipt by receipt_id or idempotency_key.No findings

    Why it is in this group

    • The name "get_receipt" says "get": a word for reading.
    Description, as the server wrote it
    Free: fetch a stored receipt by receipt_id or idempotency_key. Use it to reconcile an uncertain payment before ever paying again.
  • list_capabilitiesFree discovery: price, networks, rule set and list coverage for check_payment_recipient.No findings

    Why it is in this group

    • The name "list_capabilities" says "list": a word for reading.
    Description, as the server wrote it
    Free discovery: price, networks, rule set and list coverage for check_payment_recipient.
  • pingFree health check.No findings

    Why it is in this group

    • The name "ping" says "ping": a word for reading.
    Description, as the server wrote it
    Free health check.

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 untrusted-input or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write0
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 21, 2026, 19:22 UTC, unchanged since Nov 14, 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 (2 irreversible). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://check-payment-recipient.fuwafuwow.workers.dev/mcp: tools/list returned 5 tools to an anonymous client, including check_payment_recipient (irreversible), check_payment_batch (irreversible)

    What this check looks for

Posture changes

  1. Nov 14, 2026
    • Tools that change things, listed without credentials: 1 to 2

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. Tools2 changed.~2 changedView diff
  2. PostureRemote posture changed. Tools that change things, listed without credentials: 1 -> 2.View diff
    • Tools that change things, listed without credentials: 1 to 2
  3. Tools1 added.+1 addedView diff

Install

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

claude mcp add --transport http check-payment-recipient https://check-payment-recipient.fuwafuwow.workers.dev/mcp
claude mcp add --transport http check-payment-recipient https://check-payment-recipient.fuwafuwow.workers.dev/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__check-payment-recipient__ping",
      "mcp__check-payment-recipient__list_capabilities",
      "mcp__check-payment-recipient__get_receipt"
    ],
    "ask": [
      "mcp__check-payment-recipient__check_payment_recipient",
      "mcp__check-payment-recipient__check_payment_batch"
    ],
    "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-payment-recipient. Review it before you use it.

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/dev.kgninja/check-payment-recipient/verify?hash=666e9cb070ae4f0942f1f550e23f0396656f2732508552ea46264fee9395931f" | jq -e '.changed == false'

Pinned hash 666e9cb070ae, from Nov 21, 2026, 11:17 UTC.

Watch

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

https://radar.anlyon.com/servers/dev.kgninja/check-payment-recipient/changes.xml

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

Badge

Anlyon Radar badge for dev.kgninja/check-payment-recipient
[![Anlyon Radar](https://radar.anlyon.com/badge/dev.kgninja/check-payment-recipient.svg)](https://radar.anlyon.com/servers/dev.kgninja/check-payment-recipient)

Source: MCP Registry. Synced Nov 7, 2026, 06:17 UTC.

check-payment-recipient MCP server: questions and answers

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

Is the check-payment-recipient 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 check-payment-recipient MCP server delete data?

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

Can the check-payment-recipient MCP server do things that cannot be undone?

Yes. 2 tools can send, pay, publish or merge: check_payment_recipient and check_payment_batch.

What tools does the check-payment-recipient MCP server have?

5 tools: 2 irreversible, 3 read. check_payment_recipient, check_payment_batch, ping, list_capabilities and get_receipt.

Does the check-payment-recipient MCP server need sign-in or OAuth?

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

Does the check-payment-recipient MCP server send data to outside services?

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

Has the check-payment-recipient MCP server changed its tools?

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