Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.helloo1568/sheetspec

PYPI · SHEETSPEC

Contract testing and quality gates for spreadsheets created by AI agents.

Available components

−17 this week 67 Trust /100

Last scanned (just now)

Scores higher than 63% of PyPI servers

Category Testing and QA

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security49
  • Malware scan not yet available for this package.Unverified
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • 5 of 41 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency71
  • Repository check failed: the declared repository URL returned HTTP 404. See how to fix → View diagnostics → Fail
  • Cryptographically verified build provenance (signed, bound to helloo1568/SheetSpec). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 109 days ago).Pass
  • Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability60
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 251 tokens (~50/item across 5 items; 5 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management80
  • Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.

  • 4 Nov 26 −18
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.77 functional
  • 3 Nov 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 29 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
    • Stability: 0.97 → pass security
  • 28 Oct 26 0
    • Stability: pass → 0.97 functional
  • 23 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 22 Oct 26 0
    • Stability: 0.97 → pass security
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/sheetspec@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo helloo1568/SheetSpec
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/helloo1568/SheetSpec/.github/workflows/publish.yml@refs/tags/v0.1.2
Rekor log index 2194724635
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:b76bcc50484efa7b5ae56c4fd468fadb9ea4e0c90edd598773100bc808b687c0

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted hatchling.build

Background: Why install scripts are a supply-chain risk →

Dependencies 41 packages
Packages resolved 41
Stale 5
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 5 exposed · ~212 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
compare_workbooks ~47

Compare workbook values, formulas, and worksheet changes.

NameTypeReqDescription
after_pathstringyes–
before_pathstringyes–
cell_range–––
sheet_name–––

Structured output declared, but exposes no named fields.

No examples provided.

draft_workbook_spec ~29

Create a reviewable YAML contract draft from workbook structure.

NameTypeReqDescription
file_pathstringyes–
NameTypeReqDescription
resultstringyes–

No examples provided.

generate_validation_report ~56

Validate a workbook and write a self-contained HTML report.

NameTypeReqDescription
baseline_path–––
file_pathstringyes–
lock_path–––
output_pathstringyes–
spec_pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

inspect_workbook ~30

Read workbook structure, sheets, used ranges, and formula counts.

NameTypeReqDescription
file_pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

validate_workbook ~50

Validate a workbook against an explicit contract and return repair-friendly JSON.

NameTypeReqDescription
baseline_path–––
file_pathstringyes–
lock_path–––
spec_pathstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the io.github.helloo1568/sheetspec MCP server?

io.github.helloo1568/sheetspec runs locally as a PyPI package, launched with uvx sheetspec. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · sheetspec

# add to Claude Code
claude mcp add helloo1568-sheetspec -- uvx sheetspec
Common questions

What is the io.github.helloo1568/sheetspec MCP server?

io.github.helloo1568/sheetspec is an MCP server listed in the public MCP registry as io.github.helloo1568/sheetspec. Contract testing and quality gates for spreadsheets created by AI agents. This page covers its PyPI package (sheetspec).

Is the io.github.helloo1568/sheetspec MCP server safe to use?

io.github.helloo1568/sheetspec scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the io.github.helloo1568/sheetspec MCP server expose?

io.github.helloo1568/sheetspec exposes 5 tools: inspect_workbook, draft_workbook_spec, validate_workbook, compare_workbooks, generate_validation_report. Their descriptions and schemas cost roughly 212 tokens of context every time the server is loaded.

Is the io.github.helloo1568/sheetspec MCP server still maintained?

io.github.helloo1568/sheetspec is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.helloo1568/sheetspec MCP server under?

io.github.helloo1568/sheetspec declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.