Home / MCP registry index / io.github.paulgosnell/accountsos-mcp

AccountsOS

io.github.paulgosnell/accountsos-mcp in the official MCP registry. Endpoint https://accounts-os.com/api/mcp/plugin. Source: github.com/thriveventurelabs/accountsos-mcp-server.

The registry describes it as: Query your live AccountsOS books: balances, transactions, VAT, deadlines, invoices.

We read its 82 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code

claude mcp add --transport http accountsos-mcp https://accounts-os.com/api/mcp/plugin

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "accountsos-mcp": {
      "url": "https://accounts-os.com/api/mcp/plugin"
    }
  }
}

VS Code

code --add-mcp '{"name":"accountsos-mcp","type":"http","url":"https://accounts-os.com/api/mcp/plugin"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

list_companies update_company link_company add_document get_transactions get_balance get_deadlines get_vat_summary search_documents read_wiki search_wiki read_company_wiki search_company_wiki get_tax_facts search_tax_facts list_categories get_dla_balance get_invoices get_contacts get_bills get_estimates get_profit_and_loss get_balance_sheet get_trial_balance get_tasks get_expense_claims get_bank_accounts get_journal_entries list_opportunities get_opportunity get_income_by_currency get_financial_snapshot get_integration_status get_gst_hst_return get_gifi_status get_vat_periods get_hmrc_vat_obligations get_hmrc_vat_liabilities get_hmrc_vat_payments check_vat_number get_incoming_messages get_gov_guidance get_aged_debtors get_aged_creditors get_goals list_employees get_payroll_summary get_projects get_project_pnl get_chart_of_accounts get_filed_accounts_history get_year_on_year get_budget_vs_actual get_fx_rates get_fixed_assets get_capital_allowance_hint get_reconciliation_status get_cash_flow_forecast get_dividends get_recurring_invoices and 22 more

Run this server? Show the check in your README

The badge reflects the latest weekly read:

Markdown

[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-paulgosnell-accountsos-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-paulgosnell-accountsos-mcp)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.