# Counterparty Check (remote · counterpartycheck.com)

Check a payee before your agent pays: sanctions, lookalike domains, payment details, invoice fraud.

- Trust score: 77/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `counterpartycheck.com`: 77/100 (this document), [markdown](https://verifymcp.io/servers/chtwebllc-counterparty-check/counterpartycheck.md), [page](https://verifymcp.io/servers/chtwebllc-counterparty-check/counterpartycheck)

## Channel facts

- Endpoint: `https://counterpartycheck.com/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `1.0.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-05.

- **Endpoint Security**: 11/100
  - TLS not yet verified: we couldn't open a connection to check the certificate.
  - Authorisation not yet verified: we couldn't confirm whether this endpoint requires it.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS not yet verified: we couldn't read the response headers to check for it.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 0/100
  - Transport check failed: declared streamable-http, but we couldn't connect to verify it.
- **Schema Quality & AI Usability**: 0/100
  - Schema not yet verified: we couldn't read the endpoint's schema, or could read only part of its tool list.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 0/100
  - Tool coverage not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Tool Safety**: 0/100
  - Tool safety not yet verified: we couldn't read the endpoint's tools, or could read only part of the list.
- **Capabilities**: 0/100
  - Capabilities not yet verified: we couldn't read the endpoint's capabilities.

**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.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http chtwebllc-counterparty-check 'https://counterpartycheck.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "chtwebllc-counterparty-check": {
      "url": "https://counterpartycheck.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "chtwebllc-counterparty-check": {
      "type": "http",
      "url": "https://counterpartycheck.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.chtwebllc-counterparty-check]
url = "https://counterpartycheck.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "chtwebllc-counterparty-check": {
      "type": "remote",
      "url": "https://counterpartycheck.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add chtwebllc-counterparty-check --url 'https://counterpartycheck.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  chtwebllc-counterparty-check:
    url: "https://counterpartycheck.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "chtwebllc-counterparty-check": {
      "Transport": "http",
      "Url": "https://counterpartycheck.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add chtwebllc-counterparty-check -t streamable-http -u 'https://counterpartycheck.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "chtwebllc-counterparty-check": {
      "type": "http",
      "url": "https://counterpartycheck.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-04 (score 77, 0)

- [security regression] Endpoint reachability: reachable → unreachable
- [security regression] HSTS header: fail → unverified
- [security regression] Stability: 0.60 → unverified
- [security regression] Authorization: partial → unverified
- [security regression] Tool safety: pass → unverified
- [security regression] TLS certificate: pass → unverified
- [security regression] Transport: pass → fail
- [functional regression] Capabilities: pass → unverified
- [functional regression] Tool coverage: 100 → unverified
- [functional] First check of Schema quality: unverified

### 2026-11-03 (score 77, +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.

### 2026-11-01 (score 76, +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.

### 2026-10-30 (score 75, +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.

### 2026-10-27 (score 74, +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.

### 2026-10-25 (score 73, +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.

### 2026-10-23 (score 72, +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.

### 2026-10-21 (score 71, +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.

## MCP tools (4)

### `check_counterparty` (~168 tokens)

Check a payee before paying

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.

Input parameters:

- `context` (object): What the paying agent knows about how this payment came about. Each field sharpens fraud detection.
- `counterparty` (object, required)
- `payment` (object)

### `screen_sanctions` (~110 tokens)

Sanctions screen only

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.

Input parameters:

- `context` (object): What the paying agent knows about how this payment came about. Each field sharpens fraud detection.
- `counterparty` (object, required)
- `payment` (object)

### `check_balance` (~24 tokens)

API key balance

Show the remaining prepaid balance on the API key used for this connection. Free.

### `verify_receipt` (~44 tokens)

Verify a check receipt

Confirm that a receipt returned by a previous check is authentic and unaltered. Free.

Input parameters:

- `receipt` (object, required): The full "receipt" object from a check response

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/chtwebllc-counterparty-check/counterpartycheck#diagnostics

## Score history

- 2026-11-05: 77
- 2026-11-04: 77
- 2026-11-03: 77
- 2026-11-02: 76
- 2026-11-01: 76
- 2026-10-31: 75
- 2026-10-30: 75
- 2026-10-29: 74
- 2026-10-28: 74
- 2026-10-27: 74
- 2026-10-26: 73
- 2026-10-25: 73
- 2026-10-24: 72
- 2026-10-23: 72
- 2026-10-22: 71
- 2026-10-21: 71
- 2026-10-20: 70
- 2026-10-19: 70
- 2026-10-18: 69
- 2026-10-17: 69
- 2026-10-16: 68

## Common questions

### 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.

## Links

- Remote endpoint: https://counterpartycheck.com/mcp
- Authorisation metadata: https://counterpartycheck.com/.well-known/oauth-protected-resource/mcp
- Website: https://counterpartycheck.com/
- Changelog RSS feed: https://verifymcp.io/servers/chtwebllc-counterparty-check/counterpartycheck.xml
- Changelog JSON feed: https://verifymcp.io/servers/chtwebllc-counterparty-check/counterpartycheck.json
- HTML version of this page: https://verifymcp.io/servers/chtwebllc-counterparty-check/counterpartycheck