ChargeGuard MCP server

• Registry namecom.trychargeguard/chargeguardverified in the MCP registry

The registry name sits under trychargeguard.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-29
• Tools4
• Server calls itselfchargeguard
• Server version1.0.0
• Protocol version2025-06-18

On 2026-10-29 the server answered initialize and tools/list without a sign-in. First answer in 1010 ms.

• Its tools do none of the product's use cases we checked: generate dispute response letters for chargebacks; export defense documents as PDF with attached evidence.
• Checked on 6 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP scoreafter a weeka score needs 7 daily checks: 6 so far
• What an agent can do with it0 of 2 use cases
• Answeredmeasuring6 of the 7 daily checks it takes to print a share
• Median first answer1140 ms
• Space in an agent's context≈ 450 tokensthe definitions of all its tools (4), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 4 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 4 of 4

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• list_reason_codes

  List the 9 card-network chargeback reason codes covered by ChargeGuard (Visa, Mastercard, Amex) with one-line summaries. Use first when the user mentions a chargeback without a code.

• lookup_reason_code

  Look up one card-network chargeback reason code: what it means, the evidence that wins the representment, the response window, and the full guide URL. Accepts the code (e.g. '13.2') or a slug fragment (e.g. 'visa-13-2').

• get_response_deadlines

  Response windows merchants have to fight a chargeback, per gateway (Stripe, PayPal, Braintree, Adyen, Shopify Payments) and per card network (Visa, Mastercard, Amex).

• request_chargeback_audit

  Submit a free ChargeGuard store audit: reviews the merchant's payment setup and dispute risk and emails a written report. Requires the store URL and a contact email.