# ChargeGuard Dispute Assistant (remote · www.trychargeguard.com)

Chargeback intelligence: 9 card-network reason codes, winning evidence, gateway deadlines. Free.

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

## Components

- remote · `www.trychargeguard.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-trychargeguard-chargeguard/www.md), [page](https://verifymcp.io/servers/com-trychargeguard-chargeguard/www)

## Channel facts

- Endpoint: `https://www.trychargeguard.com/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-05.

- **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 4 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**: 73/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 344 tokens (~86/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% 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 4 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the ChargeGuard Dispute Assistant MCP server?

ChargeGuard Dispute Assistant is a hosted endpoint at https://www.trychargeguard.com/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 com-trychargeguard-chargeguard 'https://www.trychargeguard.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-trychargeguard-chargeguard": {
      "url": "https://www.trychargeguard.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-trychargeguard-chargeguard": {
      "type": "http",
      "url": "https://www.trychargeguard.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-trychargeguard-chargeguard]
url = "https://www.trychargeguard.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-trychargeguard-chargeguard": {
      "type": "remote",
      "url": "https://www.trychargeguard.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-trychargeguard-chargeguard --url 'https://www.trychargeguard.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-trychargeguard-chargeguard:
    url: "https://www.trychargeguard.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-trychargeguard-chargeguard": {
      "Transport": "http",
      "Url": "https://www.trychargeguard.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-trychargeguard-chargeguard -t streamable-http -u 'https://www.trychargeguard.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-trychargeguard-chargeguard": {
      "type": "http",
      "url": "https://www.trychargeguard.com/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-04 (score 70, +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-02 (score 69, +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-10-31 (score 68, +1)

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

### 2026-10-29 (score 67, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-28 (score 66)

First indexed and scored.

## MCP tools (4)

### `list_reason_codes` (~49 tokens)

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` (~99 tokens)

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').

Input parameters:

- `query` (string, required): Reason code like '13.2' or '4515', or slug fragment like 'visa-13-2'

### `get_response_deadlines` (~49 tokens)

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` (~122 tokens)

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.

Input parameters:

- `company` (string, required): Company or store name
- `email` (string, required): Contact email for the audit report
- `notes` (string): Optional context: dispute volume, card networks, current provider
- `platform` (string): Shopify, WooCommerce, Magento, BigCommerce or custom
- `store_url` (string, required): Store URL, e.g. https://mystore.com

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-trychargeguard-chargeguard/www#diagnostics

## Score history

- 2026-11-05: 70
- 2026-11-04: 70
- 2026-11-03: 69
- 2026-11-02: 69
- 2026-11-01: 68
- 2026-10-31: 68
- 2026-10-30: 67
- 2026-10-29: 67
- 2026-10-28: 66

## Common questions

### What is the ChargeGuard Dispute Assistant MCP server?

ChargeGuard Dispute Assistant is an MCP server listed in the public MCP registry as com.trychargeguard/chargeguard. Chargeback intelligence: 9 card-network reason codes, winning evidence, gateway deadlines. Free. This page covers its hosted endpoint (https://www.trychargeguard.com/mcp).

### Is the ChargeGuard Dispute Assistant MCP server safe to use?

ChargeGuard Dispute Assistant scores 70 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 ChargeGuard Dispute Assistant MCP server expose?

ChargeGuard Dispute Assistant exposes 4 tools: list_reason_codes, lookup_reason_code, get_response_deadlines, request_chargeback_audit. Their descriptions and schemas cost roughly 319 tokens of context every time the server is loaded.

### Does the ChargeGuard Dispute Assistant MCP server require authentication?

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

### Is the ChargeGuard Dispute Assistant MCP server still maintained?

ChargeGuard Dispute Assistant is still listed as active in the MCP registry. We last reached this channel on 5 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 ChargeGuard Dispute Assistant MCP server?

VerifyMCP ran 12 checks on ChargeGuard Dispute Assistant, 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 ChargeGuard Dispute Assistant: 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://www.trychargeguard.com/mcp
- Website: https://www.trychargeguard.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-trychargeguard-chargeguard/www.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-trychargeguard-chargeguard/www/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-trychargeguard-chargeguard/www.json
- HTML version of this page: https://verifymcp.io/servers/com-trychargeguard-chargeguard/www