Ha Tang docs and API for agents: email, VietQR payments, e-invoices, support inbox (Vietnam).
GCC e-Invoice Preflight Oracle is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Validate UAE PINT AE and Saudi ZATCA e-invoices: UBL, official Schematron, QR, fix hints.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http gcc-e-invoice-preflight-oracle-mcp https://einvoice.noahsarch.tech/mcp
# 2 — ask your agent for something these tools do
# validate_invoice, readiness_report, extract_summary and 4 more
GCC e-Invoice Preflight Oracle costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http gcc-e-invoice-preflight-oracle-mcp https://einvoice.noahsarch.tech/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take X-API-Key header (API key from contact@noahsarch.tech (catalogue and free tools work without it)) if you want to set it. Its publisher says some of its tools need it, and the rest work without.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
7 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 | ACC
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | The UBL 2.1 Invoice or CreditNote XML as a string. |
| jurisdiction | string | no | 'ae' PINT AE Billing, 'ae-sb' PINT AE Self-Billing, 'sa' ZATCA (KSA), or 'auto' (from CustomizationID / ProfileID). |
| preflight | boolean | no | Also run the advisory Noah's Arch checks (nae-*/nksa-*: TRN/TIN consistency, emirate codes, VAT rates, totals cross-check, dates). |
| include_info | boolean | no | Include info-level notes (e.g. test-data TRNs). |
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, rul
| Parameter | Type | Required | Notes |
|---|---|---|---|
| documents | array | yes | Up to 100 documents. |
| jurisdiction | string | no | — |
| preflight | boolean | no | — |
| format | string | no | 'html' adds a self-contained printable report in result.html. |
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 vers
| Parameter | Type | Required | Notes |
|---|---|---|---|
| xml | string | yes | — |
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 | pre
| Parameter | Type | Required | Notes |
|---|---|---|---|
| jurisdiction | string | no | — |
| severity | no | — | |
| contains | no | Filter by text, e.g. 'TaxPointDate', 'ibr-co', 'BTAE-16'. |
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 t
| Parameter | Type | Required | Notes |
|---|---|---|---|
| trn | string | yes | UAE Tax Registration Number as printed (spaces/dashes allowed). |
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_c
| Parameter | Type | Required | Notes |
|---|---|---|---|
| qr | string | yes | Base64 TLV content of a ZATCA QR code. |
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_confid
| Parameter | Type | Required | Notes |
|---|---|---|---|
| seller_name | string | yes | — |
| vat_number | string | yes | KSA VAT number: 15 digits, starts and ends with 3. |
| timestamp | string | yes | ISO 8601, e.g. 2026-10-31T14:05:00Z |
| total_with_vat | string | yes | e.g. '1150.00' |
| vat_total | string | yes | e.g. '150.00' |
| invoice_hash | no | Base64 SHA-256 of the invoice (phase 2). | |
| ecdsa_signature | no | Base64 (phase 2). | |
| public_key | no | Base64 (phase 2). | |
| certificate_signature | no | Base64 (phase 2, simplified invoices). |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install GCC e-Invoice Preflight Oracle or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| validate_invoice | no tags | |
| readiness_report | no tags | |
| extract_summary | no tags | |
| list_rules | no tags | |
| check_trn | no tags | |
| zatca_qr_decode | no tags | |
| zatca_qr_encode | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 0.1.1.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish GCC e-Invoice Preflight Oracle can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.