Xero Blade MCP Server
xero-blade-mcp
PyPI
v0.2.0
Published by an unidentified publisher — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.
Xero Accounting + Payroll AU MCP Server — token-efficient, security-first, Sidereal-native
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −2 | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 0
Tools 53
Each tool and what it can reach — statically extracted from the published source.
xero_verify_webhooknetwork egressxero_accountno sensitive capabilityxero_accountsno sensitive capabilityxero_aged_payablesno sensitive capabilityxero_aged_receivablesno sensitive capabilityxero_approve_timesheetno sensitive capabilityxero_archive_contactno sensitive capabilityxero_balance_sheetno sensitive capabilityxero_bank_transactionno sensitive capabilityxero_bank_transactionsno sensitive capability
Show 43 more tools ↓
xero_billno sensitive capabilityxero_billsno sensitive capabilityxero_branding_themesno sensitive capabilityxero_connectionsno sensitive capabilityxero_contactno sensitive capabilityxero_contactsno sensitive capabilityxero_create_bank_transactionno sensitive capabilityxero_create_billno sensitive capabilityxero_create_contactno sensitive capabilityxero_create_credit_noteno sensitive capabilityxero_create_invoiceno sensitive capabilityxero_create_paymentno sensitive capabilityxero_create_purchase_orderno sensitive capabilityxero_create_quoteno sensitive capabilityxero_create_timesheetno sensitive capabilityxero_credit_notesno sensitive capabilityxero_currenciesno sensitive capabilityxero_delete_paymentno sensitive capabilityxero_email_invoiceno sensitive capabilityxero_employeeno sensitive capabilityxero_employeesno sensitive capabilityxero_infono sensitive capabilityxero_invoiceno sensitive capabilityxero_invoicesno sensitive capabilityxero_manual_journalsno sensitive capabilityxero_organisationno sensitive capabilityxero_paymentno sensitive capabilityxero_paymentsno sensitive capabilityxero_payslipno sensitive capabilityxero_payslipsno sensitive capabilityxero_profit_lossno sensitive capabilityxero_purchase_ordersno sensitive capabilityxero_quotesno sensitive capabilityxero_tax_ratesno sensitive capabilityxero_timesheetno sensitive capabilityxero_timesheetsno sensitive capabilityxero_tracking_categoriesno sensitive capabilityxero_trial_balanceno sensitive capabilityxero_update_contactno sensitive capabilityxero_update_invoiceno sensitive capabilityxero_void_billno sensitive capabilityxero_void_credit_noteno sensitive capabilityxero_void_invoiceno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (53 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions 1
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.0 latest |
A 95/100 | 0 | 1.13.0 | 2026-08-25 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan xero-blade-mcp --online --registry pypiMore in Business & CRM
Free public tax reference data — GST/VAT, income, company and capital-gains tax rules for 50+ countries.
The approval gate for unattended UCP buying agents — a policy/approval MCP proxy in front of a merchant's UCP checkout endpoint.
Autotask PSA MCP server. Generic entity query/get/create/update across the full REST API plus convenience tools for tickets, companies, contacts, projects, tasks and time entries. AI-safe with readonly mode and destructive-action confirmation. stdio + opt
MCP server for B2C Commerce developer experience tools
Search, compare and contact real-world companies through a public MCP business directory.
Norwegian business register (Brønnøysundregistrene) as an MCP server — companies, roles, subunits and annual accounts, with the register's silent traps encoded as guards.