Siigo (dsfaccini) MCP Server

siigo-mcp PyPI v0.1.2

Published by dsfaccini — 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 Siigo invoicing software

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 36

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

  • get_credit_note_pdfingests untrusted input
  • get_invoice_pdfingests untrusted input
  • annul_invoiceno sensitive capability
  • call_siigo_toolno sensitive capability
  • create_credit_noteno sensitive capability
  • create_customerno sensitive capability
  • create_invoiceno sensitive capability
  • create_journalno sensitive capability
  • create_productno sensitive capability
  • delete_customerno sensitive capability
Show 26 more tools ↓
  • delete_invoiceno sensitive capability
  • delete_productno sensitive capability
  • get_account_groupsno sensitive capability
  • get_credit_noteno sensitive capability
  • get_customerno sensitive capability
  • get_document_typesno sensitive capability
  • get_invoiceno sensitive capability
  • get_journalno sensitive capability
  • get_payment_typesno sensitive capability
  • get_productno sensitive capability
  • get_stamp_errorsno sensitive capability
  • get_taxesno sensitive capability
  • get_tool_schemano sensitive capability
  • get_usersno sensitive capability
  • get_warehousesno sensitive capability
  • list_credit_notesno sensitive capability
  • list_customersno sensitive capability
  • list_invoicesno sensitive capability
  • list_journalsno sensitive capability
  • list_productsno sensitive capability
  • list_siigo_toolsno sensitive capability
  • send_invoice_emailno sensitive capability
  • stamp_invoiceno sensitive capability
  • update_customerno sensitive capability
  • update_invoiceno sensitive capability
  • update_productno 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.2 latest 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/siigo-mcp/badge.svg)](https://mcptrustchecker.com/registry/siigo-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/siigo-mcp"><img src="https://mcptrustchecker.com/registry/siigo-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/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 siigo-mcp --online --registry pypi

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