Carrot MCP Server
carrot-mcp
PyPI
v0.1.3
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.
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 − 2.1 = 98. What the published surface and source actually contain:
| Points | What was found | Category |
|---|---|---|
| −2.1 | Package has no source repository MTC-SUP-011 | supply-chain |
2. Client adoption risk — 98 − 8 = 90. 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:
| Points | Adoption-risk factor |
|---|---|
| −3 | capability blast radius (moderate) — client exposure if the model is manipulated |
| −5 | publisher verification (unlocatable) — no provenance and no public repository to inspect |
| ✓ | inspection depth (source) — how much of the target the scan could see |
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 1
low Package has no source repositoryMTC-SUP-011
"carrot-mcp" declares no repository URL, so its published artifact cannot be compared against reviewable source.
Fix: Prefer packages that link to public, reviewable source.
Location: package carrot-mcp
Tools 60
Each tool and what it can reach — statically extracted from the published source.
get_outlineingests untrusted inputget_pagesingests untrusted inputanticollno sensitive capabilitybackup_historyno sensitive capabilitybackup_restoreno sensitive capabilitycloseno sensitive capabilityconnectno sensitive capabilitycopy_rangeno sensitive capabilitycreate_sheetno sensitive capabilitydelete_columnsno sensitive capabilitydelete_imageno sensitive capabilitydelete_parano sensitive capabilitydelete_rangeno sensitive capabilitydelete_rowsno sensitive capabilitydelete_sheetno sensitive capabilitydelete_tableno sensitive capabilitydisconnectno sensitive capabilityfield_offno sensitive capabilityfield_onno sensitive capabilityfindno sensitive capabilityformat_parano sensitive capabilityformat_rangeno sensitive capabilityformat_tableno sensitive capabilityget_contentno sensitive capabilityget_tableno sensitive capabilityget_tocno sensitive capabilitygrepno sensitive capabilityhaltno sensitive capabilityhistoryno sensitive capabilityinsert_columnsno sensitive capabilityinsert_imageno sensitive capabilityinsert_parano sensitive capabilityinsert_rowsno sensitive capabilityinsert_tableno sensitive capabilityinspectno sensitive capabilitylist_monitorsno sensitive capabilitylist_readersno sensitive capabilitylist_transportsno sensitive capabilitymodify_parano sensitive capabilitymodify_tableno sensitive capabilityopenno sensitive capabilityreadno sensitive capabilityread_chartno sensitive capabilityread_rangeno sensitive capabilityrecvno sensitive capabilityrename_sheetno sensitive capabilityreqano sensitive capabilityscreenshotno sensitive capabilityscriptno sensitive capabilityselectno sensitive capabilitytrace_clearno sensitive capabilitytrace_getno sensitive capabilitytransceiveno sensitive capabilityversionno sensitive capabilityworkbook_grepno sensitive capabilityworkbook_metadatano sensitive capabilitywriteno sensitive capabilitywrite_chartno sensitive capabilitywrite_rangeno sensitive capabilitywupano sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (60 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Versions
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.1.3 latest |
A 90/100 | 1 | 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.
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 pypiMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Agent MCP server.