Carrot MCP Server

carrot-mcp PyPI v0.1.5

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.

Carrot MCP - A collection of MCP servers

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

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

  • get_outlineingests untrusted input
  • get_pagesingests untrusted input
  • activeno sensitive capability
  • backup_historyno sensitive capability
  • backup_restoreno sensitive capability
  • closeno sensitive capability
  • connectno sensitive capability
  • copy_rangeno sensitive capability
  • create_sheetno sensitive capability
  • delete_columnsno sensitive capability
Show 48 more tools ↓
  • delete_imageno sensitive capability
  • delete_parano sensitive capability
  • delete_rangeno sensitive capability
  • delete_rowsno sensitive capability
  • delete_sheetno sensitive capability
  • delete_tableno sensitive capability
  • disconnectno sensitive capability
  • field_offno sensitive capability
  • field_onno sensitive capability
  • format_parano sensitive capability
  • format_rangeno sensitive capability
  • format_tableno sensitive capability
  • get_contentno sensitive capability
  • get_tableno sensitive capability
  • get_tocno sensitive capability
  • grepno sensitive capability
  • haltno sensitive capability
  • historyno sensitive capability
  • insert_columnsno sensitive capability
  • insert_imageno sensitive capability
  • insert_parano sensitive capability
  • insert_rowsno sensitive capability
  • insert_tableno sensitive capability
  • inspectno sensitive capability
  • list_monitorsno sensitive capability
  • list_readersno sensitive capability
  • list_transportsno sensitive capability
  • modify_parano sensitive capability
  • modify_tableno sensitive capability
  • openno sensitive capability
  • readno sensitive capability
  • read_chartno sensitive capability
  • read_rangeno sensitive capability
  • recvno sensitive capability
  • rename_sheetno sensitive capability
  • reqano sensitive capability
  • screenshotno sensitive capability
  • scriptno sensitive capability
  • trace_clearno sensitive capability
  • trace_getno sensitive capability
  • transceiveno sensitive capability
  • versionno sensitive capability
  • workbook_grepno sensitive capability
  • workbook_metadatano sensitive capability
  • writeno sensitive capability
  • write_chartno sensitive capability
  • write_rangeno sensitive capability
  • wupano sensitive capability

What this scan could not see

Versions 2

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.5 latest A 95/100 0 1.13.0 2026-08-25
v0.1.3 A 95/100 0 1.12.1 2026-07-27

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

Use the free API → How scoring works

More in Developer Tools