Is the Kgninja Check Payment Recipient MCP server down?

mcp-registry/dev.kgninja/check-payment-recipient · registry v0.2.0 · server reports v0.1.0

One MCP connection for every live tool. Your agent finds the right tool and calls it through Glimind, and skips servers that are down. Free, no signup.Add to CursorVS CodeAdd to Claude Code copies a terminal command claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server. Other clients
healthy
Last checked 2026-11-22 19:03 UTC · handshake 475ms

As of 2026-11-22 19:03 UTC, the Kgninja Check Payment Recipient MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

uptime (30d checks)
100%
checks observed
908
outages (90d)
0
tools
5

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

Point your MCP client at this streamable-http endpoint: https://check-payment-recipient.fuwafuwow.workers.dev/mcp

Agent-readiness: C (71/100)

C (71/100): 0 error(s), 3 warning(s) across 5 tool(s); ~803 tokens of tool definitions.
Scores higher than 4% of 27,664 MCP servers Glimind has audited.
Its tool list costs an agent ~803 tokens per session — lighter than 75% of servers.
71 → 71 since 2026-11-16
no tool-poisoning patterns
Descriptions28
Safety hints30
Schemas100
Protocol100
Stability100
Token cost100
Reliability100
Client compatibility70

What to fix (4)

5 of 5 tool(s) carry no readOnlyHint/destructiveHint annotations.

Annotate read-only tools with {"readOnlyHint": true}. Agents and gateways can then run them without a confirmation prompt, and route around destructive ones. How to fix →

Tools: check_payment_batch, check_payment_recipient, get_receipt, list_capabilities, ping

11 parameter(s) across 3 tool(s) have no description.

Add a "description" to each parameter with its format and an example ("ISO 8601 date, e.g. 2026-10-17"). This is the commonest cause of wrong arguments on the first call. How to fix →

Tools: check_payment_batch, check_payment_recipient, get_receipt

1 tool(s) have descriptions under 20 characters.

Say when to use the tool and what it returns, not just its name restated ("Get weather" → "Current weather for a city: temperature, conditions, wind. Use for 'now', not forecasts."). How to fix →

Tools: ping

No tool declares an outputSchema.

Declare outputSchema and return structuredContent (MCP 2025-06-18+). Agents can then parse results without guessing, and chain tools reliably. How to fix →

Auto-fix: 5 corrected tool definitions

Paste-ready definitions with the problems above fixed. Changes marked verify need a human look. 3 tool(s) still need parameter descriptions written by someone who knows the API. All of them as JSON: /v1/readiness/mcp-registry%2Fdev.kgninja%2Fcheck-payment-recipient/fixes

check_payment_batch 1 change
{
  "name": "check_payment_batch",
  "description": "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 e",
  "inputSchema": {
    "type": "object",
    "required": [
      "items",
      "idempotency_key"
    ],
    "properties": {
      "items": {
        "type": "array",
        "items": {
          "type": "object",
          "required": [
            "recipient_address",
            "amount",
            "asset",
            "network",
            "idempotency_key",
            "requested_at"
          ],
          "properties": {
            "asset": {
              "type": "string"
            },
            "amount": {
              "type": "string",
              "description": "Decimal string, never a float."
            },
            "network": {
              "type": "string"
            },
            "purpose": {
              "type": "string"
            },
            "requested_at": {
              "type": "string"
            },
            "counterparty_id": {
              "type": "string"
            },
            "idempotency_key": {
              "type": "string"
            },
            "recipient_address": {
              "type": "string"
            }
          },
          "additionalProperties": false
        },
        "maxItems": 20,
        "minItems": 1
      },
      "idempotency_key": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
check_payment_recipient 1 change
{
  "name": "check_payment_recipient",
  "description": "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 wi",
  "inputSchema": {
    "type": "object",
    "required": [
      "recipient_address",
      "amount",
      "asset",
      "network",
      "idempotency_key",
      "requested_at"
    ],
    "properties": {
      "asset": {
        "type": "string"
      },
      "amount": {
        "type": "string",
        "description": "Decimal string, never a float."
      },
      "network": {
        "type": "string"
      },
      "purpose": {
        "type": "string"
      },
      "requested_at": {
        "type": "string"
      },
      "counterparty_id": {
        "type": "string"
      },
      "idempotency_key": {
        "type": "string"
      },
      "recipient_address": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}
get_receipt 1 change
{
  "name": "get_receipt",
  "description": "Free: fetch a stored receipt by receipt_id or idempotency_key. Use it to reconcile an uncertain payment before ever paying again.",
  "inputSchema": {
    "type": "object",
    "properties": {
      "receipt_id": {
        "type": "string"
      },
      "idempotency_key": {
        "type": "string"
      }
    },
    "additionalProperties": false
  },
  "annotations": {
    "readOnlyHint": true
  }
}

Get alerted

Get an email or webhook when this server's readiness drops by 10+ points, tool-poisoning text appears, or a tool breaks:

curl -X POST https://glimind.com/v1/subscriptions -H 'content-type: application/json' -d '{"tools":["mcp-registry/dev.kgninja/check-payment-recipient"],"email":"[email protected]"}'

Agents: watch_tool({"toolId": "mcp-registry/dev.kgninja/check-payment-recipient"}) over MCP.

Passed

Largest tool definitions

Static checks of the advertised tools/list (schema, descriptions, annotations, tool-poisoning patterns, names, size) plus observed protocol, uptime, latency and contract changes. Read-only: no tool is ever called. Weights: schema 15, docs 20, safety 15, efficiency 15, compatibility 15, protocol 5, reliability 10, stability 5. Token counts are estimates (~3.6 characters per token).

Operator? Fix these, then re-check live.

Badge for your README

Shows whether the server is live and its agent-readiness score; it updates within the hour.

MCP server status

Markdown
[![MCP server status](https://glimind.com/badge/mcp-registry%2Fdev.kgninja%2Fcheck-payment-recipient.svg)](https://glimind.com/server/mcp-registry%2Fdev.kgninja%2Fcheck-payment-recipient?ref=badge)
HTML
<a href="https://glimind.com/server/mcp-registry%2Fdev.kgninja%2Fcheck-payment-recipient?ref=badge"><img src="https://glimind.com/badge/mcp-registry%2Fdev.kgninja%2Fcheck-payment-recipient.svg" alt="MCP server status"></a>

Tool-definition log

Glimind records every version of this server's tool definitions in a signed, append-only transparency log. Current manifest sha256:f92d70545e018046…, first seen 2026-11-18, included at leaf 324235 of 384,933. Version history · verify what your client received.

Tools (5)

Compare: most reliable payments servers · most reliable finance servers · most reliable other servers · most reliable knowledge servers

Know before your agent calls it

Glimind tells agents whether a server is up right now and how to call it, then fails over to a live alternative when it isn't.

Add Glimind — free, no signup:

Add to Cursor Add to VS Code

Claude Code

claude mcp add --transport http glimind https://glimind.com/mcp?ref=install-server

Claude Desktop · Windsurf · Cline (mcpServers JSON)

{
  "mcpServers": {
    "glimind": {
      "type": "http",
      "url": "https://glimind.com/mcp?ref=install-server"
    }
  }
}

FAQ

Is the Kgninja Check Payment Recipient MCP server down right now?

As of 2026-11-22 19:03 UTC, the Kgninja Check Payment Recipient MCP server is up with a Glimind reliability score of 95/100 (grade A). Over the last 30 days it answered 100% of Glimind's liveness checks.

How many tools does Kgninja Check Payment Recipient MCP server provide?

Kgninja Check Payment Recipient MCP server advertises 5 tools, including check_payment_batch, check_payment_recipient, get_receipt, list_capabilities, ping.

How do I install Kgninja Check Payment Recipient MCP server?

Point your MCP client at this streamable-http endpoint: https://check-payment-recipient.fuwafuwow.workers.dev/mcp

Is the Kgninja Check Payment Recipient MCP server safe to connect to an AI agent?

Glimind scanned all 5 tool definitions for tool-poisoning patterns — hidden or invisible characters, instructions that override the model, concealment from the user, requests to read credential or MCP config files, conversation exfiltration and cross-tool shadowing — and found none. This checks what the server tells the model, not what its code does; review the source before granting access to sensitive data.

Operator of Kgninja Check Payment Recipient MCP server?

Status page: 90-day uptime, every outage and how long it lasted.

Claim this listing to get the Verified operator marker, a remediation checklist and owner analytics, or embed the live badge from any of the tool pages above. Maintainers: alerts, deploy attestation and monthly reports.

Status is an automated estimate from Glimind's liveness checks (handshake and tool listing only; no tool is ever called) and may lag or differ from your network. Glimind is not affiliated with this server or its operator. Operator? Request a correction or opt out at https://glimind.com/opt-out.

Feedback
Help us improve