Xero
NPM · @PIPEWORX/MCP-XERO · 2 COMPONENTS
Xero (Accounting) MCP Pack
Available components
Last scanned (57 minutes ago)
Scores higher than 81% of npm servers
Category Finance and Payments
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-xero). View diagnostics → Pass
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 7 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability75
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 675 tokens (~135/item across 5 items; 5 tools + 0 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 Management23
- Stability observed for 7 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 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
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 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 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 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.
- 31 Oct 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.
- 29 Oct 26 81
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 · Analysed npm/@pipeworx/mcp-xero@0.2.0
Provenance Verified
A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.
| Result | Verified |
|---|---|
| Ecosystem | npm |
| Reason | Verified |
| Discovered via | Registry attestation endpoint |
| Source repo | pipeworx-io/mcp-xero |
| Certificate issuer | https://token.actions.githubusercontent.com |
| Certificate SAN | https://github.com/pipeworx-io/mcp-xero/.github/workflows/publish.yml@refs/heads/main |
| Rekor log index | 3561204451 |
| Predicate type | SLSA build provenance https://slsa.dev/provenance/v1 |
| Subject digest | sha512:89ddc94f469c69e4b15ee9ae92203a4da2088295f37826a9ca9497d49e7b6f9b251d9413368d983df48aece6462b840e4e9ca3872f1da03cdb6a030a6 |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
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 →
get_profit_and_loss ~141
Get the Profit and Loss (income statement) financial report from a Xero accounting organisation for an optional date range. Returns the structured Xero report (report name, date, and row sections covering revenue, expenses, and net profit). Use for financial reporting and bookkeeping analysis.
| Name | Type | Req | Description |
|---|---|---|---|
| from_date | string | – | Optional start date of the reporting period in YYYY-MM-DD format. |
| tenant_id | string | – | Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations. |
| to_date | string | – | Optional end date of the reporting period in YYYY-MM-DD format. |
No output schema declared.
No examples provided.
list_accounts ~86
List the chart of accounts from a Xero accounting organisation. Returns each account's code, name, type, class, and status. Use to understand an organisation's general ledger structure for bookkeeping and financial reporting.
| Name | Type | Req | Description |
|---|---|---|---|
| tenant_id | string | – | Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations. |
No output schema declared.
No examples provided.
list_contacts ~160
List contacts (customers and suppliers) from a Xero accounting organisation. Returns name, email, status, and customer/supplier flags. Use for accounting, bookkeeping, and accounts-receivable/payable workflows. Supports Xero filter expressions and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination (default 1). Xero returns up to 100 contacts per page. |
| tenant_id | string | – | Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations. |
| where | string | – | Optional Xero filter expression (e.g. 'IsCustomer==true' or 'ContactStatus=="ACTIVE"'). Applied as the Xero `where` query parameter. |
No output schema declared.
No examples provided.
list_invoices ~168
List invoices and bills from a Xero accounting organisation. Returns compact invoice summaries (number, type, status, contact, dates, total, amount due, currency) for bookkeeping, accounts-receivable, and accounts-payable review. Supports Xero filter expressions and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| page | number | – | Page number for pagination (default 1). Xero returns up to 100 invoices per page. |
| tenant_id | string | – | Optional Xero tenant (organisation) id to target. If omitted, the first connected organisation is used. Get ids from list_organisations. |
| where | string | – | Optional Xero filter expression (e.g. 'Status=="AUTHORISED"' or 'Type=="ACCREC"'). Applied as the Xero `where` query parameter. |
No output schema declared.
No examples provided.
list_organisations ~68
List the Xero organisations (tenants) the connected account can access, with tenant id, name, and type. Xero accounting is multi-tenant — use this first to discover the tenant_id for a specific organisation, then pass it to the other accounting tools to target that org.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the Xero MCP server?
Xero runs locally as an npm package, launched with npx -y @pipeworx/mcp-xero. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @pipeworx/mcp-xero
claude mcp add pipeworx-io-xero -- npx -y @pipeworx/mcp-xero
What is the Xero MCP server?
Xero is an MCP server listed in the public MCP registry as io.github.pipeworx-io/xero. Xero (Accounting) MCP Pack. This page covers its npm package (@pipeworx/mcp-xero).
Is the Xero MCP server safe to use?
Xero scores 84 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Xero MCP server expose?
Xero exposes 5 tools: list_organisations, list_invoices, list_contacts, get_profit_and_loss, list_accounts. Their descriptions and schemas cost roughly 623 tokens of context every time the server is loaded.
Is the Xero MCP server still maintained?
Xero 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.
What licence is the Xero MCP server under?
Xero declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.