spreadsheet-kit MCP
MCP server for spreadsheet analysis and editing. Slim, token-efficient tool surface designed for LLM agents.
Is spreadsheet-kit MCP safe? Thin or incomplete trust evidence. Review carefully before production use.
Compare spreadsheet-kit MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: spreadsheet-kit MCP scores 42.5/100 (Grade D), ranked #1168 of 1378 tracked open-source AI agent projects, on evidence coverage C (2 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 3.3/10; 10% of recent commits are signed; last pushed 2026-09-09. Every point is earned from checkable signals — never paid placement. How scoring works →
How spreadsheet-kit MCP could raise its score
Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.
- Raise the OSSF Scorecard from 3.3 to 9.0lowest checks: Branch-Protection 0, CII-Best-Practices 0, Code-Review 0 +12.0 → 54.5 C · #466 of 781
- Sign every commit10% signed today +4.5 → 47.0 D · #616 of 781
Chain of custody
Scanners check what the code says. This traces who ships spreadsheet-kit MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the code you run. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.
-
Source Partly signed
github.com/PSU3D0/agent-spreadsheet, Apache-2.0, last pushed 2026-09-09. 10% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.
-
Review and release Weak
OpenSSF Scorecard rates the repository's practices 3.3/10 (scanned Oct 16, 2026). The checks that decide who can get a change released:
- Code Review0
- Branch Protection0
- Signed Releases0
- Dangerous Workflow10
- Token Permissions0
- Pinned Dependencies0
All 18 Scorecard checks
Binary-Artifacts 10Branch-Protection 0CI-Tests 10CII-Best-Practices 0Code-Review 0Contributors 0Dangerous-Workflow 10Dependency-Update-Tool 0Fuzzing 0License 10Maintained 10Packaging 10Pinned-Dependencies 0SAST 0Security-Policy 0Signed-Releases 0Token-Permissions 0Vulnerabilities 0 -
Published packages None
Distributed as the container image ghcr.io/psu3d0/spreadsheet-mcp:0.11.1-full; HVTracker doesn't check that registry's source link yet.
Changes to this chain
- 2026-08-29 OSSF Scorecard: 3.3/10
Evidence behind this score
Coverage C: 2 of 5 independent evidence types found.
- GitHub repository data
- Package downloads (missing)
- Supply-chain checks
- Public actions (missing)
- Community mentions (missing)
Verify this score yourself
Every build re-issues spreadsheet-kit MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.
What this score doesn’t check
It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.
How spreadsheet-kit MCP compares in MCP Servers
- #671 Deployhq MCP Server 42.9 +0.4
- #672 Loomle 42.6 +0.1
- #673 spreadsheet-kit MCP 42.5 this agent
- #674 Kolada MCP Server 42.4 −0.1
- #675 MCP Mermaid 42.4 −0.1
Bars show each HVTrust score; the tick marks spreadsheet-kit MCP’s 42.5.
Where the 42.5 comes from
HVTrust dimensions vs the MCP Servers average
42.5 / 100 · 100.0% confidencespreadsheet-kit MCP MCP Servers average (781 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade D reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage C is separate — it grades how many independent signal types back the score (2 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
35.0 / 100Common questions about spreadsheet-kit MCP
Does spreadsheet-kit MCP publish package provenance?
Does spreadsheet-kit MCP have an OpenSSF Scorecard?
Is spreadsheet-kit MCP actively maintained?
What license does spreadsheet-kit MCP use?
Are spreadsheet-kit MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to spreadsheet-kit MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain spreadsheet-kit MCP?
For maintainers
HVTrust scores spreadsheet-kit MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/spreadsheet-kit-mcp)
<a href="https://hvtracker.net/agents/spreadsheet-kit-mcp"><img src="https://hvtracker.net/badge/spreadsheet-kit-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON