Skip to main content
Glama

Server Details

payout check

If you are the author of this connector, you can claim ownership. Claimed connector authors can inspect health checks, view analytics, and manage their listing.
Status
Healthy
Uptime
100.0% over the last 24 hours
Last Tested
Transport
Streamable HTTP · MCP 2025-06-18
URL
ChatGPT
–
Claude
–

TDQS

A4.1/5.0

Scored across 3 tools

Disambiguation5/5

Each tool is clearly distinct: single validation, batch validation, and outcome reporting. The batch tool explicitly extends the single validator with the same input shape, and the reporting tool has a unique post-payment purpose, so an agent can easily choose the right one.

Naming Consistency5/5

All three tools follow a consistent verb_noun_object snake_case pattern (validate_payout_beneficiary, validate_payout_batch, report_payout_outcome) with a shared 'payout' domain token. Batch vs. single is expressed in the same family of names, which is predictable.

Tool Count4/5

Three tools is on the thin side, but the domain (pre-payout beneficiary validation) is narrow and each tool earns its place. Coverage of single, batch, and feedback paths is sensible for the scope.

Completeness4/5

The core lifecycle—validate one, validate many, report outcome—is covered with no dead ends for the primary workflow. Minor gaps: outcome reporting appears single-only (no batch report) and there is no way to retrieve past validations or list supported countries/institutions.

Available Tools

3 tools
report_payout_outcomeReport payout outcomeAInspect

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

Inputs: outcome (required), request_id (required), reason.

validate_payout_batchValidate a batch of LATAM payout beneficiariesA
Read-onlyIdempotent
Inspect

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.

Inputs: items (required).

validate_payout_beneficiaryValidate LATAM payout beneficiaryA
Read-onlyIdempotent
Inspect

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.

Inputs: country (required), tax_id, account, pix_key, +2 more.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

Loading tool schema changelog…

    Related MCP Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Remote MCP server that lets AI assistants read tracked competitive intelligence — competitor news, reviews, website changes, social posts and ads — and act on it by managing projects, competitors, battle cards, reports and canvases. Every answer carries a source and a date, and write actions only publish when explicitly shared.
      MIT
    • A
      license
      A
      quality
      D
      maintenance
      Enables brand visibility monitoring across major AI platforms like ChatGPT, Claude, Gemini, and Perplexity. It allows users to track visibility scores, analyze competitor data, and receive actionable insights to improve AI-generated brand recommendations.
      16
      11 npm
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Browse IndustryLens's published competitive-intelligence reports and head-to-head competitor comparisons from any AI agent — real, source-backed data.
      MIT
    Try in Browser

    Glama MCP Gateway

    Add one secure layer between your agents and this server.

    Resources