Remote MCP · Endpoint

Recoup: AI agent refund audit MCP server

No. Recoup: AI agent refund audit answered an MCP handshake 6 hours ago.

UpLast checked 6 hours ago

Server URL

https://recoupaudit.com/mcp/

The last check completed an MCP handshake.

Registry name
com.recoupaudit/recoup
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
303 ms
Tools exposed
4 tools
Uptime, last 30 days
100% from 14 checks
Described by its publisher as
Checks AI support agent refunds against Shopify and Stripe. Read-only pricing, fit and estimates.
Listing
From the official MCP registry (active).
Recent checks of Recoup: AI agent refund audit
CheckedResultHandshake
6 hours agoHandshake completed303 ms
9 days agoHandshake completed290 ms
10 days agoHandshake completed336 ms
11 days agoHandshake completed289 ms
12 days agoHandshake completed302 ms
14 days agoHandshake completed325 ms
15 days agoHandshake completed289 ms
15 days agoHandshake completed317 ms
17 days agoHandshake completed296 ms
19 days agoHandshake completed304 ms
22 days agoHandshake completed415 ms
24 days agoHandshake completed267 ms
26 days agoHandshake completed222 ms
28 days agoHandshake completed266 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 14 responding of 14.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Recoup: AI agent refund audit and makes no claim about it beyond what these checks measured.