GCC e-Invoice Preflight Oracle
REMOTE · EINVOICE.NOAHSARCH.TECH
Validate UAE PINT AE and Saudi ZATCA e-invoices: UBL, official Schematron, QR, fix hints.
Available components
Last scanned (2 hours ago)
Scores higher than 53% of remote servers
Reachable. Last reached 5 Nov 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 406, 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 Usability74
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1759 tokens (~195/item across 9 items; 7 tools + 2 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 Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage93
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 74% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a current MCP spec version (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.
- 4 Nov 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.
- 2 Nov 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.
- 1 Nov 26 0
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 66
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 5 Nov 2026 · Probed https://einvoice.noahsarch.tech/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=noahsarch.tech | CN=WE1,O=Google Trust Services,C=US | 15 Oct 2026 | 14 Jan 2027 | ECDSA 256 | ECDSA-SHA256 | 470026e1ea46ecc0e06d5a5a9df0965 |
| SANs: noahsarch.tech, *.noahsarch.tech | ||||||
| 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 einvoice.noahsarch.tech. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| tech. | present | 2185 | 13 | Verified |
| noahsarch.tech. | 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://einvoice.noahsarch.tech/mcp | Verified | 200 | |
| http (plaintext) | http://einvoice.noahsarch.tech/mcp | Inconclusive | 406 |
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_trn Check a UAE TRN and derive the Peppol endpoint ~168
Format check of a UAE Tax Registration Number (15 digits) and derivation of the TIN / Peppol participant identifier (scheme 0235 = first 10 digits). Free. Example: trn '100 1234 5670 0003'. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| trn | string | yes | UAE Tax Registration Number as printed (spaces/dashes allowed). |
Structured output declared, but exposes no named fields.
No examples provided.
extract_summary Read the key fields of a UBL invoice ~145
Seller/buyer (names, TRN, endpoint, legal registration, emirate), dates, currency, totals, VAT breakdown, line count, payment means, attachments and the detected rule set — without validating. Free. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| xml | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
list_rules List the official PINT AE rules ~186
Rule ids, severities and texts from the installed PINT AE Schematron (shared PINT rules and the -ae jurisdiction rules), filterable by severity or text, with fix hints where we have them. Free. Example: contains 'TaxPointDate'. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| contains | – | – | Filter by text, e.g. 'TaxPointDate', 'ibr-co', 'BTAE-16'. |
| jurisdiction | string | – | – |
| severity | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
readiness_report Validate up to 100 e-invoices and summarise readiness ~180
Batch preflight for a go-live check or an ERP regression suite: per-document verdicts, readiness percentage, the most frequent rejection rules across the batch, optional printable HTML. Charged per document. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| documents | array | yes | Up to 100 documents. |
| format | string | – | 'html' adds a self-contained printable report in result.html. |
| jurisdiction | string | – | – |
| preflight | boolean | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
validate_invoice Validate one e-invoice (UAE PINT AE / KSA ZATCA) ~317
Full preflight of one UBL Invoice or CreditNote: XML well-formedness, UBL 2.1 XSD, the official PINT AE Schematron (≈300 rules incl. the UAE jurisdiction overlay) or the ZATCA pre-check, plus advisory cross-checks. Returns a verdict and every finding with rule id, severity, fields, location and fix hint. Example: xml '<Invoice …>', jurisdiction 'auto'. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| include_info | boolean | – | Include info-level notes (e.g. test-data TRNs). |
| jurisdiction | string | – | 'ae' PINT AE Billing, 'ae-sb' PINT AE Self-Billing, 'sa' ZATCA (KSA), or 'auto' (from CustomizationID / ProfileID). |
| preflight | boolean | – | Also run the advisory Noah's Arch checks (nae-*/nksa-*: TRN/TIN consistency, emirate codes, VAT rates, totals cross-check, dates). |
| xml | string | yes | The UBL 2.1 Invoice or CreditNote XML as a string. |
Structured output declared, but exposes no named fields.
No examples provided.
zatca_qr_decode Decode a ZATCA QR (TLV) ~156
Decode the base64 TLV of a Saudi e-invoice QR into seller name, VAT number, timestamp, totals, hash, signature and key tags, with phase detection and format issues. Free. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| qr | string | yes | Base64 TLV content of a ZATCA QR code. |
Structured output declared, but exposes no named fields.
No examples provided.
zatca_qr_encode Build a ZATCA QR (TLV) payload ~290
Encode the five phase-1 fields (plus optional phase-2 hash/signature/key tags) into the base64 TLV string that goes into the QR image and the UBL QR reference. Free. Response: result with verdict (ACCEPTED | ACCEPTED_WITH_WARNINGS | REJECTED), findings[] (id, severity, message, fields, location, fix_hint, source = xsd | schematron | preflight), counts, ruleset version and timings, plus data_confidence, estimated_items[], sources[], data_version, warnings[] and a disclaimer. Documents are validated in memory and never stored or logged.
| Name | Type | Req | Description |
|---|---|---|---|
| certificate_signature | – | – | Base64 (phase 2, simplified invoices). |
| ecdsa_signature | – | – | Base64 (phase 2). |
| invoice_hash | – | – | Base64 SHA-256 of the invoice (phase 2). |
| public_key | – | – | Base64 (phase 2). |
| seller_name | string | yes | – |
| timestamp | string | yes | ISO 8601, e.g. 2026-10-31T14:05:00Z |
| total_with_vat | string | yes | e.g. '1150.00' |
| vat_number | string | yes | KSA VAT number: 15 digits, starts and ends with 3. |
| vat_total | string | yes | e.g. '150.00' |
Structured output declared, but exposes no named fields.
No examples provided.
How do I install the GCC e-Invoice Preflight Oracle MCP server?
GCC e-Invoice Preflight Oracle is a hosted endpoint at https://einvoice.noahsarch.tech/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 · einvoice.noahsarch.tech
claude mcp add --transport http tech-noahsarch-einvoice-preflight 'https://einvoice.noahsarch.tech/mcp'
What is the GCC e-Invoice Preflight Oracle MCP server?
GCC e-Invoice Preflight Oracle is an MCP server listed in the public MCP registry as tech.noahsarch/einvoice-preflight. Validate UAE PINT AE and Saudi ZATCA e-invoices: UBL, official Schematron, QR, fix hints. This page covers its hosted endpoint (https://einvoice.noahsarch.tech/mcp).
Is the GCC e-Invoice Preflight Oracle MCP server safe to use?
GCC e-Invoice Preflight Oracle scores 68 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 GCC e-Invoice Preflight Oracle MCP server expose?
GCC e-Invoice Preflight Oracle exposes 7 tools: validate_invoice, readiness_report, extract_summary, list_rules, check_trn, and 2 more. Their descriptions and schemas cost roughly 1,442 tokens of context every time the server is loaded.
Does the GCC e-Invoice Preflight Oracle MCP server require authentication?
No. We connected to GCC e-Invoice Preflight Oracle without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the GCC e-Invoice Preflight Oracle MCP server still maintained?
GCC e-Invoice Preflight Oracle is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.