Firefly Iii (xerrion) MCP Server

@xerrion/firefly-iii-mcp npm v0.1.1 Source verified

Published by xerrion — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

MCP server exposing 41 task-shaped Firefly III tools for personal accounting

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 97/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 3 = 97. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 41

Each tool and what it can reach — statically extracted from the published source.

  • get_accountingests untrusted input
  • get_ruleingests untrusted input
  • get_rule_groupingests untrusted input
  • get_transactioningests untrusted input
  • list_transactionsingests untrusted input
  • contribute_piggy_bankno sensitive capability
  • create_accountno sensitive capability
  • create_piggy_bankno sensitive capability
  • create_ruleno sensitive capability
  • create_rule_groupno sensitive capability
Show 31 more tools ↓
  • create_transactionno sensitive capability
  • delete_accountno sensitive capability
  • delete_billno sensitive capability
  • delete_budgetno sensitive capability
  • delete_categoryno sensitive capability
  • delete_piggy_bankno sensitive capability
  • delete_ruleno sensitive capability
  • delete_rule_groupno sensitive capability
  • delete_tagno sensitive capability
  • delete_transactionno sensitive capability
  • get_financial_summaryno sensitive capability
  • get_spending_insightsno sensitive capability
  • get_system_infono sensitive capability
  • list_accountsno sensitive capability
  • list_billsno sensitive capability
  • list_budgetsno sensitive capability
  • list_categoriesno sensitive capability
  • list_piggy_banksno sensitive capability
  • list_rule_groupsno sensitive capability
  • list_rulesno sensitive capability
  • list_tagsno sensitive capability
  • search_transactionsno sensitive capability
  • update_accountno sensitive capability
  • update_piggy_bankno sensitive capability
  • update_ruleno sensitive capability
  • update_rule_groupno sensitive capability
  • update_transactionno sensitive capability
  • upsert_billno sensitive capability
  • upsert_budgetno sensitive capability
  • upsert_categoryno sensitive capability
  • upsert_tagno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.1 latest A 97/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 97/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/xerrion-firefly-iii-mcp/badge.svg)](https://mcptrustchecker.com/registry/xerrion-firefly-iii-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/xerrion-firefly-iii-mcp"><img src="https://mcptrustchecker.com/registry/xerrion-firefly-iii-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/xerrion-firefly-iii-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @xerrion/firefly-iii-mcp --online

Use the free API → How scoring works

Other implementations of Firefly Iii 4

Independent packages implementing the same tool, scanned with the same engine. Compare all 5 side by side →

More in Finance & Commerce