Check Payment Recipient

dev.kgninjaPublished by kgninja.devv0.2.0Updated Nov 7, 2026

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

The publisher's own server: check.tattoo: tattoo size and placement guide

VerifiedStreamable HTTPWeb executableFinanceSecurity & Monitoring

Overview

AI-generated overview

Remote MCP server that lets an assistant screen a planned crypto payment recipient before signing, returning allow, escalate or block with reasons and a…

What you can do
  • Check service health and discover pricing, supported networks, rule set and list coverage
  • Run a paid pre-signing safety check on a planned payment recipient and get allow, escalate or block with reasons, evidence and a verifiable receipt
  • Run a paid batch of 1 to 20 payment checks in one call, with per-item decisions and a summary count
  • Fetch a stored receipt by receipt id or idempotency key to reconcile an uncertain payment before paying again
When to use it
Use it when an assistant is about to sign or send a payment and you want an automated risk decision first, or when you need to reconcile a payment whose outcome was unclear before retrying.
Requirements
A remote streamable HTTP endpoint; no account, API key or header is declared. Paid tools require an x402 payment of $0.05 per check or $0.50 per batch, so a wallet or payment-capable client is needed. Network access to the hosted endpoint.
Before you install
The check and batch tools cost money per call ($0.05 and $0.50) and are paid through x402, so an assistant can spend funds. Decisions are advisory allow/escalate/block results, not a guarantee. On an uncertain outcome, reuse the same idempotency key rather than paying again. Payment details sent for checking go to a third-party hosted service.

Installation

In SourceWeft

  1. Open Check Payment Recipient 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.kgninja%2Fcheck-payment-recipient/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": {
    "check-payment-recipient": {
      "type": "http",
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}

Tools

5

ping

Free health check.

Takes no parameters.

list_capabilities

Free discovery: price, networks, rule set and list coverage for check_payment_recipient.

Takes no parameters.

get_receipt

Free: fetch a stored receipt by receipt_id or idempotency_key. Use it to reconcile an uncertain payment before ever paying again.

Parametersreceipt_ididempotency_key

check_payment_recipient

Paid ($0.05, x402 v2 exact): pre-signing safety check of a planned payment. Returns allow / escalate / block with reasons, evidence and a verifiable receipt. Input errors are returned before payment and are never charged. On an uncertain outcome, reuse the same idempotency_key; a replay returns the stored receipt without a new payment.

Parametersassetrequiredamountrequirednetworkrequiredpurposerequested_atrequiredcounterparty_ididempotency_keyrequiredrecipient_addressrequired

check_payment_batch

Paid ($0.50, x402 v2 exact): batch pre-signing safety check — 1 to 20 payment checks in ONE paid call. Each item takes exactly the same fields as check_payment_recipient and gets its own decision; the result carries per-item decisions plus a summary {total, allow, escalate, block, input_error}. An item with invalid fields is reported per item as INPUT_ERROR and does not fail the batch. Envelope errors (missing batch idempotency_key, items not an array of 1-20) are returned before payment and are never charged. On an uncertain outcome, reuse the same batch idempotency_key; a replay returns the stored result without a new payment.

Parametersitemsrequiredidempotency_keyrequired

Version history

2
  1. v0.2.0LatestNov 7, 2026
  2. v0.1.0Nov 6, 2026

Score

72% 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
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • 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.

Other Check integrations