Invoice & Payment ID Validator
REMOTE · INVOICE-VALIDATOR.MOHAMED-BAHAA53000.WORKERS.DEV · 2 COMPONENTS
Pay/review/hold verdict for invoice payees: cross-checks IBAN, BIC, VAT, EIN. Paid: RapidAPI
Last scanned (16 hours ago)
Scores higher than 59% of remote servers
Reachable. Last reached 22 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 Security63
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- 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 Usability77
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 735 tokens (~122/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 Management13
- Stability observed for 4 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 7 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.
- 22 Oct 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.
- 20 Oct 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.
- 19 Oct 26 0
- Stability: unverified → 0.03 ▲ functional
- 18 Oct 26 67
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 22 Oct 2026 · Probed https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=mohamed-bahaa53000.workers.dev | CN=WE1,O=Google Trust Services,C=US | 3 Oct 2026 | 1 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 47240052cd2434ee13434869a0b4b51b |
| SANs: mohamed-bahaa53000.workers.dev, *.mohamed-bahaa53000.workers.dev | ||||||
| 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 invoice-validator.mohamed-bahaa53000.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| workers.dev. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp | Verified | 200 | |
| http (plaintext) | http://invoice-validator.mohamed-bahaa53000.workers.dev/demo/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 →
check_invoice_payee Check an invoice payee (pay / review / hold) ~268
One call before paying a supplier: validates the IBAN, BIC, VAT (EU or UK) and EIN on the invoice AND cross-checks them against each other and the supplier's country, then returns verdict pay / review / hold with plain-English reasons. Catches the changed-bank-details fraud pattern (e.g. a German supplier asking to be paid into a foreign account), BIC/IBAN country mismatches, unregistered VAT numbers, and (with live=true) a VIES-registered company name that doesn't match the supplier name. Pass whatever the invoice has; only one field is needed.
| Name | Type | Req | Description |
|---|---|---|---|
| bic | string | – | BIC/SWIFT from the invoice |
| currency | string | – | Invoice currency |
| ein | string | – | US EIN, if any |
| iban | string | – | Supplier IBAN from the invoice |
| live | boolean | – | Also check the VAT number in the official EU VIES registry |
| supplier_country | string | – | ISO country of the supplier as you know it (from your vendor master, not the invoice) |
| supplier_name | string | – | Supplier legal name, compared with the VIES-registered name when live=true |
| vat | string | – | Supplier VAT ID (EU with country prefix, or GB...) |
No output schema declared.
No examples provided.
validate_bic Validate BIC / SWIFT ~88
Validate a BIC/SWIFT code (8 or 11 chars): structure, ISO country, test-BIC flag. Pass the IBAN too and it checks that the BIC country matches the IBAN country (a common fraud/typo signal).
| Name | Type | Req | Description |
|---|---|---|---|
| iban | string | – | Optional IBAN to cross-check country |
| value | string | yes | BIC/SWIFT code |
No output schema declared.
No examples provided.
validate_ein Validate US EIN ~61
Validate a US Employer Identification Number: 9-digit format and a valid IRS campus prefix. EINs have no check digit, so this catches typos and fake prefixes, not every invalid number.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | EIN, with or without dash |
No output schema declared.
No examples provided.
validate_eu_vat Validate EU VAT number ~95
Validate an EU VAT ID (27 member states + XI): format and check digit offline. Set live=true to also query the EU VIES registry for registration status, company name and address (slower, may be throttled; failures return vies.checked=false, never a false 'invalid').
| Name | Type | Req | Description |
|---|---|---|---|
| live | boolean | – | Also check the official VIES registry |
| value | string | yes | VAT ID with country prefix |
No output schema declared.
No examples provided.
validate_gb_vat Validate UK VAT number ~55
Validate a UK (GB) VAT registration number: format, branch/government/health-authority types, and the HMRC mod-97 / 9755 checksum.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | UK VAT number |
No output schema declared.
No examples provided.
validate_iban Validate IBAN ~76
Validate an International Bank Account Number: mod-97 checksum, length for its country (100+ countries), SEPA membership. Returns the normalized and formatted IBAN, country and BBAN, or machine-readable error codes. Use before paying an invoice or saving supplier bank details.
| Name | Type | Req | Description |
|---|---|---|---|
| value | string | yes | IBAN, spaces allowed |
No output schema declared.
No examples provided.
How do I install the Invoice & Payment ID Validator MCP server?
Invoice & Payment ID Validator is a hosted endpoint at https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/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 · invoice-validator.mohamed-bahaa53000.workers.dev
claude mcp add --transport http dev-workers-mohamed-bahaa53000-invoice-validator 'https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp'
What is the Invoice & Payment ID Validator MCP server?
Invoice & Payment ID Validator is an MCP server listed in the public MCP registry as dev.workers.mohamed-bahaa53000.invoice-validator/invoice-pa…. Pay/review/hold verdict for invoice payees: cross-checks IBAN, BIC, VAT, EIN. Paid: RapidAPI. This page covers its hosted endpoint (https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp).
Is the Invoice & Payment ID Validator MCP server safe to use?
Invoice & Payment ID Validator scores 69 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 Invoice & Payment ID Validator MCP server expose?
Invoice & Payment ID Validator exposes 6 tools: check_invoice_payee, validate_iban, validate_bic, validate_eu_vat, validate_gb_vat, validate_ein. Their descriptions and schemas cost roughly 643 tokens of context every time the server is loaded.
Does the Invoice & Payment ID Validator MCP server require authentication?
No. We connected to Invoice & Payment ID Validator without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Invoice & Payment ID Validator MCP server still maintained?
Invoice & Payment ID Validator is still listed as active in the MCP registry. We last reached this channel on 22 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.