Yuki MCP Server

@codemill-solutions/yuki-mcp npm v1.7.0

Published by @codemill-solutions — 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 the Yuki accounting SOAP API

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−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 31

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

  • download_documentingests untrusted input
  • get_transaction_documentingests untrusted input
  • get_administration_idno sensitive capability
  • get_administrationsno sensitive capability
  • get_cost_categoriesno sensitive capability
  • get_documentno sensitive capability
  • get_document_foldersno sensitive capability
  • get_gl_account_schemeno sensitive capability
  • get_gl_accountsno sensitive capability
  • get_gl_accounts_fiscalno sensitive capability
Show 21 more tools ↓
  • get_gl_transactions_detailedno sensitive capability
  • get_missing_invoicesno sensitive capability
  • get_net_revenueno sensitive capability
  • get_outstanding_questionsno sensitive capability
  • get_period_tableno sensitive capability
  • get_purchase_invoicesno sensitive capability
  • get_sales_invoicesno sensitive capability
  • get_start_balancesno sensitive capability
  • get_transaction_detailsno sensitive capability
  • get_transactionsno sensitive capability
  • get_workflowno sensitive capability
  • list_documentsno sensitive capability
  • process_journalno sensitive capability
  • process_purchase_invoiceno sensitive capability
  • process_sales_invoiceno sensitive capability
  • reload_keysno sensitive capability
  • search_documentsno sensitive capability
  • search_relationsno sensitive capability
  • upload_documentno sensitive capability
  • upload_document_from_pathno sensitive capability
  • upsert_contactno sensitive capability

What this scan could not see

Versions 3

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
v1.7.0 latest A 96/100 0 1.13.0 2026-09-08
v1.6.0 A 96/100 0 1.13.0 2026-09-01
v1.5.1 A 96/100 0 1.13.0 2026-08-25

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/codemill-solutions-yuki-mcp/badge.svg)](https://mcptrustchecker.com/registry/codemill-solutions-yuki-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/codemill-solutions-yuki-mcp"><img src="https://mcptrustchecker.com/registry/codemill-solutions-yuki-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/codemill-solutions-yuki-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 @codemill-solutions/yuki-mcp --online

Use the free API → How scoring works

More in Finance & Commerce