# VerifyDesk (remote · verifydesk.agenttoolworks.com)

Verify French and UK companies, EU VAT and IBANs; screen OFAC, UN, EU and UK sanctions lists.

- Trust score: 80/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-23

## Components

- remote · `verifydesk.agenttoolworks.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-agenttoolworks-verifydesk/verifydesk.md), [page](https://verifymcp.io/servers/com-agenttoolworks-verifydesk/verifydesk)

## Channel facts

- Endpoint: `https://verifydesk.agenttoolworks.com/mcp`
- Transports: `streamable-http`
- Auth: `required (not validated)`
- Version: `1.2.0`

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

- **Endpoint Security**: 71/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, but the challenge carries no valid RFC 9728 metadata, so a client cannot discover where to get a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1175 tokens (~195/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 77/100
  - Stability observed for 23 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the VerifyDesk MCP server?

VerifyDesk is a hosted endpoint at https://verifydesk.agenttoolworks.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 com-agenttoolworks-verifydesk 'https://verifydesk.agenttoolworks.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-agenttoolworks-verifydesk": {
      "url": "https://verifydesk.agenttoolworks.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-agenttoolworks-verifydesk": {
      "type": "http",
      "url": "https://verifydesk.agenttoolworks.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-agenttoolworks-verifydesk]
url = "https://verifydesk.agenttoolworks.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-agenttoolworks-verifydesk": {
      "type": "remote",
      "url": "https://verifydesk.agenttoolworks.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-agenttoolworks-verifydesk --url 'https://verifydesk.agenttoolworks.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-agenttoolworks-verifydesk:
    url: "https://verifydesk.agenttoolworks.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-agenttoolworks-verifydesk": {
      "Transport": "http",
      "Url": "https://verifydesk.agenttoolworks.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-agenttoolworks-verifydesk -t streamable-http -u 'https://verifydesk.agenttoolworks.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-agenttoolworks-verifydesk": {
      "type": "http",
      "url": "https://verifydesk.agenttoolworks.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-10-23 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-20 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 63 to 67. That category is still filling its 30-day observation window: 19 days of observed history at the previous scan, 20 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-18 (score 78, +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-10-16 (score 77, +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-14 (score 76, +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-12 (score 75, 0)

- [security] Tool “screen_sanctions” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 168 → 195
- [cosmetic] “screen_sanctions” added an optional parameter “min_score”
- [cosmetic] “screen_sanctions” reworded the description of “name”

### 2026-10-11 (score 75, +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-10 (score 74, 0)

- [security] Tool “validate_iban” rewrote its description, which is the text the model reads
- [security] Tool “verify_vat” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [cosmetic] “validate_iban” added an optional parameter “bic”
- [cosmetic] “verify_vat” added an optional parameter “requester_vat_number”
- [cosmetic] “validate_iban” reworded the description of “iban”
- [cosmetic] “verify_vat” reworded the description of “vat_number”
- [cosmetic] Tool “validate_iban” changed its title: Validate an IBAN → Validate an IBAN and BIC

## MCP tools (6)

### `verify_company` (~150 tokens)

Verify a company in an official registry

Verifies a company against its official state registry and returns its legal status. France (SIREN/SIRET) and the United Kingdom (Companies House company number) are supported. Input: country and a query that is either a registration number or a company name. Returns up to 5 normalized records: registration number, legal name, active/closed status, legal form, activity code, registered address, creation date. Costs 1 credit.

Input parameters:

- `country` (string, required): Registry to query: FR (France, SIRENE/RNE) or GB (UK Companies House)
- `query` (string, required): Registration number or company name, e.g. '552032534' or 'Danone'

### `verify_vat` (~273 tokens)

Validate an EU VAT number (VIES)

Validates an EU VAT number live against VIES (European Commission) and returns whether it is currently valid, with the registered name and address when the member state provides them. Input: the full VAT number with its country prefix, e.g. 'FR40303265045'. Optional: requester_vat_number, your own EU VAT number; VIES then issues a consultationNumber, its official proof that you made this check at checkedAt. If VIES or the member state is down, returns the last answer VIES gave us for that number within the past 7 days, marked stale: true with its original checkedAt and never a consultation number; with no such answer, a retryable error. Fresh answers carry stale: false. Light read: costs 0.2 credit.

Input parameters:

- `requester_vat_number` (string): Optional: YOUR OWN EU VAT number, with country prefix, e.g. 'DE811569869'. When given, VIES returns a consultationNumber proving the check. VIES refuses a requester it does not know as valid.
- `vat_number` (string, required): EU VAT number to check, with its 2-letter country prefix (EL for Greece, XI for Northern Ireland), e.g. 'FR40303265045'. Not an IBAN or a company registration number.

### `validate_iban` (~286 tokens)

Validate an IBAN and BIC

Validates an IBAN offline against the SWIFT IBAN Registry (Release 103, Sep 2026, all 89 countries): registered country, length, the national account format (BBAN), check digits 02-98 and the ISO 7064 mod-97 checksum. Returns valid, and when invalid a stable reason_code (malformed, unknown_country, wrong_length, bad_bban_format, bad_check_digits, checksum_failed) with a human reason; on a valid IBAN, the bank_code and branch_code the registry defines for that country. Optional bic: checks the ISO 9362 format and its country code, returned as bic.valid; a BIC country that differs from the IBAN country is a warnings entry, not an invalid result. 'valid' is about the IBAN only. This checks structure, not that the account or BIC exists. Light read: costs 0.2 credit.

Input parameters:

- `bic` (string): Optional BIC (SWIFT code) of the bank holding the account, 8 or 11 characters, e.g. 'COBADEFFXXX'. Checked for format and compared with the IBAN country.
- `iban` (string, required): IBAN to validate, spaces allowed, e.g. 'DE89 3704 0044 0532 0130 00'. Not a VAT number.

### `screen_sanctions` (~314 tokens)

Screen a name against sanctions lists

Screens a person or company name against official sanctions lists: OFAC SDN and OFAC Consolidated (US Treasury), the UN Security Council Consolidated List, the EU consolidated financial sanctions list and the UK Sanctions List, primary names and aliases. Matching ignores case, accents, punctuation, word order and legal forms (LLC, PJSC, GmbH), and tolerates one typo in a word of 4+ letters and common transliterations (Sergei, Sergey, Sergej). Each match has a score from 0 to 1 and a match_type (exact, alias, fuzzy); only scores at or above min_score (default 0.85) are returned, at most 10 designated parties. Always reports which lists were screened, which were unavailable and when each was last refreshed: keep 'data_as_of' with the result as evidence of the check. Latin-script names only; dates of birth, nationalities and addresses are not compared. A match is a signal for enhanced due diligence, never a legal determination. Costs 1 credit.

Input parameters:

- `min_score` (number): Optional. Lowest match score returned, 0.7 to 1, default 0.85. Lower finds more spelling variants and more false positives, higher fewer of both, e.g. 0.9
- `name` (string, required): Person or company name to screen, in Latin script, e.g. 'Rosneft Oil Company PJSC' or 'Sergei Aksyonov'

### `enrich_company` (~122 tokens)

Enrich a company with officers and registry details

Returns extended registry data for one company identified by its registration number: officers/directors currently in office (name and role), legal form, activity, address, headcount range when available. Input: country (FR or GB) and the exact registration number (SIREN for FR, company number for GB). Costs 1 credit.

Input parameters:

- `country` (string, required): Registry to query: FR (France, SIRENE/RNE) or GB (UK Companies House)
- `registration_number` (string, required): Exact SIREN (FR) or company number (GB)

### `get_usage` (~30 tokens)

Get usage and credit balance

Returns your current plan, remaining credit balance and call volume over the last 30 days. Free to call.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-agenttoolworks-verifydesk/verifydesk#diagnostics

## Score history

- 2026-10-23: 80
- 2026-10-22: 79
- 2026-10-21: 79
- 2026-10-20: 79
- 2026-10-19: 78
- 2026-10-18: 78
- 2026-10-17: 77
- 2026-10-16: 77
- 2026-10-15: 76
- 2026-10-14: 76
- 2026-10-13: 75
- 2026-10-12: 75
- 2026-10-11: 75
- 2026-10-10: 74
- 2026-10-06: 74
- 2026-10-05: 74
- 2026-10-04: 73
- 2026-10-03: 73
- 2026-10-02: 72
- 2026-10-01: 72
- 2026-09-30: 71

## Common questions

### What is the VerifyDesk MCP server?

VerifyDesk is an MCP server listed in the public MCP registry as com.agenttoolworks/verifydesk. Verify French and UK companies, EU VAT and IBANs; screen OFAC, UN, EU and UK sanctions lists. This page covers its hosted endpoint (https://verifydesk.agenttoolworks.com/mcp).

### Is the VerifyDesk MCP server safe to use?

VerifyDesk scores 80 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 VerifyDesk MCP server expose?

VerifyDesk exposes 6 tools: verify_company, verify_vat, validate_iban, screen_sanctions, enrich_company, get_usage. Their descriptions and schemas cost roughly 1,175 tokens of context every time the server is loaded.

### Does the VerifyDesk MCP server require authentication?

Yes. VerifyDesk asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the VerifyDesk MCP server still maintained?

VerifyDesk is still listed as active in the MCP registry. We last reached this channel on 23 October 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://verifydesk.agenttoolworks.com/mcp
- Authorisation metadata: https://verifydesk.agenttoolworks.com/.well-known/oauth-protected-resource/mcp
- Repository: https://github.com/agenttoolworks/mcp-servers
- Website: https://agenttoolworks.com/servers/verifydesk
- Changelog RSS feed: https://verifymcp.io/servers/com-agenttoolworks-verifydesk/verifydesk.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-agenttoolworks-verifydesk/verifydesk.json
- HTML version of this page: https://verifymcp.io/servers/com-agenttoolworks-verifydesk/verifydesk