Recoup: AI agent refund audit
REMOTE · RECOUPAUDIT.COM
Checks AI support agent refunds against Shopify and Stripe. Read-only pricing, fit and estimates.
Available components
Last scanned (8 hours ago)
Scores higher than 55% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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. How we score → Why this is hard to score →
Endpoint Security57
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 382 tokens (~95/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management60
- Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 4 Nov 26 +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.
- 2 Nov 26 +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.
- 31 Oct 26 +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.
- 29 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 20 Oct 26 +1
- The server rewrote its instructions, which are the text every model session reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://recoupaudit.com/mcp/
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=recoupaudit.com | CN=YE1,O=Let's Encrypt,C=US | 17 Oct 2026 | 15 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5c74808e0eff7757b6e41d75c2a5caf4cc6 |
| SANs: recoupaudit.com, www.recoupaudit.com | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of recoupaudit.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| recoupaudit.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| content-security-policy | upgrade-insecure-requests |
| x-content-type-options | nosniff |
| referrer-policy | strict-origin-when-cross-origin |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://recoupaudit.com/mcp/ | Verified | 200 | |
| http (plaintext) | http://recoupaudit.com/mcp/ | HTTPS enforced | 301 | https://recoupaudit.com/mcp/ |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
estimate_refund_exposure Estimate refund exposure ~186
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.
| Name | Type | Req | Description |
|---|---|---|---|
| ai_tickets_per_month | number | yes | 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. |
No output schema declared.
No examples provided.
get_recoup_overview What Recoup does ~55
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_recoup_pricing Recoup pricing ~21
Current Recoup prices and what each plan covers.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_supported_sources Supported help desks and exports ~28
Which help desks, AI agents and payment systems Recoup reads, with the page for each.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
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.
remote · recoupaudit.com
claude mcp add --transport http com-recoupaudit-recoup 'https://recoupaudit.com/mcp/'
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.