Karbon MCP Server

karbon-mcp-server npm v0.2.4 Source verified

Published by mad-man-dan — publish provenance cryptographically ties this package to that repository. That is proof of origin, not an official vendor package.

Unofficial MCP server for Karbon practice management — connect Claude Code, Claude Desktop, Copilot, or any MCP client to your Karbon instance.

Trust grade
A
97/100
Last scanned get badge →
Trust
A · 97/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 = 97/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 − 3 = 97. 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

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 2

medium Untrusted input can drive an external actionMTC-FLOW-005

Untrusted-input tools ([update_business_card, list_entity_files, download_file]) co-exist with external-action tools ([upload_file]). A prompt injection could cause unwanted external actions, though no direct sensitive-data leak path was found.

Evidence: untrusted [update_business_card, list_entity_files, download_file] → sinks [upload_file]

Fix: Require confirmation for state-changing/egress actions triggered after processing untrusted content.

Location: flow update_business_card → upload_file

low Shell/command execution in packaging/dev tooling (dist/setup.js)MTC-SRC-002

In a packaging/dev/install script (shipped, but not the server runtime) (`dist/setup.js:14`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.

Evidence: spawnSync } from "node:child_process"; import * as fs from "node:fs"; import * as os from "node:os"; import * as path f

Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.

Location: server dist/setup.js

Tools 53

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

  • download_fileingests untrusted input
  • list_entity_filesingests untrusted input
  • update_business_cardingests untrusted input
  • upload_filenetwork egress
  • add_team_membersno sensitive capability
  • create_client_groupno sensitive capability
  • create_contactno sensitive capability
  • create_custom_fieldno sensitive capability
  • create_manual_paymentno sensitive capability
  • create_noteno sensitive capability
Show 43 more tools ↓
  • create_organizationno sensitive capability
  • create_work_itemno sensitive capability
  • create_work_scheduleno sensitive capability
  • delete_custom_fieldno sensitive capability
  • delete_manual_paymentno sensitive capability
  • get_business_cardno sensitive capability
  • get_client_groupno sensitive capability
  • get_commentno sensitive capability
  • get_contactno sensitive capability
  • get_custom_field_valuesno sensitive capability
  • get_estimate_summaryno sensitive capability
  • get_invoiceno sensitive capability
  • get_noteno sensitive capability
  • get_organizationno sensitive capability
  • get_paymentno sensitive capability
  • get_teamno sensitive capability
  • get_tenant_settingsno sensitive capability
  • get_time_entryno sensitive capability
  • get_timesheetno sensitive capability
  • get_userno sensitive capability
  • get_work_itemno sensitive capability
  • get_work_scheduleno sensitive capability
  • get_work_templateno sensitive capability
  • list_client_groupsno sensitive capability
  • list_contactsno sensitive capability
  • list_custom_fieldsno sensitive capability
  • list_invoicesno sensitive capability
  • list_organizationsno sensitive capability
  • list_paymentsno sensitive capability
  • list_teamsno sensitive capability
  • list_time_entriesno sensitive capability
  • list_timesheetsno sensitive capability
  • list_usersno sensitive capability
  • list_work_itemsno sensitive capability
  • list_work_templatesno sensitive capability
  • remove_team_memberno sensitive capability
  • reverse_manual_paymentno sensitive capability
  • set_custom_field_valuesno sensitive capability
  • update_client_groupno sensitive capability
  • update_contactno sensitive capability
  • update_organizationno sensitive capability
  • update_work_itemno sensitive capability
  • update_work_scheduleno sensitive capability

Toxic flows 1

Cross-tool combinations that form a data-exfiltration primitive (untrusted input → sensitive source → external sink).

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

Use the free API → How scoring works

More in Business & CRM