@crowdform/freeagent-mcp
npm
v0.1.0
Published by @crowdform — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Unofficial MCP server for the FreeAgent accounting API — accounts, invoices, bills and bank reconciliation
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 − 7 = 93. 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 |
|---|---|
| −6 | capability blast radius (high) — client exposure if the model is manipulated |
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
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.
In the server's implementation (`dist/auth-cli.js:18`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { loadConfig } from "./config.js"; import { writeTokens } from "./token-s
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/auth-cli.js
In the server's implementation (`dist/tools/auth.js:3`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: rt { spawn } from "node:child_process"; import { z } from "zod"; import { jsonResult, safe } from "../helpers.js"; impor
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server dist/tools/auth.js
Each tool and what it can reach — statically extracted from the published source.
check_auth_statusno sensitive capabilityconnect_freeagentno sensitive capabilitycreate_billno sensitive capabilitycreate_contactno sensitive capabilitycreate_invoiceno sensitive capabilitycreate_journal_setno sensitive capabilitydelete_bank_transaction_explanationno sensitive capabilityexplain_bank_transactionno sensitive capabilityget_balance_sheetno sensitive capabilityget_bank_transactionno sensitive capabilityget_billno sensitive capabilityget_cashflowno sensitive capabilityget_companyno sensitive capabilityget_contactno sensitive capabilityget_invoiceno sensitive capabilityget_profit_and_lossno sensitive capabilityget_trial_balanceno sensitive capabilityget_vat_returnno sensitive capabilitylist_bank_accountsno sensitive capabilitylist_bank_transaction_explanationsno sensitive capabilitylist_bank_transactionsno sensitive capabilitylist_billsno sensitive capabilitylist_categoriesno sensitive capabilitylist_contactsno sensitive capabilitylist_credit_notesno sensitive capabilitylist_estimatesno sensitive capabilitylist_expensesno sensitive capabilitylist_invoicesno sensitive capabilitylist_journal_setsno sensitive capabilitylist_ledger_transactionsno sensitive capabilitylist_projectsno sensitive capabilitylist_usersno sensitive capabilitylist_vat_returnsno sensitive capabilitysuggest_reconciliation_matchesno sensitive capabilityupdate_bank_transaction_explanationno sensitive capabilityupdate_invoice_statusno sensitive capabilityupload_bank_statementno sensitive capabilityScan 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.1.0 latest |
A 93/100 | 2 | 1.13.0 | 2026-09-07 |
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.
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 @crowdform/freeagent-mcp --online
Independent packages implementing the same tool, scanned with the same engine. Compare all 4 side by side →
MCP Server for FreeAgent accounting API integration
MCP server for the FreeAgent API
MCP server for FreeAgent accounting — bank reconciliation, expenses, mileage claims and receipt management
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.