Holded (npm) MCP Server

holded-mcp npm v1.0.0

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

MCP server for the Holded ERP API - invoicing, CRM, projects, team, and accounting

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 136

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

  • attach_file_to_documentno sensitive capability
  • cancel_bookingno sensitive capability
  • create_accountno sensitive capability
  • create_bookingno sensitive capability
  • create_contactno sensitive capability
  • create_contact_groupno sensitive capability
  • create_daily_ledger_entryno sensitive capability
  • create_documentno sensitive capability
  • create_employeeno sensitive capability
  • create_employee_timeno sensitive capability
Show 126 more tools ↓
  • create_eventno sensitive capability
  • create_expenses_accountno sensitive capability
  • create_funnelno sensitive capability
  • create_leadno sensitive capability
  • create_lead_noteno sensitive capability
  • create_lead_taskno sensitive capability
  • create_numbering_seriesno sensitive capability
  • create_paymentno sensitive capability
  • create_productno sensitive capability
  • create_projectno sensitive capability
  • create_project_timeno sensitive capability
  • create_sales_channelno sensitive capability
  • create_serviceno sensitive capability
  • create_taskno sensitive capability
  • create_treasuryno sensitive capability
  • create_warehouseno sensitive capability
  • delete_contactno sensitive capability
  • delete_contact_groupno sensitive capability
  • delete_documentno sensitive capability
  • delete_employeeno sensitive capability
  • delete_eventno sensitive capability
  • delete_expenses_accountno sensitive capability
  • delete_funnelno sensitive capability
  • delete_leadno sensitive capability
  • delete_lead_taskno sensitive capability
  • delete_numbering_seriesno sensitive capability
  • delete_paymentno sensitive capability
  • delete_productno sensitive capability
  • delete_projectno sensitive capability
  • delete_project_timeno sensitive capability
  • delete_sales_channelno sensitive capability
  • delete_serviceno sensitive capability
  • delete_taskno sensitive capability
  • delete_time_trackingno sensitive capability
  • delete_warehouseno sensitive capability
  • employee_clock_inno sensitive capability
  • employee_clock_outno sensitive capability
  • employee_pauseno sensitive capability
  • employee_unpauseno sensitive capability
  • get_attachmentno sensitive capability
  • get_bookingno sensitive capability
  • get_booking_slotsno sensitive capability
  • get_contactno sensitive capability
  • get_contact_groupno sensitive capability
  • get_documentno sensitive capability
  • get_document_pdfno sensitive capability
  • get_employeeno sensitive capability
  • get_eventno sensitive capability
  • get_expenses_accountno sensitive capability
  • get_funnelno sensitive capability
  • get_leadno sensitive capability
  • get_paymentno sensitive capability
  • get_productno sensitive capability
  • get_product_imageno sensitive capability
  • get_product_secondary_imageno sensitive capability
  • get_projectno sensitive capability
  • get_project_summaryno sensitive capability
  • get_project_timeno sensitive capability
  • get_remittanceno sensitive capability
  • get_sales_channelno sensitive capability
  • get_serviceno sensitive capability
  • get_shipped_unitsno sensitive capability
  • get_taskno sensitive capability
  • get_taxesno sensitive capability
  • get_time_trackingno sensitive capability
  • get_treasuryno sensitive capability
  • get_warehouseno sensitive capability
  • list_accountsno sensitive capability
  • list_all_timesno sensitive capability
  • list_booking_locationsno sensitive capability
  • list_bookingsno sensitive capability
  • list_contact_attachmentsno sensitive capability
  • list_contact_groupsno sensitive capability
  • list_contactsno sensitive capability
  • list_daily_ledgerno sensitive capability
  • list_documentsno sensitive capability
  • list_employee_timesno sensitive capability
  • list_employeesno sensitive capability
  • list_eventsno sensitive capability
  • list_expenses_accountsno sensitive capability
  • list_funnelsno sensitive capability
  • list_leadsno sensitive capability
  • list_numbering_seriesno sensitive capability
  • list_payment_methodsno sensitive capability
  • list_paymentsno sensitive capability
  • list_product_imagesno sensitive capability
  • list_productsno sensitive capability
  • list_products_stockno sensitive capability
  • list_project_timesno sensitive capability
  • list_projectsno sensitive capability
  • list_remittancesno sensitive capability
  • list_sales_channelsno sensitive capability
  • list_servicesno sensitive capability
  • list_tasksno sensitive capability
  • list_time_trackingsno sensitive capability
  • list_treasuriesno sensitive capability
  • list_warehousesno sensitive capability
  • pay_documentno sensitive capability
  • send_documentno sensitive capability
  • ship_all_itemsno sensitive capability
  • ship_items_by_lineno sensitive capability
  • update_bookingno sensitive capability
  • update_contactno sensitive capability
  • update_contact_groupno sensitive capability
  • update_documentno sensitive capability
  • update_document_pipelineno sensitive capability
  • update_document_trackingno sensitive capability
  • update_employeeno sensitive capability
  • update_eventno sensitive capability
  • update_expenses_accountno sensitive capability
  • update_funnelno sensitive capability
  • update_leadno sensitive capability
  • update_lead_dateno sensitive capability
  • update_lead_noteno sensitive capability
  • update_lead_stageno sensitive capability
  • update_lead_taskno sensitive capability
  • update_numbering_seriesno sensitive capability
  • update_paymentno sensitive capability
  • update_productno sensitive capability
  • update_product_stockno sensitive capability
  • update_projectno sensitive capability
  • update_project_timeno sensitive capability
  • update_sales_channelno sensitive capability
  • update_serviceno sensitive capability
  • update_time_trackingno sensitive capability
  • update_warehouseno 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.0.0 latest A 98/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 · 98/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/holded-mcp/badge.svg)](https://mcptrustchecker.com/registry/holded-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/holded-mcp"><img src="https://mcptrustchecker.com/registry/holded-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/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 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