Milkee MCP Server

milkee-mcp npm v1.2.14

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.

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.
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 73

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

  • milkee_bulk_archive_projectsno sensitive capability
  • milkee_bulk_delete_entriesno sensitive capability
  • milkee_convert_proposal_to_invoiceno sensitive capability
  • milkee_create_accountno sensitive capability
  • milkee_create_contactno sensitive capability
  • milkee_create_customerno sensitive capability
  • milkee_create_entryno sensitive capability
  • milkee_create_entry_with_fileno sensitive capability
  • milkee_create_invoiceno sensitive capability
  • milkee_create_productno sensitive capability
Show 63 more tools ↓
  • milkee_create_projectno sensitive capability
  • milkee_create_proposalno sensitive capability
  • milkee_create_tagno sensitive capability
  • milkee_create_taskno sensitive capability
  • milkee_create_timeno sensitive capability
  • milkee_delete_accountno sensitive capability
  • milkee_delete_contactno sensitive capability
  • milkee_delete_customerno sensitive capability
  • milkee_delete_entryno sensitive capability
  • milkee_delete_invoiceno sensitive capability
  • milkee_delete_productno sensitive capability
  • milkee_delete_projectno sensitive capability
  • milkee_delete_proposalno sensitive capability
  • milkee_delete_tagno sensitive capability
  • milkee_delete_taskno sensitive capability
  • milkee_delete_timeno sensitive capability
  • milkee_discard_timerno sensitive capability
  • milkee_get_accountno sensitive capability
  • milkee_get_company_summaryno sensitive capability
  • milkee_get_customerno sensitive capability
  • milkee_get_customer_statisticsno sensitive capability
  • milkee_get_entryno sensitive capability
  • milkee_get_invoiceno sensitive capability
  • milkee_get_next_entry_numberno sensitive capability
  • milkee_get_productno sensitive capability
  • milkee_get_projectno sensitive capability
  • milkee_get_proposalno sensitive capability
  • milkee_get_tagno sensitive capability
  • milkee_get_tag_colorsno sensitive capability
  • milkee_get_taskno sensitive capability
  • milkee_get_tax_rateno sensitive capability
  • milkee_get_timeno sensitive capability
  • milkee_get_timerno sensitive capability
  • milkee_list_accountsno sensitive capability
  • milkee_list_contactsno sensitive capability
  • milkee_list_customersno sensitive capability
  • milkee_list_entriesno sensitive capability
  • milkee_list_invoicesno sensitive capability
  • milkee_list_productsno sensitive capability
  • milkee_list_projectsno sensitive capability
  • milkee_list_proposalsno sensitive capability
  • milkee_list_tagsno sensitive capability
  • milkee_list_tasksno sensitive capability
  • milkee_list_tax_ratesno sensitive capability
  • milkee_list_timesno sensitive capability
  • milkee_mark_invoice_paidno sensitive capability
  • milkee_send_invoiceno sensitive capability
  • milkee_send_proposalno sensitive capability
  • milkee_start_timerno sensitive capability
  • milkee_stop_timerno sensitive capability
  • milkee_update_accountno sensitive capability
  • milkee_update_contactno sensitive capability
  • milkee_update_customerno sensitive capability
  • milkee_update_entryno sensitive capability
  • milkee_update_invoiceno sensitive capability
  • milkee_update_productno sensitive capability
  • milkee_update_projectno sensitive capability
  • milkee_update_proposalno sensitive capability
  • milkee_update_tagno sensitive capability
  • milkee_update_taskno sensitive capability
  • milkee_update_timeno sensitive capability
  • milkee_update_timer_descriptionno sensitive capability
  • milkee_upload_entry_fileno 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.2.14 latest A 98/100 0 1.8.0 2026-07-23

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/milkee-mcp/badge.svg)](https://mcptrustchecker.com/registry/milkee-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/milkee-mcp"><img src="https://mcptrustchecker.com/registry/milkee-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/milkee-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 milkee-mcp --online

Use the free API → How scoring works

More in Business & CRM