Home / MCP registry index / io.usefulapi/daftra

Daftra MCP by usefulapi

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

The registry describes it as: Read clients, invoices, expenses and suppliers; create clients, invoices and expenses in Daftra.

We read its 30 tools on 2026-11-05. 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 daftra https://daftra.usefulapi.io/mcp

Cursor: ~/.cursor/mcp.json

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

VS Code

code --add-mcp '{"name":"daftra","type":"http","url":"https://daftra.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

daftra_get_site_info daftra_list_clients daftra_get_client daftra_list_invoices daftra_get_invoice daftra_list_estimates daftra_get_estimate daftra_list_invoice_payments daftra_list_client_payments daftra_list_products daftra_get_product daftra_list_product_categories daftra_list_stores daftra_list_stock_transactions daftra_list_treasuries daftra_list_expenses daftra_get_expense daftra_list_incomes daftra_list_taxes daftra_list_purchase_invoices daftra_get_purchase_invoice daftra_list_suppliers daftra_get_supplier daftra_list_notes daftra_create_client daftra_update_client daftra_create_supplier daftra_create_expense daftra_create_invoice daftra_add_note

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-05): 593be6774894825b. 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:

Markdown

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

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. How tool poisoning works. 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 every server in the index.