Home / MCP registry index / io.usefulapi/kashflow

KashFlow MCP by usefulapi

io.usefulapi/kashflow in the official MCP registry. Endpoint https://kashflow.usefulapi.io/mcp. Source: github.com/m190/usefulapi-mcp.

The registry describes it as: Read KashFlow invoices, customers, suppliers, banking and reports; add customers, notes.

We read its 38 tools on 2026-10-31. 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 kashflow https://kashflow.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

{
  "mcpServers": {
    "kashflow": {
      "url": "https://kashflow.usefulapi.io/mcp"
    }
  }
}

VS Code

code --add-mcp '{"name":"kashflow","type":"http","url":"https://kashflow.usefulapi.io/mcp"}'

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 jamesdfinance-dev/lazaretto-plugins
claude plugin install lazaretto-guard@lazaretto-plugins

Tools it advertises

kashflow_get_company_details kashflow_list_customers kashflow_get_customer kashflow_get_customer_by_id kashflow_find_customer_by_email kashflow_get_customer_balance kashflow_create_customer kashflow_list_suppliers kashflow_get_supplier kashflow_create_supplier kashflow_get_invoice kashflow_list_invoices kashflow_list_customer_invoices kashflow_list_unpaid_invoices kashflow_list_overdue_invoices kashflow_list_recent_invoices kashflow_list_invoice_payments kashflow_list_payments_by_date kashflow_get_invoice_notes kashflow_add_invoice_note kashflow_list_quotes kashflow_get_receipt kashflow_list_recent_receipts kashflow_list_supplier_receipts kashflow_list_products kashflow_list_bank_accounts kashflow_list_bank_transactions kashflow_get_bank_balance kashflow_list_nominal_codes kashflow_list_vat_rates kashflow_list_projects kashflow_get_profit_and_loss kashflow_get_balance_sheet kashflow_get_trial_balance kashflow_get_aged_debtors kashflow_get_aged_creditors kashflow_get_vat_report kashflow_get_kpis

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-10-31): e6151759432a33f9. 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.

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-usefulapi-kashflow/badge.svg)](https://lazaretto.dev/mcp-registry/io-usefulapi-kashflow)

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.