Home / MCP server directory / com.mobileaccounting/mcp

Mobile Accounting

com.mobileaccounting/mcp in the official MCP registry. Endpoint https://mcp.mobileaccounting.com/.

The registry describes it as: Your books in your AI assistant: draft expenses, bills, invoices, estimates; ask about P&L, tax.

We read its 52 tools on 2026-11-20. 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 about every two weeks.

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 mobileaccounting https://mcp.mobileaccounting.com/
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "mobileaccounting": {
      "url": "https://mcp.mobileaccounting.com/"
    }
  }
}
VS Code
code --add-mcp '{"name":"mobileaccounting","type":"http","url":"https://mcp.mobileaccounting.com/"}'

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.

Let Claude Code check servers as it adds them

With the free lazaretto-guard plugin installed, when Claude Code adds a server for you or writes one into an MCP config, the plugin reads the server's tools first and asks you if one of our rules matches. Install it, restart Claude Code, then ask it to run the command above.

Install lazaretto-guard
claude plugin marketplace add lazaretto-ai/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

find_contacts find_estimates get_installment_plan sales_tax_returns find_purchase_orders budget_vs_actual upcoming_installments log_time journal_entries profit_and_loss create_estimate tax_exemption_forms customer_statement general_ledger insights unbilled_time update_contact sales_tax_return_worksheet sales_tax_claims list_time balance_sheet create_invoice account_balances draft_budget cash_forecast month_end_checklist unpaid_bills draft_purchase_order get_on_order get_purchase_order sales_tax_report spending bill_time list_budgets check_tax_exemption exempt_sales tax_exemption_certificates sales_by_customer record_bill record_journal_entry budget_status list_books missing_receipts unpaid_invoices list_categories cash_flow record_expense get_document customer_portal get_card_fee_setting tax_set_aside find_documents

Tool changes

We compare every full read of this server with the one before. No change in what its tools say has been seen since we started keeping this record on 2026-10-30.

Fingerprint of its tools at our last full read (2026-11-20): c65d87e6d3abebd3. A client can hash the tools it is served the same way and compare; the full value and a hash per tool are in this page as JSON.

Rather than checking back: subscribe to this server's tool changes (a feed, no account and no address needed). Tool names and dates only, never what a tool says.

Run this server? Show the check in your README

The badge reflects the latest read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/com-mobileaccounting-mcp/badge.svg)](https://lazaretto.dev/mcp-registry/com-mobileaccounting-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. MCP tool poisoning, explained. What we found across the registry. Check another server.

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