Home / MCP registry index / com.getsavitools/savi-tools
com.getsavitools/savi-tools
com.getsavitools/savi-tools in the official MCP registry.
Endpoint https://getsavitools.com/api/mcp.
The registry describes it as: Ask your AI assistant about your Savi Tools business: invoices, expenses, mileage, and more.
We read its 25 tools on 2026-10-22. 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.
Tools it advertises
list_outstanding_invoices get_mileage_summary get_contact_history get_contact_summary get_business_snapshot get_tax_setaside get_revenue_summary get_invoice_details list_recent_invoices get_expense_summary list_recent_expenses get_cost_summary list_bills_owed get_profitability get_tax_deductions get_1099_summary list_clients get_client_summary list_projects get_project_summary get_time_summary get_cash_summary list_uncategorized_transactions get_goals_progress get_business_profile
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-getsavitools-savi-tools)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.