representments.com
REMOTE · REPRESENTMENTS.COM
Explains each card chargeback reason code and the proof that wins it, and prices custom responses.
Available components
Last scanned (11 hours ago)
Scores higher than 90% of remote servers
Reachable. Last reached 7 Nov 2026.
Category Finance and Payments
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 Security100
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation. View diagnostics → Pass
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability75
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 397 tokens (~99/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 Management23
- Stability observed for 7 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 Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- 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
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 7 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Nov 26 +7
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 4 Nov 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.
- 2 Nov 26 +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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 75
First indexed and scored.
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 7 Nov 2026 · Probed https://representments.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=representments.com | CN=YR2,O=Let's Encrypt,C=US | 31 Oct 2026 | 29 Jan 2027 | RSA 2048 | SHA256-RSA | 5a9d09b58df5ecddcdd6172b36c66ca7d38 |
| SANs: representments.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of representments.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| representments.com. | DS published | 2371 | 13 | Verified |
| representments.com. | Verified address RRset verified with the apex keys |
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 |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://representments.com/mcp | Verified | 200 | |
| http (plaintext) | http://representments.com/mcp | HTTPS enforced | 308 | https://representments.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 →
get_help_with_a_dispute Get help with a chargeback ~94
For a merchant with a chargeback open now. Explains how to get a custom response to it, with the first one free. Pass the reason code if you know it.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | – | The reason code on the chargeback notice, for example 13.1 or Visa 10.4. |
| network | string | – | Card network: Visa, Mastercard, Amex or Discover. |
No output schema declared.
No examples provided.
get_pricing Get pricing ~43
Prices for representments.com in US dollars: the free first response, the two monthly plans, and per-case work for a single chargeback over $10,000.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
list_reason_codes List chargeback reason codes ~70
Lists the Visa, Mastercard, Amex and Discover chargeback reason codes that representments.com explains, each with its plain-English name and a link to the full page. Pass a network to see only its codes.
| Name | Type | Req | Description |
|---|---|---|---|
| network | string | – | Card network: Visa, Mastercard, Amex or Discover. |
No output schema declared.
No examples provided.
lookup_reason_code Look up a chargeback reason code ~111
Explains one chargeback reason code: what the customer claimed, the proof that wins, the situations it usually comes from, and a link to the full page. Accepts forms such as 13.1, Visa 10.4, 4853 or C08.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The reason code on the chargeback notice, for example 13.1 or Visa 10.4. |
| network | string | – | Card network: Visa, Mastercard, Amex or Discover. |
No output schema declared.
No examples provided.
How do I install the representments.com MCP server?
representments.com is a hosted endpoint at https://representments.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 · representments.com
claude mcp add --transport http com-representments-chargebacks 'https://representments.com/mcp'
What is the representments.com MCP server?
representments.com is an MCP server listed in the public MCP registry as com.representments/chargebacks. Explains each card chargeback reason code and the proof that wins it, and prices custom responses. This page covers its hosted endpoint (https://representments.com/mcp).
Is the representments.com MCP server safe to use?
representments.com scores 85 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 representments.com MCP server expose?
representments.com exposes 4 tools: list_reason_codes, lookup_reason_code, get_pricing, get_help_with_a_dispute. Their descriptions and schemas cost roughly 318 tokens of context every time the server is loaded.
Does the representments.com MCP server require authentication?
No. We connected to representments.com without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the representments.com MCP server still maintained?
representments.com is still listed as active in the MCP registry. We last reached this channel on 7 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 representments.com MCP server?
VerifyMCP ran 13 checks on representments.com, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.