VerifyDesk
REMOTE · VERIFYDESK.AGENTTOOLWORKS.COM
Verify French and UK companies, EU VAT and IBANs; screen OFAC, UN, EU and UK sanctions lists.
Available components
Last scanned (4 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 23 Oct 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 Security71
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Fail
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management77
- Stability observed for 23 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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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.
- 23 Oct 26 +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.
- 20 Oct 26 +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.
- 18 Oct 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.
- 16 Oct 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.
- 14 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.
- 12 Oct 26 0
- Tool “screen_sanctions” rewrote its description, which is the text the model reads security
- Schema quality: 168 → 195 ▼ functional
- “screen_sanctions” added an optional parameter “min_score” cosmetic
- “screen_sanctions” reworded the description of “name” cosmetic
- 11 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.
- 10 Oct 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- “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 cosmetic
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 23 Oct 2026 · Probed https://verifydesk.agenttoolworks.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=agenttoolworks.com | CN=WE1,O=Google Trust Services,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | ec596cee176306430ed390046015b077 |
| SANs: agenttoolworks.com, verifydesk.agenttoolworks.com, *.verifydesk.agenttoolworks.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of verifydesk.agenttoolworks.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| agenttoolworks.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication Challenged, unverified
The endpoint asked for a token, but we could not retrieve and validate the RFC 9728 metadata that tells a client how to obtain one.
| Result | Challenged, unverified |
|---|---|
| Enforced | On tool calls |
| HTTP status | 200 |
Protected resource metadata
| Retrieved | No |
|---|---|
| Problem | no_resource_metadata |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://verifydesk.agenttoolworks.com/mcp | Verified | 200 | |
| http (plaintext) | http://verifydesk.agenttoolworks.com/mcp | Inconclusive | 405 |
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 →
enrich_company Enrich a company with officers and registry details ~122
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Registry to query: FR (France, SIRENE/RNE) or GB (UK Companies House) |
| registration_number | string | yes | Exact SIREN (FR) or company number (GB) |
No output schema declared.
No examples provided.
get_usage Get usage and credit balance ~30
Returns your current plan, remaining credit balance and call volume over the last 30 days. Free to call.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
screen_sanctions Screen a name against sanctions lists ~314
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | Person or company name to screen, in Latin script, e.g. 'Rosneft Oil Company PJSC' or 'Sergei Aksyonov' |
No output schema declared.
No examples provided.
validate_iban Validate an IBAN and BIC ~286
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | IBAN to validate, spaces allowed, e.g. 'DE89 3704 0044 0532 0130 00'. Not a VAT number. |
No output schema declared.
No examples provided.
verify_company Verify a company in an official registry ~150
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.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | Registry to query: FR (France, SIRENE/RNE) or GB (UK Companies House) |
| query | string | yes | Registration number or company name, e.g. '552032534' or 'Danone' |
No output schema declared.
No examples provided.
verify_vat Validate an EU VAT number (VIES) ~273
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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. |
No output schema declared.
No examples provided.
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.
remote · verifydesk.agenttoolworks.com
claude mcp add --transport http com-agenttoolworks-verifydesk 'https://verifydesk.agenttoolworks.com/mcp'
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.