Holded (energio) MCP Server

@energio/holded-mcp npm v1.5.1

Published by @energio — 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 Holded — invoicing, accounting, CRM, projects, and team

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 63

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

  • holded_accounting_create_entryno sensitive capability
  • holded_accounting_list_account_balancesno sensitive capability
  • holded_accounting_list_daily_ledgerno sensitive capability
  • holded_crm_create_lead_noteno sensitive capability
  • holded_crm_create_lead_taskno sensitive capability
  • holded_crm_delete_lead_taskno sensitive capability
  • holded_crm_get_available_slotsno sensitive capability
  • holded_crm_list_booking_locationsno sensitive capability
  • holded_crm_update_lead_datesno sensitive capability
  • holded_crm_update_lead_noteno sensitive capability
Show 53 more tools ↓
  • holded_crm_update_lead_stageno sensitive capability
  • holded_crm_update_lead_taskno sensitive capability
  • holded_invoicing_attach_document_fileno sensitive capability
  • holded_invoicing_create_documentno sensitive capability
  • holded_invoicing_create_numbering_serieno sensitive capability
  • holded_invoicing_create_paymentno sensitive capability
  • holded_invoicing_create_treasuryno sensitive capability
  • holded_invoicing_delete_documentno sensitive capability
  • holded_invoicing_delete_numbering_serieno sensitive capability
  • holded_invoicing_get_contact_attachmentno sensitive capability
  • holded_invoicing_get_documentno sensitive capability
  • holded_invoicing_get_document_pdfno sensitive capability
  • holded_invoicing_get_numbering_seriesno sensitive capability
  • holded_invoicing_get_product_imageno sensitive capability
  • holded_invoicing_get_product_secondary_imageno sensitive capability
  • holded_invoicing_get_shipped_itemsno sensitive capability
  • holded_invoicing_get_taxesno sensitive capability
  • holded_invoicing_get_treasuryno sensitive capability
  • holded_invoicing_list_contact_attachmentsno sensitive capability
  • holded_invoicing_list_documentsno sensitive capability
  • holded_invoicing_list_payment_methodsno sensitive capability
  • holded_invoicing_list_product_imagesno sensitive capability
  • holded_invoicing_list_products_stockno sensitive capability
  • holded_invoicing_list_treasuriesno sensitive capability
  • holded_invoicing_pay_documentno sensitive capability
  • holded_invoicing_send_documentno sensitive capability
  • holded_invoicing_ship_all_itemsno sensitive capability
  • holded_invoicing_ship_items_by_lineno sensitive capability
  • holded_invoicing_update_documentno sensitive capability
  • holded_invoicing_update_document_pipelineno sensitive capability
  • holded_invoicing_update_document_trackingno sensitive capability
  • holded_invoicing_update_numbering_serieno sensitive capability
  • holded_invoicing_update_paymentno sensitive capability
  • holded_invoicing_update_product_stockno sensitive capability
  • holded_invoicing_upload_product_imageno sensitive capability
  • holded_projects_create_project_time_trackingno sensitive capability
  • holded_projects_create_taskno sensitive capability
  • holded_projects_delete_project_time_trackingno sensitive capability
  • holded_projects_get_project_summaryno sensitive capability
  • holded_projects_get_project_time_trackingno sensitive capability
  • holded_projects_list_all_timesno sensitive capability
  • holded_projects_list_project_time_trackingsno sensitive capability
  • holded_projects_update_project_time_trackingno sensitive capability
  • holded_team_create_employee_time_trackingno sensitive capability
  • holded_team_delete_time_trackingno sensitive capability
  • holded_team_employee_clock_inno sensitive capability
  • holded_team_employee_clock_outno sensitive capability
  • holded_team_employee_pauseno sensitive capability
  • holded_team_employee_unpauseno sensitive capability
  • holded_team_get_time_trackingno sensitive capability
  • holded_team_list_all_time_trackingsno sensitive capability
  • holded_team_list_employee_time_trackingsno sensitive capability
  • holded_team_update_time_trackingno 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
v1.5.1 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/energio-holded-mcp/badge.svg)](https://mcptrustchecker.com/registry/energio-holded-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/energio-holded-mcp"><img src="https://mcptrustchecker.com/registry/energio-holded-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/energio-holded-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 @energio/holded-mcp --online

Use the free API → How scoring works

Other implementations of Holded 4

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

More in Business & CRM