Invoice & Payment ID Validator MCP server
dev.workers.mohamed-bahaa53000.invoice-validator/invoice-payment-id-validatorinvoice-validator.mohamed-bahaa53000.workers.devstreamable-httpv1.2.1Scanned
Pay/review/hold verdict for invoice payees: cross-checks IBAN, BIC, VAT, EIN. Paid: RapidAPI
6 tools: 1 change things and 5 only read.
- Reads private data · 0
- Reads text others write · 2
- Can send data out · 0
- No findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here changes things. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Invoice & Payment ID Validator MCP server can do
The Invoice & Payment ID Validator MCP server is published by invoice-validator.mohamed-bahaa53000.workers.dev, a domain the MCP Registry verified. It has 6 tools. It can create or change data (1 tool: check_invoice_payee), but cannot delete data. 5 tools only read.
2 tools bring in text other people can write (check_invoice_payee and validate_eu_vat).
None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 11, 2026, version 1.2.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
6 tools
Changes things 1Claude Code: ask
check_invoice_payeeOne 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 …Reads text others writeNo findings
Why it is in this group
- Nothing in its name or description says what it does, so it is counted as a write.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
Only reads 5Show 5 read-only tools
validate_bicValidate a BIC/SWIFT code (8 or 11 chars): structure, ISO country, test-BIC flag.No findings
Why it is in this group
- The name "validate_bic" says "validate": a word for reading.
Description, as the server wrote it 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).
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_einValidate a US Employer Identification Number: 9-digit format and a valid IRS campus prefix.No findings
Why it is in this group
- The name "validate_ein" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_eu_vatValidate an EU VAT ID (27 member states + XI): format and check digit offline.Reads text others writeNo findings
Why it is in this group
- The name "validate_eu_vat" says "validate": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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').
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
validate_gb_vatValidate a UK (GB) VAT registration number: format, branch/government/health-authority types, and the HMRC mod-97 / 9755 checksum.No findings
Why it is in this group
- The name "validate_gb_vat" says "validate": a word for reading.
Description, as the server wrote it Validate a UK (GB) VAT registration number: format, branch/government/health-authority types, and the HMRC mod-97 / 9755 checksum.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
validate_ibanValidate an International Bank Account Number: mod-97 checksum, length for its country (100+ countries), SEPA membership.No findings
Why it is in this group
- The name "validate_iban" says "validate": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write2
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:53 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 1
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcp: tools/list returned 6 tools to an anonymous client, including check_invoice_payee (write)
Findings
Matches of fixed checks, with the text they matched.
No check matched anything in these tool definitions. That is not a safety guarantee.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http invoice-payment-id-validator https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcpclaude mcp add --transport http invoice-payment-id-validator https://invoice-validator.mohamed-bahaa53000.workers.dev/demo/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__invoice-payment-id-validator__validate_iban",
"mcp__invoice-payment-id-validator__validate_bic",
"mcp__invoice-payment-id-validator__validate_eu_vat",
"mcp__invoice-payment-id-validator__validate_gb_vat",
"mcp__invoice-payment-id-validator__validate_ein"
],
"ask": [
"mcp__invoice-payment-id-validator__check_invoice_payee"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as invoice-payment-id-validator. Review it before you use it.
Capability tags behind 2 rules
- mcp__invoice-payment-id-validator__check_invoice_payee untrusted-input
- mcp__invoice-payment-id-validator__validate_eu_vat untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/dev.workers.mohamed-bahaa53000.invoice-validator/invoice-payment-id-validator/verify?hash=833461e87ec1559644c64f92dcc08fd334afcf022bdf8184ca405dbba56839a7" | jq -e '.changed == false'Pinned hash 833461e87ec1, from Nov 11, 2026, 11:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/dev.workers.mohamed-bahaa53000.invoice-validator/invoice-payment-id-validator/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/dev.workers.mohamed-bahaa53000.invoice-validator/invoice-payment-id-validator)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:12 UTC.
Invoice & Payment ID Validator MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Invoice & Payment ID Validator MCP server safe?
- No scan can promise that. What its definitions show: 6 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Invoice & Payment ID Validator MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Invoice & Payment ID Validator MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Invoice & Payment ID Validator MCP server have?
- 6 tools: 1 write, 5 read. check_invoice_payee, validate_iban, validate_bic, validate_eu_vat, validate_gb_vat and validate_ein.
Does the Invoice & Payment ID Validator MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Invoice & Payment ID Validator MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Invoice & Payment ID Validator MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 11, 2026.