# dev.kgninja/check-payment-recipient (remote · check-payment-recipient.fuwafuwow.workers.dev)

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

- Trust score: 62/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `check-payment-recipient.fuwafuwow.workers.dev`: 62/100 (this document), [markdown](https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient.md), [page](https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient)

## Channel facts

- Endpoint: `https://check-payment-recipient.fuwafuwow.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 5 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 402, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (fair).
  - Tool/resource definitions use about 468 tokens (~93/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 50/100
  - Stability observed for 15 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 69/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 8% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the dev.kgninja/check-payment-recipient MCP server?

dev.kgninja/check-payment-recipient is a hosted endpoint at https://check-payment-recipient.fuwafuwow.workers.dev/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http dev-kgninja-check-payment-recipient 'https://check-payment-recipient.fuwafuwow.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-kgninja-check-payment-recipient": {
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-kgninja-check-payment-recipient": {
      "type": "http",
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-kgninja-check-payment-recipient]
url = "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-kgninja-check-payment-recipient": {
      "type": "remote",
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-kgninja-check-payment-recipient --url 'https://check-payment-recipient.fuwafuwow.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-kgninja-check-payment-recipient:
    url: "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-kgninja-check-payment-recipient": {
      "Transport": "http",
      "Url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-kgninja-check-payment-recipient -t streamable-http -u 'https://check-payment-recipient.fuwafuwow.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-kgninja-check-payment-recipient": {
      "type": "http",
      "url": "https://check-payment-recipient.fuwafuwow.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 62, +1)

No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-19 (score 61, +1)

- [security] Tool “check_payment_batch” rewrote its description, which is the text the model reads
- [security] Tool “check_payment_recipient” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 82 → 93

### 2026-11-17 (score 60, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-14 (score 59, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-12 (score 58, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-10 (score 57, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-08 (score 56, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-07 (score 55, 0)

- [functional regression] Schema quality: 61 → 82
- [functional improvement] Stability: unverified → 0.03
- [functional] New tool “check_payment_batch”

## MCP tools (5)

### `ping` (~11 tokens)

Free health check.

### `list_capabilities` (~27 tokens)

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

### `get_receipt` (~54 tokens)

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

Input parameters:

- `idempotency_key` (string)
- `receipt_id` (string)

### `check_payment_recipient` (~188 tokens)

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.

Input parameters:

- `amount` (string, required): Decimal string, never a float.
- `asset` (string, required)
- `counterparty_id` (string)
- `idempotency_key` (string, required)
- `network` (string, required)
- `purpose` (string)
- `recipient_address` (string, required)
- `requested_at` (string, required)

### `check_payment_batch` (~188 tokens)

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.

Input parameters:

- `idempotency_key` (string, required)
- `items` (array, required)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient#diagnostics

## Score history

- 2026-11-21: 62
- 2026-11-20: 61
- 2026-11-19: 61
- 2026-11-18: 60
- 2026-11-17: 60
- 2026-11-16: 59
- 2026-11-15: 59
- 2026-11-14: 59
- 2026-11-13: 58
- 2026-11-12: 58
- 2026-11-11: 57
- 2026-11-10: 57
- 2026-11-09: 56
- 2026-11-08: 56
- 2026-11-07: 55
- 2026-11-06: 55

## Common questions

### What is the dev.kgninja/check-payment-recipient MCP server?

dev.kgninja/check-payment-recipient is an MCP server listed in the public MCP registry as dev.kgninja/check-payment-recipient. Payment safety check for AI agents before signing. $0.05 per check; $0.50 batch (20). Via x402. This page covers its hosted endpoint (https://check-payment-recipient.fuwafuwow.workers.dev/mcp).

### Is the dev.kgninja/check-payment-recipient MCP server safe to use?

dev.kgninja/check-payment-recipient scores 62 out of 100 on VerifyMCP. 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.

### What tools does the dev.kgninja/check-payment-recipient MCP server expose?

dev.kgninja/check-payment-recipient exposes 5 tools: ping, list_capabilities, get_receipt, check_payment_recipient, check_payment_batch. Their descriptions and schemas cost roughly 468 tokens of context every time the server is loaded.

### Does the dev.kgninja/check-payment-recipient MCP server require authentication?

No. We connected to dev.kgninja/check-payment-recipient without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the dev.kgninja/check-payment-recipient MCP server still maintained?

dev.kgninja/check-payment-recipient is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the dev.kgninja/check-payment-recipient MCP server?

VerifyMCP ran 11 checks on dev.kgninja/check-payment-recipient, covering TLS certificate, HSTS header, DNSSEC, Transport and 7 more. 2 items could not be completed, a gap on our side rather than a finding about dev.kgninja/check-payment-recipient: Authorization and HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://check-payment-recipient.fuwafuwow.workers.dev/mcp
- Changelog RSS feed: https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient.json
- HTML version of this page: https://verifymcp.io/servers/dev-kgninja-check-payment-recipient/check-payment-recipient
