Accountsos MCP Server

@thriveventurelabs/accountsos-mcp npm v0.2.3

Published by @thriveventurelabs — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

MCP server for AccountsOS - Chat with your books from Claude Desktop

Trust grade
A
99/100
Last scanned get badge →
Trust
A · 99/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
Minimal
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 = 99/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 − 1 = 99. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 43

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

  • add_opportunity_noteno sensitive capability
  • categorize_transactionno sensitive capability
  • Companyno sensitive capability
  • create_billno sensitive capability
  • create_contactno sensitive capability
  • create_deadlineno sensitive capability
  • create_estimateno sensitive capability
  • create_opportunityno sensitive capability
  • create_taskno sensitive capability
  • create_transactionno sensitive capability
Show 33 more tools ↓
  • Deadlinesno sensitive capability
  • Documentsno sensitive capability
  • get_balanceno sensitive capability
  • get_balance_sheetno sensitive capability
  • get_bank_accountsno sensitive capability
  • get_billsno sensitive capability
  • get_contactsno sensitive capability
  • get_deadlinesno sensitive capability
  • get_dla_balanceno sensitive capability
  • get_estimatesno sensitive capability
  • get_expense_claimsno sensitive capability
  • get_invoicesno sensitive capability
  • get_journal_entriesno sensitive capability
  • get_opportunityno sensitive capability
  • get_profit_and_lossno sensitive capability
  • get_tasksno sensitive capability
  • get_tax_factsno sensitive capability
  • get_transactionsno sensitive capability
  • get_trial_balanceno sensitive capability
  • get_vat_summaryno sensitive capability
  • list_categoriesno sensitive capability
  • list_opportunitiesno sensitive capability
  • pay_billno sensitive capability
  • read_company_wikino sensitive capability
  • read_wikino sensitive capability
  • Recent Transactionsno sensitive capability
  • search_company_wikino sensitive capability
  • search_documentsno sensitive capability
  • search_tax_factsno sensitive capability
  • search_wikino sensitive capability
  • update_opportunity_stageno sensitive capability
  • update_transactionno sensitive capability
  • upload_documentno 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.2.3 latest A 99/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 · 99/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/thriveventurelabs-accountsos-mcp/badge.svg)](https://mcptrustchecker.com/registry/thriveventurelabs-accountsos-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/thriveventurelabs-accountsos-mcp"><img src="https://mcptrustchecker.com/registry/thriveventurelabs-accountsos-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/thriveventurelabs-accountsos-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 @thriveventurelabs/accountsos-mcp --online

Use the free API → How scoring works

More in Business & CRM