# 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)

- Trust score: 61/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `supplier-invoice-tool.nerolabs.workers.dev`: 61/100 (this document), [markdown](https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool.md), [page](https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool)

## Channel facts

- Endpoint: `https://supplier-invoice-tool.nerolabs.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Endpoint Security**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (review_invoice).
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 68/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1194 tokens (~85/item across 14 items; 14 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 46% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 14 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 15 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### 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.

### Claude

```bash
claude mcp add --transport http nero-engine-supplier-invoice-tool 'https://supplier-invoice-tool.nerolabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "nero-engine-supplier-invoice-tool": {
      "url": "https://supplier-invoice-tool.nerolabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "nero-engine-supplier-invoice-tool": {
      "type": "http",
      "url": "https://supplier-invoice-tool.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.nero-engine-supplier-invoice-tool]
url = "https://supplier-invoice-tool.nerolabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "nero-engine-supplier-invoice-tool": {
      "type": "remote",
      "url": "https://supplier-invoice-tool.nerolabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add nero-engine-supplier-invoice-tool --url 'https://supplier-invoice-tool.nerolabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  nero-engine-supplier-invoice-tool:
    url: "https://supplier-invoice-tool.nerolabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "nero-engine-supplier-invoice-tool": {
      "Transport": "http",
      "Url": "https://supplier-invoice-tool.nerolabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add nero-engine-supplier-invoice-tool -t streamable-http -u 'https://supplier-invoice-tool.nerolabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "nero-engine-supplier-invoice-tool": {
      "type": "http",
      "url": "https://supplier-invoice-tool.nerolabs.workers.dev/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-21 (score 61, +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.

### 2026-11-18 (score 60, +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.

### 2026-11-16 (score 59, +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.

### 2026-11-14 (score 58, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-13 (score 57)

First indexed and scored.

## MCP tools (14)

### `create_trade_account` (~227 tokens)

Create the business invoice book

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.

Input parameters:

- `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, required): 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.

### `get_account` (~18 tokens)

Show the business account and settings

The trade's account, settings and Nero identity.

### `update_settings` (~65 tokens)

Change job reference and Xero settings

Change how job references are read and how bills are entered in Xero.

Input parameters:

- `company_number` (string)
- `job_reference_prefixes` (array)
- `job_reference_style` (string)
- `settings` (object)
- `vat_number` (string)

### `add_supplier_invoices` (~112 tokens)

Add supplier invoices (emails, PDFs, photos)

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.

Input parameters:

- `invoices` (array, required)

### `month_summary` (~82 tokens)

Month summary: draft bills per supplier and job

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.

Input parameters:

- `month` (string, required): YYYY-MM, for example 2026-11.

### `list_invoices` (~44 tokens)

List the month's invoices

Every invoice in the book for a month, with its lines, status and any problems.

Input parameters:

- `month` (string, required): YYYY-MM, for example 2026-11.

### `price_alerts` (~50 tokens)

Supplier price changes this month

Price changes on the same product code from the same supplier this month, in date order, and the extra they cost.

Input parameters:

- `month` (string, required): YYYY-MM, for example 2026-11.

### `get_original` (~36 tokens)

Link to an original invoice

A private link to the original email, PDF or scan of one invoice, to show the trade.

Input parameters:

- `invoice_id` (string, required)

### `assign_job_reference` (~59 tokens)

Put an invoice on a job

Put an invoice (or some of its lines) on a job, when the supplier left the reference off or it was wrong.

Input parameters:

- `invoice_id` (string, required)
- `job_reference` (string, required)
- `line_numbers` (array)

### `review_invoice` (~61 tokens)

Accept or remove an invoice held for checking

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.

Input parameters:

- `action` (string, required)
- `invoice_id` (string, required)

### `connect_xero` (~36 tokens)

Get the Xero sign-in link

A link for the trade to open and sign in to Xero. Test mode: only a Xero Demo Company can be connected.

### `xero_status` (~20 tokens)

Check the Xero connection

Whether Xero is connected, and to which organisation.

### `push_bills_to_xero` (~137 tokens)

Put the month's bills into Xero as drafts

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.

Input parameters:

- `month` (string, required): YYYY-MM, for example 2026-11.
- `send` (boolean): true to really add the drafts. Default false (dry run).
- `suppliers` (array): Only these suppliers.

### `disconnect_xero` (~22 tokens)

Forget the Xero connection

Forget the Xero connection. Nothing in Xero is changed.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool#diagnostics

## Score history

- 2026-11-21: 61
- 2026-11-20: 60
- 2026-11-19: 60
- 2026-11-18: 60
- 2026-11-17: 59
- 2026-11-16: 59
- 2026-11-15: 58
- 2026-11-14: 58
- 2026-11-13: 57

## Common questions

### 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.

## Links

- Remote endpoint: https://supplier-invoice-tool.nerolabs.workers.dev/mcp
- Repository: https://github.com/Nero-Engine/supplier-invoice-tool-mcp
- Website: https://supplier-invoice-tool.nerolabs.workers.dev/docs
- Changelog RSS feed: https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool.xml
- Changelog JSON feed: https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool.json
- HTML version of this page: https://verifymcp.io/servers/nero-engine-supplier-invoice-tool/supplier-invoice-tool
