Supplier Invoice Tool
REMOTE · SUPPLIER-INVOICE-TOOL.NEROLABS.WORKERS.DEV
Supplier invoices to draft Xero bills per job, for UK trades' AI assistants (test mode)
Available components
Last scanned (15 hours ago)
Scores higher than 45% of remote servers
Reachable. Last reached 21 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 Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (review_invoice). See how to fix → View diagnostics → Fail
- 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 Usability68
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1194 tokens (~85/item across 14 items; 14 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 46% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 15 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
Checks we ran (12)
- TLS certificate
- Authorization
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Checks we could not complete (1)
These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.
- HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
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.
- 21 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 13 to 17. That category is still filling its 30-day observation window: 4 days of observed history at the previous scan, 5 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Nov 26 +1
- Stability: unverified → 0.03 ▲ functional
- 13 Nov 26 57
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 21 Nov 2026 · Probed https://supplier-invoice-tool.nerolabs.workers.dev/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=nerolabs.workers.dev | CN=YE1,O=Let's Encrypt,C=US | 10 Nov 2026 | 8 Feb 2027 | ECDSA 256 | ECDSA-SHA384 | 6de4049323d6abaa327886d7b5c76757b3a |
| SANs: *.nerolabs.workers.dev, nerolabs.workers.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of supplier-invoice-tool.nerolabs.workers.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | DS published | 60074 | 8 | Verified |
| workers.dev. | No DS | 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://supplier-invoice-tool.nerolabs.workers.dev/mcp | Verified | 200 | |
| http (plaintext) | http://supplier-invoice-tool.nerolabs.workers.dev/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 →
add_supplier_invoices Add supplier invoices (emails, PDFs, photos) ~112
Add supplier invoices to the book: raw emails with PDF attachments, PDFs (text or scanned), photos, or pasted text, up to 25 per call. Each is read, checked against its own printed total, given its job reference, kept with its original, and checked for price changes against earlier invoices from the same supplier. Duplicates are skipped. Returns one result per document: added, needs_check (did not add up, held back), duplicate or failed.
| Name | Type | Req | Description |
|---|---|---|---|
| invoices | array | yes | – |
No output schema declared.
No examples provided.
assign_job_reference Put an invoice on a job ~59
Put an invoice (or some of its lines) on a job, when the supplier left the reference off or it was wrong.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
| job_reference | string | yes | – |
| line_numbers | array | – | – |
No output schema declared.
No examples provided.
connect_xero Get the Xero sign-in link ~36
A link for the trade to open and sign in to Xero. Test mode: only a Xero Demo Company can be connected.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
create_trade_account Create the business invoice book ~227
Start here, once per business. Creates the trade's invoice book and returns an API key to send as "Authorization: Bearer <key>" on every other call. Test mode: free, nothing is charged. The same identity (company number) can later sign the trade into Nero Work without a new sign up.
| Name | Type | Req | Description |
|---|---|---|---|
| company_number | string | – | Companies House number, if a limited company. Leave out for a sole trader. |
| job_reference_prefixes | array | – | Letters the trade puts before job numbers on orders, for example ["JOB", "HAUS"]. Default JOB, NW, REF. |
| job_reference_style | string | – | "number" (recommended when jobs are numbered): JOB-1042, Job 1042 and 1042 are all job 1042. "prefixed": keep JOB-1042 as written. |
| name | string | yes | Trading name, for example Spark & Sons Electrical Ltd. |
| vat_number | string | – | – |
| vat_registered | boolean | – | Default true. If false, bills are entered gross with no VAT. |
No output schema declared.
No examples provided.
disconnect_xero Forget the Xero connection ~22
Forget the Xero connection. Nothing in Xero is changed.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_account Show the business account and settings ~18
The trade's account, settings and Nero identity.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_original Link to an original invoice ~36
A private link to the original email, PDF or scan of one invoice, to show the trade.
| Name | Type | Req | Description |
|---|---|---|---|
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
list_invoices List the month's invoices ~44
Every invoice in the book for a month, with its lines, status and any problems.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | YYYY-MM, for example 2026-11. |
No output schema declared.
No examples provided.
month_summary Month summary: draft bills per supplier and job ~82
The month at a glance: one draft bill per supplier with a line per job (net, VAT and which invoices), invoices held back to check, lines with no job reference, and price changes with the extra cost they caused. Includes the exact Xero payloads. Sends nothing.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | YYYY-MM, for example 2026-11. |
No output schema declared.
No examples provided.
price_alerts Supplier price changes this month ~50
Price changes on the same product code from the same supplier this month, in date order, and the extra they cost.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | YYYY-MM, for example 2026-11. |
No output schema declared.
No examples provided.
push_bills_to_xero Put the month's bills into Xero as drafts ~137
Put the month's bills into Xero as DRAFT bills, one per supplier, one line per job, with the original invoices attached. Without send: true it is a dry run that shows what would be sent. Running it again updates the same draft (no duplicates). A bill the trade has already approved is never changed; late invoices go on a top up bill. Never approves or pays.
| Name | Type | Req | Description |
|---|---|---|---|
| month | string | yes | YYYY-MM, for example 2026-11. |
| send | boolean | – | true to really add the drafts. Default false (dry run). |
| suppliers | array | – | Only these suppliers. |
No output schema declared.
No examples provided.
review_invoice Accept or remove an invoice held for checking ~61
For an invoice held back as needs_check: accept it as read (it then goes on the bill), or remove it (for example to add a corrected copy). Ask the trade first.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | yes | – |
| invoice_id | string | yes | – |
No output schema declared.
No examples provided.
update_settings Change job reference and Xero settings ~65
Change how job references are read and how bills are entered in Xero.
| Name | Type | Req | Description |
|---|---|---|---|
| company_number | string | – | – |
| job_reference_prefixes | array | – | – |
| job_reference_style | string | – | – |
| settings | object | – | – |
| vat_number | string | – | – |
No output schema declared.
No examples provided.
xero_status Check the Xero connection ~20
Whether Xero is connected, and to which organisation.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Supplier Invoice Tool MCP server?
Supplier Invoice Tool is a hosted endpoint at https://supplier-invoice-tool.nerolabs.workers.dev/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 · supplier-invoice-tool.nerolabs.workers.dev
claude mcp add --transport http nero-engine-supplier-invoice-tool 'https://supplier-invoice-tool.nerolabs.workers.dev/mcp'
What is the Supplier Invoice Tool MCP server?
Supplier Invoice Tool is an MCP server listed in the public MCP registry as io.github.Nero-Engine/supplier-invoice-tool. Supplier invoices to draft Xero bills per job, for UK trades' AI assistants (test mode). This page covers its hosted endpoint (https://supplier-invoice-tool.nerolabs.workers.dev/mcp).
Is the Supplier Invoice Tool MCP server safe to use?
Supplier Invoice Tool scores 61 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 Supplier Invoice Tool MCP server expose?
Supplier Invoice Tool exposes 14 tools: create_trade_account, get_account, update_settings, add_supplier_invoices, month_summary, and 9 more. Their descriptions and schemas cost roughly 969 tokens of context every time the server is loaded.
Does the Supplier Invoice Tool MCP server require authentication?
No. We connected to Supplier Invoice Tool without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Supplier Invoice Tool MCP server still maintained?
Supplier Invoice Tool is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What did VerifyMCP test on the Supplier Invoice Tool MCP server?
VerifyMCP ran 12 checks on Supplier Invoice Tool, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Supplier Invoice Tool: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.