Counterparty Check
REMOTE · COUNTERPARTYCHECK.COM
Check a payee before your agent pays: sanctions, lookalike domains, payment details, invoice fraud.
Available components
Last scanned (4 minutes ago)
Scores higher than 69% of remote servers
Unreachable for 2 days in a row. Last reached 3 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 Security11
- TLS not yet verified: we couldn't open a connection to check the certificate. View diagnostics → Unverified
- Authorisation not yet verified: we couldn't confirm whether this endpoint requires it. View diagnostics → Unverified
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS not yet verified: we couldn't read the response headers to check for it. View diagnostics → Unverified
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability0
- Transport check failed: declared streamable-http, but we couldn't connect to verify it. See how to fix → View diagnostics → Fail
Schema Quality & AI Usability0
- Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.Unverified
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
- Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Tool Safety0
- Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.Unverified
Capabilities0
- Capabilities not yet verified: we couldn't read the endpoint's capabilities.Unverified
Unverified: 5 categories
Categories scored 0 because we could not verify them: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.
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 0
- Endpoint reachability: reachable → unreachable ▼ security
- HSTS header: fail → unverified ▼ security
- Stability: 0.60 → unverified ▼ security
- Authorization: partial → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- TLS certificate: pass → unverified ▼ security
- Transport: pass → fail ▼ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- First check of Schema quality: unverified functional
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 57 to 60. That category is still filling its 30-day observation window: 17 days of observed history at the previous scan, 18 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 50 to 53. That category is still filling its 30-day observation window: 15 days of observed history at the previous scan, 16 at this one. The score rises as the window fills, whether or not the server changes.
- 30 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.
- 27 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.
- 25 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.
- 23 Oct 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.
- 21 Oct 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
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://counterpartycheck.com/mcp
TLS unreached
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of counterpartycheck.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| counterpartycheck.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Inconclusive
We could not reach the endpoint well enough to judge its authorisation posture.
| Result | Inconclusive |
|---|
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://counterpartycheck.com/mcp | Unreachable | ||
| http (plaintext) | http://counterpartycheck.com/mcp | HTTPS enforced |
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 →
check_balance API key balance ~24
Show the remaining prepaid balance on the API key used for this connection. Free.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
check_counterparty Check a payee before paying ~168
Run a full pre-payment risk check on a payee: OFAC sanctions (names and wallets), domain age and email authentication, lookalike domains (vendor impersonation, brand typo-squats, executive impersonation), routing/IBAN/SWIFT/wallet validation, and business-email-compromise signals. Returns verdict proceed/review/block, a 0-100 risk score, explained findings, and a signed receipt. Costs $0.25 from the API key balance. Fill in "context" with everything you know about how the payment request arrived; it materially improves fraud detection.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | What the paying agent knows about how this payment came about. Each field sharpens fraud detection. |
| counterparty | object | yes | – |
| payment | object | – | – |
No output schema declared.
No examples provided.
screen_sanctions Sanctions screen only ~110
Screen a payee name (and optional crypto wallet) against OFAC sanctions lists and embargoed jurisdictions. Faster and cheaper than check_counterparty but does not detect fraud patterns. Costs $0.05 from the API key balance; without a key, the first 3 screens each day are free.
| Name | Type | Req | Description |
|---|---|---|---|
| context | object | – | What the paying agent knows about how this payment came about. Each field sharpens fraud detection. |
| counterparty | object | yes | – |
| payment | object | – | – |
No output schema declared.
No examples provided.
verify_receipt Verify a check receipt ~44
Confirm that a receipt returned by a previous check is authentic and unaltered. Free.
| Name | Type | Req | Description |
|---|---|---|---|
| receipt | object | yes | The full "receipt" object from a check response |
No output schema declared.
No examples provided.
How do I install the Counterparty Check MCP server?
Counterparty Check is a hosted endpoint at https://counterpartycheck.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 · counterpartycheck.com
claude mcp add --transport http chtwebllc-counterparty-check 'https://counterpartycheck.com/mcp'
What is the Counterparty Check MCP server?
Counterparty Check is an MCP server listed in the public MCP registry as io.github.chtwebllc/counterparty-check. Check a payee before your agent pays: sanctions, lookalike domains, payment details, invoice fraud. This page covers its hosted endpoint (https://counterpartycheck.com/mcp).
Is the Counterparty Check MCP server safe to use?
Counterparty Check scores 77 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 Counterparty Check MCP server expose?
Counterparty Check exposes 4 tools: check_counterparty, screen_sanctions, check_balance, verify_receipt. Their descriptions and schemas cost roughly 346 tokens of context every time the server is loaded.
Does the Counterparty Check MCP server require authentication?
Its publisher declares that Counterparty Check requires credentials, so you will need to authorise it in your MCP client. We have not been able to confirm that against the live endpoint.
Is the Counterparty Check MCP server still maintained?
Counterparty Check is still listed in the MCP registry, though our most recent checks did not reach this channel. We last reached this channel on 3 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.