Siigo (jdlar) MCP Server

@jdlar/siigo-mcp npm v4.0.0

Published by @jdlar — 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.

Model Context Protocol (MCP) server for Siigo Colombian accounting software API integration

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 71

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

  • siigo_create_webhooknetwork egress
  • siigo_delete_webhooknetwork egress
  • siigo_get_webhooksnetwork egress
  • siigo_update_webhooknetwork egress
  • siigo_annul_invoiceno sensitive capability
  • siigo_create_account_groupno sensitive capability
  • siigo_create_credit_noteno sensitive capability
  • siigo_create_customerno sensitive capability
  • siigo_create_invoiceno sensitive capability
  • siigo_create_invoice_batchno sensitive capability
Show 61 more tools ↓
  • siigo_create_journalno sensitive capability
  • siigo_create_payment_receiptno sensitive capability
  • siigo_create_productno sensitive capability
  • siigo_create_purchaseno sensitive capability
  • siigo_create_purchase_support_documentno sensitive capability
  • siigo_create_quotationno sensitive capability
  • siigo_create_voucherno sensitive capability
  • siigo_delete_invoiceno sensitive capability
  • siigo_delete_payment_receiptno sensitive capability
  • siigo_delete_productno sensitive capability
  • siigo_delete_purchaseno sensitive capability
  • siigo_delete_purchase_support_documentno sensitive capability
  • siigo_delete_quotationno sensitive capability
  • siigo_get_account_groupsno sensitive capability
  • siigo_get_accounts_payableno sensitive capability
  • siigo_get_cost_centersno sensitive capability
  • siigo_get_credit_noteno sensitive capability
  • siigo_get_credit_note_pdfno sensitive capability
  • siigo_get_credit_notesno sensitive capability
  • siigo_get_customerno sensitive capability
  • siigo_get_customersno sensitive capability
  • siigo_get_document_typesno sensitive capability
  • siigo_get_expensesno sensitive capability
  • siigo_get_fixed_assetsno sensitive capability
  • siigo_get_invoiceno sensitive capability
  • siigo_get_invoice_pdfno sensitive capability
  • siigo_get_invoice_stamp_errorsno sensitive capability
  • siigo_get_invoice_xmlno sensitive capability
  • siigo_get_invoicesno sensitive capability
  • siigo_get_journalno sensitive capability
  • siigo_get_journalsno sensitive capability
  • siigo_get_misc_incomeno sensitive capability
  • siigo_get_payment_receiptno sensitive capability
  • siigo_get_payment_receiptsno sensitive capability
  • siigo_get_payment_typesno sensitive capability
  • siigo_get_price_listsno sensitive capability
  • siigo_get_productno sensitive capability
  • siigo_get_productsno sensitive capability
  • siigo_get_purchaseno sensitive capability
  • siigo_get_purchase_support_documentno sensitive capability
  • siigo_get_purchasesno sensitive capability
  • siigo_get_quotationno sensitive capability
  • siigo_get_quotationsno sensitive capability
  • siigo_get_taxesno sensitive capability
  • siigo_get_trial_balanceno sensitive capability
  • siigo_get_trial_balance_by_thirdno sensitive capability
  • siigo_get_usersno sensitive capability
  • siigo_get_voucherno sensitive capability
  • siigo_get_vouchersno sensitive capability
  • siigo_get_warehousesno sensitive capability
  • siigo_search_customersno sensitive capability
  • siigo_search_productsno sensitive capability
  • siigo_send_invoice_emailno sensitive capability
  • siigo_update_account_groupno sensitive capability
  • siigo_update_customerno sensitive capability
  • siigo_update_invoiceno sensitive capability
  • siigo_update_payment_receiptno sensitive capability
  • siigo_update_productno sensitive capability
  • siigo_update_purchaseno sensitive capability
  • siigo_update_purchase_support_documentno sensitive capability
  • siigo_update_quotationno sensitive capability

What this scan could not see

Versions 2

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
v4.0.0 latest A 96/100 0 1.13.0 2026-09-08
v3.1.0 A 93/100 5 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/jdlar-siigo-mcp/badge.svg)](https://mcptrustchecker.com/registry/jdlar-siigo-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/jdlar-siigo-mcp"><img src="https://mcptrustchecker.com/registry/jdlar-siigo-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/jdlar-siigo-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 @jdlar/siigo-mcp --online

Use the free API → How scoring works

Other implementations of Siigo 1

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

More in Finance & Commerce