Remote MCP · Endpoint
ChargeGuard Dispute Assistant MCP server
No. ChargeGuard Dispute Assistant answered an MCP handshake 3 days ago.
UpLast checked 3 days ago
Server URL
https://www.trychargeguard.com/mcp
The last check completed an MCP handshake.
- Registry name
- com.trychargeguard/chargeguard
- Transport
- Streamable HTTP
- Protocol negotiated
- 2025-06-18
- Handshake latency
- 935 ms
- Tools exposed
- 4 tools
- Uptime, last 30 days
- 100% from 9 checks
- Described by its publisher as
- Chargeback intelligence: 9 card-network reason codes, winning evidence, gateway deadlines. Free.
- Listing
- From the official MCP registry (active).
| Checked | Result | Handshake |
|---|---|---|
| 3 days ago | Handshake completed | 935 ms |
| 4 days ago | Handshake completed | 226 ms |
| 4 days ago | Handshake completed | 948 ms |
| 6 days ago | Handshake completed | 169 ms |
| 7 days ago | Handshake completed | 458 ms |
| 8 days ago | Handshake completed | 148 ms |
| 9 days ago | Handshake completed | 172 ms |
| 10 days ago | Handshake completed | 153 ms |
| 12 days ago | Handshake completed | 2.18 s |
The last 9 checks. Full history is kept for 30 days; the all-time counter stands at 9 responding of 9.
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 ChargeGuard Dispute Assistant and makes no claim about it beyond what these checks measured.