# Payout Check (remote · xivenjicbpfqitrqpqiu.supabase.co)

Validate LATAM payout beneficiaries (tax ID, bank account, PIX) for MX, BR, AR, CL, CO, UY.

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

## Components

- remote · `xivenjicbpfqitrqpqiu.supabase.co`: 67/100 (this document), [markdown](https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp.md), [page](https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp)

## Channel facts

- Endpoint: `https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.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**: 63/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 1 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 is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 487 tokens (~162/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 93/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 80% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Payout Check MCP server?

Payout Check is a hosted endpoint at https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/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 marcanthonybeare-agentpay-payout-check 'https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "marcanthonybeare-agentpay-payout-check": {
      "url": "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "marcanthonybeare-agentpay-payout-check": {
      "type": "http",
      "url": "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.marcanthonybeare-agentpay-payout-check]
url = "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "marcanthonybeare-agentpay-payout-check": {
      "type": "remote",
      "url": "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add marcanthonybeare-agentpay-payout-check --url 'https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  marcanthonybeare-agentpay-payout-check:
    url: "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "marcanthonybeare-agentpay-payout-check": {
      "Transport": "http",
      "Url": "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add marcanthonybeare-agentpay-payout-check -t streamable-http -u 'https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp'
```

### Other

```json
{
  "mcpServers": {
    "marcanthonybeare-agentpay-payout-check": {
      "type": "http",
      "url": "https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/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 67, +1)

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

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

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

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

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

### 2026-11-14 (score 64, +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-13 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-12 (score 63)

First indexed and scored.

## MCP tools (3)

### `validate_payout_beneficiary` (~285 tokens)

Validate LATAM payout beneficiary

Check a payout beneficiary's tax ID and bank account (or PIX key) for Mexico, Brazil, Argentina, Chile, Colombia or Uruguay before sending money. Validates format, check digits and bank code against central-bank directories. Returns verdict ready | review | invalid with error codes and bank name. MX: RFC + CLABE. BR: CPF/CNPJ + PIX key. AR: CUIT/CUIL + CBU/CVU. CL/CO/UY: tax ID + account with bank_code. Does not confirm account ownership.

Input parameters:

- `account` (string): CLABE (MX), CBU/CVU (AR), or local account number (CL, CO, UY; needs bank_code)
- `account_type` (string): Optional; improves CO checks
- `bank_code` (string): CL: CMF code (012 BancoEstado). CO: CENIT code (1007 Bancolombia, 1507 Nequi). UY: BCU code (001 BROU, 113 Itau)
- `country` (string, required): ISO country code of the beneficiary
- `pix_key` (string): PIX key (BR only)
- `tax_id` (string): RFC (MX), CPF/CNPJ (BR), CUIT/CUIL (AR), RUT (CL), NIT (CO), RUT/CI (UY)

### `validate_payout_batch` (~62 tokens)

Validate a batch of LATAM payout beneficiaries

Validate up to 100 beneficiaries in one call (payroll runs, supplier files, marketplace withdrawals). Each item takes the same fields as validate_payout_beneficiary. Returns a summary count per verdict and per-item results.

Input parameters:

- `items` (array, required)

### `report_payout_outcome` (~75 tokens)

Report payout outcome

After sending a payout that was checked with validate_payout_beneficiary, report whether it was paid or bounced. Improves future checks.

Input parameters:

- `outcome` (string, required)
- `reason` (string): Optional bank rejection reason
- `request_id` (string, required): request_id returned by validate_payout_beneficiary

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp#diagnostics

## Score history

- 2026-11-21: 67
- 2026-11-20: 66
- 2026-11-19: 66
- 2026-11-18: 65
- 2026-11-17: 65
- 2026-11-16: 64
- 2026-11-15: 64
- 2026-11-14: 64
- 2026-11-13: 63
- 2026-11-12: 63

## Common questions

### What is the Payout Check MCP server?

Payout Check is an MCP server listed in the public MCP registry as io.github.marcanthonybeare-agentpay/payout-check. Validate LATAM payout beneficiaries (tax ID, bank account, PIX) for MX, BR, AR, CL, CO, UY. This page covers its hosted endpoint (https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp).

### Is the Payout Check MCP server safe to use?

Payout Check scores 67 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 Payout Check MCP server expose?

Payout Check exposes 3 tools: validate_payout_beneficiary, validate_payout_batch, report_payout_outcome. Their descriptions and schemas cost roughly 422 tokens of context every time the server is loaded.

### Does the Payout Check MCP server require authentication?

No. We connected to Payout Check without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Payout Check MCP server still maintained?

Payout Check 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 Payout Check MCP server?

VerifyMCP ran 12 checks on Payout Check, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Payout Check: Authorization. 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://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp
- Changelog RSS feed: https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp.json
- HTML version of this page: https://verifymcp.io/servers/marcanthonybeare-agentpay-payout-check/functions-v1-mcp
