Malaysia MyInvois Invoice Builder — connector documentation

MCP endpoint: https://my-einvoice-builder.connectorbay.com/mcp
REST API: POST https://my-einvoice-builder.connectorbay.com/v1/tools/{tool_name}, described by the OpenAPI 3.1 spec at https://my-einvoice-builder.connectorbay.com/openapi.json
Transport: Streamable HTTP, stateless, MCP specification 2025-06-18 or later
Authentication: none required. An optional Authorization: Bearer <key> raises rate limits.
Health: https://my-einvoice-builder.connectorbay.com/health · Tool schemas: https://my-einvoice-builder.connectorbay.com/tools.json
Publisher: Unify Dynamics LLC · connectorbay.com/my-einvoice-builder · agent@connectorbay.com

What Malaysia MyInvois Invoice Builder is for

Malaysia MyInvois Invoice Builder helps an owner's agent prepare and check e-invoice documents for the LHDN MyInvois system without credentials. build_einvoice_json turns plain supplier, buyer and line-item details into an unsigned Invoice v1.1 JSON draft in the SDK wire format (UBL 2.1 style), with line and document totals computed exactly in decimals. validate_einvoice checks a document against the field list, lengths and code tables of the SDK Invoice v1.1 page and adds arithmetic consistency findings. lookup_code returns the SDK code tables for document types, payment modes, tax types, classification codes and state codes. list_document_types shows the eight document type codes. tin_format_check checks the shape of a TIN and registration number without any registry lookup. validation_link_and_qr builds the validation link pattern the SDK FAQ gives for the printed QR code. explain_submission_flow gives the sandbox and production hosts, login endpoints, rate limits and size limits. Every code, limit and field rule was read from the public MyInvois SDK on 29 September 2026 and carries its source, date and verification level; nothing is submitted, signed or stored. The Invoice v1.1 structure is modelled; credit, debit, refund and self-billed structures were not read. Independent; not affiliated with LHDN or the Inland Revenue Board of Malaysia.

Ask your assistant things like:

"Turn these line items into a MyInvois invoice JSON draft with 10% sales tax."
"Check this MyInvois JSON invoice: are required fields, codes and totals right?"
"What is the MyInvois payment mode code for an e-wallet?"
"Which MyInvois document type is a self-billed credit note?"
"How many invoices and how many megabytes may one MyInvois submission hold, and what are the sandbox hosts?"
"What link goes into the QR code once an invoice is validated?"

What it does

build_einvoice_json: Build an unsigned MyInvois Invoice v1.1 JSON draft from supplier, buyer and line items, with exact totals.
validate_einvoice: Check a MyInvois Invoice v1.1 JSON document against the SDK field list, lengths and code tables, with arithmetic consistency findings.
lookup_code: Look up an SDK code table (document type, payment mode, tax type, classification, state) by code or by words.
list_document_types: The eight MyInvois e-invoice document type codes with the structure pages this connector has read.
tin_format_check: Check the shape of a TIN and a registration number against the SDK field limits, with no registry lookup.
validation_link_and_qr: Build the validation link pattern the SDK FAQ gives for the printed QR code, for sandbox or production.
explain_submission_flow: Hosts, login endpoints, token validity, rate limits, size limits and the intermediary route as the SDK states them.

Data sources

Reference data from official sources (sdk.myinvois.hasil.gov.my); every answer states its source, date and validity period.

What it is not

Malaysia MyInvois Invoice Builder is independent; not affiliated with, endorsed by or operated by any government body, central bank, standards body or scheme operator. Names of rails, schemes and standards are used only to say what a tool works with. It is read-only: it never sends, pays, files or signs anything for you, and it never looks up private individuals.

Not advice. General information only, not legal, tax, accounting or payment advice. Malaysia MyInvois Invoice Builder is an independent tool: it is not affiliated with, endorsed by or operated by any government body, central bank, standards body or scheme operator. Rates, thresholds and rules change; check the cited official source and confirm with a qualified professional before you rely on a result.

Built for: Malaysia. Languages: English.

Tools

Look up & validate

validate_einvoice — Check a MyInvois Invoice v1.1 JSON document against the SDK field list, lengths and code tables, with arithmetic consistency findings. Use for "Check this MyInvois JSON invoice: are required fields, codes and totals right". Args: document.

lookup_code — Look up an SDK code table (document type, payment mode, tax type, classification, state) by code or by words. Use for "What is the MyInvois payment mode code for an e-wallet", "Which MyInvois document type is a self-billed credit note". Args: table, code, query.

list_document_types — The eight MyInvois e-invoice document type codes with the structure pages this connector has read. Use for "Which MyInvois document type is a self-billed credit note".

Build & format

build_einvoice_json — Build an unsigned MyInvois Invoice v1.1 JSON draft from supplier, buyer and line items, with exact totals. Use for "Turn these line items into a MyInvois invoice JSON draft with 10% sales tax". Args: invoice_number, issue_date, issue_time, supplier, buyer, lines, currency, exchange_rate, payment_mode, supplier_bank_account, payment_terms.

Reference & guides

tin_format_check — Check the shape of a TIN and a registration number against the SDK field limits, with no registry lookup. Use for "Is this TIN string shaped correctly for MyInvois, and is the registration number within its length limit". Args: tin, id_type, id_value.

validation_link_and_qr — Build the validation link pattern the SDK FAQ gives for the printed QR code, for sandbox or production. Use for "What URL goes into the QR code for a validated document with this UUID and long ID". Args: document_uuid, long_id, environment.

explain_submission_flow — Hosts, login endpoints, token validity, rate limits, size limits and the intermediary route as the SDK states them. Use for "What are the MyInvois sandbox and production hosts, and how many invoices and bytes can one submission carry".

Conventions

Read-only. Every tool reads public data or computes; nothing is written anywhere and nothing about the user is stored.
Result envelope. ok: true with data, or ok: false with a structured error (bad_input, not_found, upstream_error). degraded lists optional sources that were unreachable.
Rate limits. Free tier 60 tool calls/minute and 300/day per user (keyed on the user identifier supplied by the host agent, else client IP); Pro keys raise this. Over-limit calls return HTTP 429 with Retry-After. initialize and tools/list are never counted.

Support

agent@connectorbay.com · connectorbay.com/my-einvoice-builder/support