Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Payout Check

REMOTE · XIVENJICBPFQITRQPQIU.SUPABASE.CO

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

+3 this week 67 Trust /100

Last scanned (22 hours ago)

Scores higher than 52% of remote servers

Reachable. Last reached 21 Nov 2026.

Category Finance and Payments

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation 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.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 19 Nov 26 +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.

  • 17 Nov 26 +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.

  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 63

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=supabase.co CN=WE1,O=Google Trust Services,C=US 24 Oct 2026 22 Jan 2027 ECDSA 256 ECDSA-SHA256 d2b50611cd88e9c50e4e2231f4d3f059
SANs: supabase.co, *.supabase.co
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of xivenjicbpfqitrqpqiu.supabase.co. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
co. DS published 7786 8 Verified
supabase.co. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=31536000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp Verified 200
http (plaintext) http://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp HTTPS enforced 301 https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp
MCP tools · 3 exposed · ~422 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
report_payout_outcome ~75

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

NameTypeReqDescription
outcomestringyes–
reasonstring–Optional bank rejection reason
request_idstringyesrequest_id returned by validate_payout_beneficiary

No output schema declared.

No examples provided.

validate_payout_batch ~62

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.

NameTypeReqDescription
itemsarrayyes–

No output schema declared.

No examples provided.

validate_payout_beneficiary ~285

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.

NameTypeReqDescription
accountstring–CLABE (MX), CBU/CVU (AR), or local account number (CL, CO, UY; needs bank_code)
account_typestring–Optional; improves CO checks
bank_codestring–CL: CMF code (012 BancoEstado). CO: CENIT code (1007 Bancolombia, 1507 Nequi). UY: BCU code (001 BROU, 113 Itau)
countrystringyesISO country code of the beneficiary
pix_keystring–PIX key (BR only)
tax_idstring–RFC (MX), CPF/CNPJ (BR), CUIT/CUIL (AR), RUT (CL), NIT (CO), RUT/CI (UY)

No output schema declared.

No examples provided.

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.

remote · xivenjicbpfqitrqpqiu.supabase.co

# add to Claude Code
claude mcp add --transport http marcanthonybeare-agentpay-payout-check 'https://xivenjicbpfqitrqpqiu.supabase.co/functions/v1/mcp'
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.