updated 2026-11-10 04:07 UTC

Excel Vision MCP

Repository

MCP server that lets AI agents SEE embedded images inside Excel files — full text + image extraction for .xlsx/.xlsm

MCP Servers Python Listed MIT

Is Excel Vision MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.3 / 10
Provenance Attested
Signed commits 0%
Last push 102d ago
Advisories None known
Compare Excel Vision MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Excel Vision MCP scores 57.3/100 (Grade C), ranked #785 of 1374 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.3/10; recent commits are unsigned; no published advisory affects its latest release (excel-vision-mcp); last pushed 2026-07-31. Every point is earned from checkable signals — never paid placement. How scoring works →

How Excel Vision 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.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Excel Vision MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Unsigned

    github.com/VOYAGER-Inc/excel-vision-mcp, MIT, last pushed 2026-07-31. None of the last 100 commits carry a verified signature, so no change traces to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.3/10 (scanned Nov 3, 2026). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection8
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies0
    All 18 Scorecard checks
    Binary-Artifacts 10
    Branch-Protection 8
    CI-Tests -1
    CII-Best-Practices 0
    Code-Review 0
    Contributors 0
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 0
    Packaging 10
    Pinned-Dependencies 0
    SAST 0
    Security-Policy 0
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • PyPI excel-vision-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: excel-vision-mcp 1.2.1. No published advisory affects it (OSV, checked 2026-11-09).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-09-02 OSSF Scorecard: 4.0/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Excel Vision 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.

Signed credential (JSON) How to verify

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 Excel Vision MCP compares in MCP Servers

  1. #424 MCP Me 57.4 +0.1
  2. #425 AEC Model Bridge 57.3 ±0
  3. #426 Excel Vision MCP 57.3 this agent
  4. #427 Runapi Ai MCP 57.2 −0.1
  5. #428 Pyslang MCP 57.2 −0.1

Bars show each HVTrust score; the tick marks Excel Vision MCP’s 57.3.

Where the 57.3 comes from

HVTrust dimensions vs the MCP Servers average

57.3 / 100 · 100.0% confidence

Excel Vision MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.6 / 25
0.8 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.3 / 17
1.0 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
5.2 / 20
7.0 below avg 12.2
AdoptionLog-scaled stars · package downloads
5.2 / 20
2.4 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-10-30
Rank Moved
Rank dropped 35 spots (#722 → #757)
2026-10-29
Activity Went Stale
No commits for 90 days
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.3/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Refresh maintenance signals The repo was last pushed 102 days ago. Fresh activity helps separate stable projects from stale ones.
Compare with another agent
View MCP Servers Report missing data
21.1
Activity sub-score · out of 100
#426
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed 102 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
20
Forks
2
Last Push
2026-07-31
102 days ago
Commits (4 wk)
0
Downloads (7d)
35
pypi
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #785

Analysis

Activity Inputs

21.1 / 100
StarsRepository reach
7.9 / 30
FreshnessLast push recency
10.8 / 25
ActivityRecent commits
0.0 / 25
CommunityFork signal
2.2 / 20

Common questions about Excel Vision MCP

Excel Vision MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Excel Vision MCP publish package provenance?
Yes. Excel Vision MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Excel Vision MCP have an OpenSSF Scorecard?
Excel Vision MCP has an OpenSSF Scorecard score of 3.3/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Excel Vision MCP actively maintained?
Slowing down. Last push was 102 days ago — keep an eye on whether activity resumes.
What license does Excel Vision MCP use?
Excel Vision MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Excel Vision MCP's commits signed?
0% of the last 100 commits to Excel Vision MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 Server Support
high confidence
Implemented
Excel Vision MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
None detected
No clear third-party provider dependency detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
None detected
No clear plugin system or broad tool surface detected.
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

Detected changes to Excel Vision 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.

2026-10-29
Activity Went Stale
No commits for 90 days
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

Maintain Excel Vision MCP?

For maintainers

HVTrust scores Excel Vision 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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 24HVTrust 2Score 1Scorecard 1Delisted 1Listed 1Grade 1Provenance 1MCP 1Stale 1
2026-10-30
Rank Moved
Rank dropped 35 spots (#722 → #757)
2026-10-29
Activity Went Stale
No commits for 90 days
2026-10-09
Rank Moved
Rank dropped 13 spots (#663 → #676)
2026-10-03
Rank Moved
Rank dropped 10 spots (#635 → #645)
2026-10-02
Rank Moved
Rank dropped 51 spots (#584 → #635)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 592 spots (#1152 → #560)
2026-09-23
HVTrust Changed
HVTrust up 41.7pts (20.6 → 62.3)
2026-09-22
Newly Listed
First tracked at rank #1152
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-11
Rank Moved
Rank dropped 11 spots (#497 → #508)
2026-09-08
Rank Moved
Rank dropped 13 spots (#482 → #495)
2026-09-07
Rank Moved
Rank dropped 32 spots (#450 → #482)
2026-09-05
Rank Moved
Rank dropped 74 spots (#368 → #442)
2026-09-04
Rank Moved
Rank dropped 12 spots (#356 → #368)
2026-09-03
Rank Moved
Rank dropped 45 spots (#311 → #356)
2026-09-02
Scorecard Added
OSSF Scorecard: 4.0/10
2026-09-02
Rank Moved
Rank rose 203 spots (#514 → #311)
2026-09-02
HVTrust Changed
HVTrust up 8.3pts (56.2 → 64.5)
2026-09-01
Rank Moved
Rank dropped 10 spots (#504 → #514)
2026-08-31
Rank Moved
Rank dropped 35 spots (#469 → #504)
2026-08-30
Rank Moved
Rank dropped 51 spots (#418 → #469)
2026-08-30
Activity Score Changed
Activity score down 8pts (38 → 31)
2026-08-29
Rank Moved
Rank dropped 24 spots (#394 → #418)
2026-08-28
Rank Moved
Rank dropped 16 spots (#378 → #394)
2026-08-26
Rank Moved
Rank dropped 37 spots (#335 → #372)
2026-08-24
Rank Moved
Rank dropped 22 spots (#310 → #332)
2026-08-22
Rank Moved
Rank rose 16 spots (#328 → #312)
2026-08-19
Rank Moved
Rank dropped 18 spots (#309 → #327)
2026-08-17
Rank Moved
Rank rose 18 spots (#328 → #310)
2026-08-15
Rank Moved
Rank dropped 25 spots (#295 → #320)
2026-08-13
Rank Moved
Rank dropped 18 spots (#273 → #291)
GitHub → PyPI: excel-vision-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 57.3 Grade C
Markdown:
[![HVTrust](https://hvtracker.net/badge/excel-vision-mcp.svg)](https://hvtracker.net/agents/excel-vision-mcp)
HTML:
<a href="https://hvtracker.net/agents/excel-vision-mcp"><img src="https://hvtracker.net/badge/excel-vision-mcp.svg" alt="HVTrust"></a>

Other agents in MCP Servers

Data sources
GitHub REST API (repo, commits, stars, forks, license) · PyPI / pypistats (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.4 · Raw JSON