Cynco MCP Server

@cynco/mcp npm v2.0.0

Published by @cynco — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Cynco Accounting MCP Server — AI-native accounting tools via Model Context Protocol

Trust grade
A
98/100
Last scanned get badge →
Trust
A · 98/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 = 98/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 − 2 = 98. 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
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

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 52

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

  • apply_journal_entry_templateno sensitive capability
  • close_periodno sensitive capability
  • create_bank_transactionsno sensitive capability
  • create_categorization_ruleno sensitive capability
  • create_invoiceno sensitive capability
  • create_journal_entriesno sensitive capability
  • create_journal_entry_templateno sensitive capability
  • execute_queryno sensitive capability
  • get_account_activityno sensitive capability
  • get_account_balancesno sensitive capability
Show 42 more tools ↓
  • get_balance_sheetno sensitive capability
  • get_bank_transactionsno sensitive capability
  • get_billsno sensitive capability
  • get_cash_flow_summaryno sensitive capability
  • get_categorization_rulesno sensitive capability
  • get_chart_of_accountsno sensitive capability
  • get_company_profileno sensitive capability
  • get_credit_debit_notesno sensitive capability
  • get_customer_agingno sensitive capability
  • get_customer_statementno sensitive capability
  • get_customersno sensitive capability
  • get_financial_accountsno sensitive capability
  • get_financial_summaryno sensitive capability
  • get_general_ledgerno sensitive capability
  • get_income_statementno sensitive capability
  • get_invoice_aging_detailno sensitive capability
  • get_invoicesno sensitive capability
  • get_journal_entriesno sensitive capability
  • get_journal_entry_templatesno sensitive capability
  • get_paymentsno sensitive capability
  • get_period_statusno sensitive capability
  • get_purchase_ordersno sensitive capability
  • get_quotationsno sensitive capability
  • get_reconciliation_statusno sensitive capability
  • get_recurring_invoicesno sensitive capability
  • get_tagsno sensitive capability
  • get_trial_balanceno sensitive capability
  • get_vendor_agingno sensitive capability
  • get_vendor_statementno sensitive capability
  • get_vendorsno sensitive capability
  • post_bank_transactionsno sensitive capability
  • reconcile_accountsno sensitive capability
  • record_paymentno sensitive capability
  • reopen_periodno sensitive capability
  • search_accountsno sensitive capability
  • search_bank_transactionsno sensitive capability
  • search_journal_entriesno sensitive capability
  • search_schemano sensitive capability
  • update_bank_transaction_statusno sensitive capability
  • update_categorization_ruleno sensitive capability
  • update_invoice_statusno sensitive capability
  • update_journal_entry_statusno 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
v2.0.0 latest A 98/100 0 1.13.0 2026-09-08

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

Use the free API → How scoring works

More in Finance & Commerce