# com.edgethirteen.www/chargeback-response (remote · www.edgethirteen.com)

Draft a chargeback dispute-response evidence checklist and letter preview from order details.

- Trust score: 25/100 (low)
- Change this week: −46
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-24

## Components

- remote · `www.edgethirteen.com`: 25/100 (this document), [markdown](https://verifymcp.io/servers/com-edgethirteen-www-chargeback-response/api-mcp-chargeback-response.md), [page](https://verifymcp.io/servers/com-edgethirteen-www-chargeback-response/api-mcp-chargeback-response)

## Channel facts

- Endpoint: `https://www.edgethirteen.com/api/mcp/chargeback-response`
- 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-09-24.

- **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 connect, but we couldn't read the tool list to see what that exposes.
  - 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**: 0/100
  - Transport check failed: declared streamable-http, but the endpoint returned HTTP 404.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**Unverified: 5 categories.** Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### How do I install the com.edgethirteen.www/chargeback-response MCP server?

com.edgethirteen.www/chargeback-response is a hosted endpoint at https://www.edgethirteen.com/api/mcp/chargeback-response, 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-edgethirteen-www-chargeback-response 'https://www.edgethirteen.com/api/mcp/chargeback-response'
```

### Cursor

```json
{
  "mcpServers": {
    "com-edgethirteen-www-chargeback-response": {
      "url": "https://www.edgethirteen.com/api/mcp/chargeback-response"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-edgethirteen-www-chargeback-response": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/chargeback-response"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-edgethirteen-www-chargeback-response]
url = "https://www.edgethirteen.com/api/mcp/chargeback-response"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-edgethirteen-www-chargeback-response --url 'https://www.edgethirteen.com/api/mcp/chargeback-response' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-edgethirteen-www-chargeback-response:
    url: "https://www.edgethirteen.com/api/mcp/chargeback-response"
```

### Netclaw

```json
{
  "McpServers": {
    "com-edgethirteen-www-chargeback-response": {
      "Transport": "http",
      "Url": "https://www.edgethirteen.com/api/mcp/chargeback-response"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-edgethirteen-www-chargeback-response -t streamable-http -u 'https://www.edgethirteen.com/api/mcp/chargeback-response'
```

### Other

```json
{
  "mcpServers": {
    "com-edgethirteen-www-chargeback-response": {
      "type": "http",
      "url": "https://www.edgethirteen.com/api/mcp/chargeback-response"
    }
  }
}
```

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-09-24 (score 25, −51)

- [security regression] Endpoint reachability: reachable → not serving MCP
- [security regression] Stability: 0.30 → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-09-22 (score 76, +1)

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

### 2026-09-19 (score 75, +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-09-18 (score 74, +3)

- [functional improvement] MCP protocol: fail → pass
- [functional] MCP protocol version: 2025-03-26 → 2025-11-25

### 2026-09-17 (score 71, +7)

- [security improvement] Authorization: unverified → partial
- [security] Tool “draft_chargeback_response_checklist” rewrote its description, which is the text the model reads

### 2026-09-16 (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-09-15 (score 63, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-14 (score 63)

First indexed and scored.

## MCP tools (1)

### `draft_chargeback_response_checklist` (~353 tokens)

Given a chargeback/dispute reason code category and order details, return the evidence checklist for that reason code (what to attach: tracking numbers, prior-order signals, refund records, etc.) and a preview of the response letter. Covers Visa 10.4/13.1/13.3/13.7/13.6/12.6.1 and the equivalent Mastercard reason codes. The full formatted dispute-response letter is a separate $39 product at https://www.edgethirteen.com/tools/chargeback-response. Not legal advice.

Input parameters:

- `amount` (string): Disputed amount
- `category` (string, required): The dispute reason category: fraud_card_absent (“I didn't make this purchase” (Visa 10.4, Mastercard 4837 — fraud)); not_received (“I never got it” (Visa 13.1, Mastercard 4855 — product/service not r…
- `currency` (string): Currency code, defaults to USD
- `merchant_name` (string): Merchant/business name
- `order_date` (string): Order date
- `order_id` (string): Order or transaction ID
- `product_description` (string): What was sold

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-edgethirteen-www-chargeback-response/api-mcp-chargeback-response#diagnostics

## Score history

- 2026-09-24: 25
- 2026-09-23: 76
- 2026-09-22: 76
- 2026-09-21: 75
- 2026-09-20: 75
- 2026-09-19: 75
- 2026-09-18: 74
- 2026-09-17: 71
- 2026-09-16: 64
- 2026-09-15: 63
- 2026-09-14: 63

## Common questions

### What is the com.edgethirteen.www/chargeback-response MCP server?

com.edgethirteen.www/chargeback-response is an MCP server listed in the public MCP registry as com.edgethirteen.www/chargeback-response. Draft a chargeback dispute-response evidence checklist and letter preview from order details. This page covers its hosted endpoint (https://www.edgethirteen.com/api/mcp/chargeback-response).

### Is the com.edgethirteen.www/chargeback-response MCP server safe to use?

com.edgethirteen.www/chargeback-response scores 25 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 com.edgethirteen.www/chargeback-response MCP server expose?

com.edgethirteen.www/chargeback-response exposes 1 tool: draft_chargeback_response_checklist. Their descriptions and schemas cost roughly 353 tokens of context every time the server is loaded.

### Does the com.edgethirteen.www/chargeback-response MCP server require authentication?

No. We connected to com.edgethirteen.www/chargeback-response without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the com.edgethirteen.www/chargeback-response MCP server still maintained?

com.edgethirteen.www/chargeback-response is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://www.edgethirteen.com/api/mcp/chargeback-response
- Website: https://www.edgethirteen.com/tools/chargeback-response
- Changelog RSS feed: https://verifymcp.io/servers/com-edgethirteen-www-chargeback-response/api-mcp-chargeback-response.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-edgethirteen-www-chargeback-response/api-mcp-chargeback-response.json
- HTML version of this page: https://verifymcp.io/servers/com-edgethirteen-www-chargeback-response/api-mcp-chargeback-response