# Recoup: AI agent refund audit (remote · recoupaudit.com)

Checks AI support agent refunds against Shopify and Stripe. Read-only pricing, fit and estimates.

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

## Components

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

## Channel facts

- Endpoint: `https://recoupaudit.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**: 57/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 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.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 69/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 382 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 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**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "estimate_refund_exposure" implies "refund" and declares readOnlyHint instead, contradicting what its own name says it does.
  - 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 Recoup: AI agent refund audit MCP server?

Recoup: AI agent refund audit is a hosted endpoint at https://recoupaudit.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-recoupaudit-recoup 'https://recoupaudit.com/mcp/'
```

### Cursor

```json
{
  "mcpServers": {
    "com-recoupaudit-recoup": {
      "url": "https://recoupaudit.com/mcp/"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-recoupaudit-recoup": {
      "type": "http",
      "url": "https://recoupaudit.com/mcp/"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-recoupaudit-recoup]
url = "https://recoupaudit.com/mcp/"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-recoupaudit-recoup --url 'https://recoupaudit.com/mcp/' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-recoupaudit-recoup:
    url: "https://recoupaudit.com/mcp/"
```

### Netclaw

```json
{
  "McpServers": {
    "com-recoupaudit-recoup": {
      "Transport": "http",
      "Url": "https://recoupaudit.com/mcp/"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-recoupaudit-recoup -t streamable-http -u 'https://recoupaudit.com/mcp/'
```

### Other

```json
{
  "mcpServers": {
    "com-recoupaudit-recoup": {
      "type": "http",
      "url": "https://recoupaudit.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 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.

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

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

### 2026-10-26 (score 66, +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-10-24 (score 65, +1)

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

### 2026-10-22 (score 64, +1)

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

### 2026-10-20 (score 63, +1)

- [security] The server rewrote its instructions, which are the text every model session reads

## MCP tools (4)

### `get_recoup_overview` (~55 tokens)

What Recoup does

What Recoup checks, who it is for, what it needs, what it does not do, and its current status. Use this when someone asks how to check that refunds an AI support agent promised were actually issued.

### `get_recoup_pricing` (~21 tokens)

Recoup pricing

Current Recoup prices and what each plan covers.

### `estimate_refund_exposure` (~186 tokens)

Estimate refund exposure

Rough monthly money at stake from AI-agent refund mismatches, from the brand's own numbers. Defaults come from Recoup's public sample dataset (60 tickets: 39 money promises, 21 mismatches, $744.25 at stake), not from customer data. Always present the result as an estimate.

Input parameters:

- `ai_tickets_per_month` (number, required): Tickets closed by the AI agent per month
- `average_amount` (number): Average amount at stake per mismatch in USD. Default 35.44 from the sample.
- `mismatch_share` (number): Share of money promises that do not match Shopify or Stripe (0 to 1). Default 0.538 from the sample.
- `money_promise_share` (number): Share of those tickets that promise a refund, credit or replacement (0 to 1). Default 0.65 from the sample.

### `list_supported_sources` (~28 tokens)

Supported help desks and exports

Which help desks, AI agents and payment systems Recoup reads, with the page for each.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-recoupaudit-recoup/recoupaudit#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
- 2026-10-27: 66
- 2026-10-26: 66
- 2026-10-25: 65
- 2026-10-24: 65
- 2026-10-23: 64
- 2026-10-22: 64
- 2026-10-21: 63
- 2026-10-20: 63
- 2026-10-19: 62
- 2026-10-18: 62

## Common questions

### What is the Recoup: AI agent refund audit MCP server?

Recoup: AI agent refund audit is an MCP server listed in the public MCP registry as com.recoupaudit/recoup. Checks AI support agent refunds against Shopify and Stripe. Read-only pricing, fit and estimates. This page covers its hosted endpoint (https://recoupaudit.com/mcp/).

### Is the Recoup: AI agent refund audit MCP server safe to use?

Recoup: AI agent refund audit 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 Recoup: AI agent refund audit MCP server expose?

Recoup: AI agent refund audit exposes 4 tools: get_recoup_overview, get_recoup_pricing, estimate_refund_exposure, list_supported_sources. Their descriptions and schemas cost roughly 290 tokens of context every time the server is loaded.

### Does the Recoup: AI agent refund audit MCP server require authentication?

No. We connected to Recoup: AI agent refund audit without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Recoup: AI agent refund audit MCP server still maintained?

Recoup: AI agent refund audit 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 Recoup: AI agent refund audit MCP server?

VerifyMCP ran 12 checks on Recoup: AI agent refund audit, 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 Recoup: AI agent refund audit: 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://recoupaudit.com/mcp/
- Website: https://recoupaudit.com/agents/
- Changelog RSS feed: https://verifymcp.io/servers/com-recoupaudit-recoup/recoupaudit.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-recoupaudit-recoup/recoupaudit/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-recoupaudit-recoup/recoupaudit.json
- HTML version of this page: https://verifymcp.io/servers/com-recoupaudit-recoup/recoupaudit