updated 2026-11-11 00:08 UTC

Storeshots MCP

Repository

Store-ready App Store & Google Play screenshots from any MCP client. Device frames, benefit-driven headlines, exact store dimensions. No API keys.

MCP Servers TypeScript Listed MIT

Is Storeshots MCP safe? Thin or incomplete trust evidence. Review carefully before production use.

OSSF Scorecard 2.9 / 10
Provenance None
Signed commits 15%
Last push 30d ago
Advisories None known
Compare Storeshots MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Storeshots MCP scores 49.9/100 (Grade D), ranked #1011 of 1387 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: no package-provenance attestation found; OSSF Scorecard rates its supply-chain practices 2.9/10; 15% of recent commits are signed; no published advisory affects its latest release (storeshots-mcp); last pushed 2026-10-12. Every point is earned from checkable signals — never paid placement. How scoring works →

How Storeshots 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 Storeshots 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 Partly signed

    github.com/mtbun/storeshots-mcp, MIT, last pushed 2026-10-12. 15% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

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

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

  3. Published packages Linked, not attested

    • npm storeshots-mcp Source link points back to this repo No build attestation

    Without a build attestation, nothing proves the published files were built from this repository.

  4. What you install today No known advisories

    Latest release checked: storeshots-mcp 0.5.0. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-12 OSSF Scorecard: 2.4/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 Storeshots 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 Storeshots MCP compares in MCP Servers

  1. #569 Opendocswork MCP 50.0 +0.1
  2. #570 Reddit Research MCP 49.9 ±0
  3. #571 Storeshots MCP 49.9 this agent
  4. #572 MCP Server Infranodus 49.8 −0.1
  5. #573 Markdownify MCP 49.8 −0.1

Bars show each HVTrust score; the tick marks Storeshots MCP’s 49.9.

Where the 49.9 comes from

HVTrust dimensions vs the MCP Servers average

49.9 / 100 · 100.0% confidence

Storeshots MCP MCP Servers average (779 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
4.4 / 25
6.4 below avg 10.8
Identity / Provenance60% listing status · 40% build provenance
10.8 / 18
2.9 below avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.0 / 17
1.3 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
11.2 / 20
1.1 below avg 12.3
AdoptionLog-scaled stars · package downloads
6.8 / 20
0.8 below avg 7.6

Quick Trust Read

What Would Improve It
Publish package provenance or release attestations for stronger supply-chain evidence.
Recent Changes
2026-11-11
Grade Changed
Trust grade C → D
2026-11-09
Rank Moved
Rank dropped 16 spots (#993 → #1009)
2026-11-06
Rank Moved
Rank dropped 22 spots (#971 → #993)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 2.9/10. Tighten the weakest checks to improve public safety evidence.
Publish provenance Add package provenance or release attestations so users can verify where shipped artifacts came from.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
33.5
Activity sub-score · out of 100
#571
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 D 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-11 00:08 UTC · Repo last pushed 30 days ago

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
27
Forks
0
Last Push
2026-10-12
30 days ago
Commits (4 wk)
1
Downloads (7d)
294
npm
HN mentions (30d)
—
Open Issues
0
Rank Change
=
was #1011

Analysis

Activity Inputs

33.5 / 100
StarsRepository reach
8.7 / 30
FreshnessLast push recency
20.8 / 25
ActivityRecent commits
3.8 / 25
CommunityFork signal
0.0 / 20

Common questions about Storeshots MCP

Public trust evidence for Storeshots MCP is thin: several supply-chain signals are missing or weak. This does not mean the project is unsafe — it means an outside observer cannot easily verify the usual integrity checks. Treat with extra scrutiny.
Does Storeshots MCP publish package provenance?
No published build provenance is currently detected for Storeshots MCP. This is common for open-source projects but means consumers cannot independently verify that the package on the registry matches the GitHub source.
Does Storeshots MCP have an OpenSSF Scorecard?
Storeshots MCP has an OpenSSF Scorecard score of 2.9/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 Storeshots MCP actively maintained?
Maintained. Last push was 30 days ago.
What license does Storeshots MCP use?
Storeshots MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Storeshots MCP's commits signed?
15% of the last 100 commits to Storeshots 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
Storeshots MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
medium confidence
1 detected
Public provider/service dependencies detected.
Credential signal: No explicit API-key/config marker detected.
Tool / Plugin Surface
high confidence
Declared
Declared plugin/integration 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 Storeshots 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-10
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-10
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented

Maintain Storeshots MCP?

For maintainers

HVTrust scores Storeshots 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 30HVTrust 4Grade 4Score 2Scorecard 1Delisted 1Listed 1MCP 1Surface 1Surface 1
2026-11-11
Grade Changed
Trust grade C → D
2026-11-09
Rank Moved
Rank dropped 16 spots (#993 → #1009)
2026-11-06
Rank Moved
Rank dropped 22 spots (#971 → #993)
2026-10-28
Grade Changed
Trust grade D → C
2026-10-28
Rank Moved
Rank rose 80 spots (#1050 → #970)
2026-10-27
Grade Changed
Trust grade C → D
2026-10-27
Rank Moved
Rank dropped 98 spots (#952 → #1050)
2026-10-27
HVTrust Changed
HVTrust down 3.4pts (52.3 → 48.9)
2026-10-26
Rank Moved
Rank rose 24 spots (#976 → #952)
2026-10-21
Rank Moved
Rank rose 21 spots (#982 → #961)
2026-10-16
Rank Moved
Rank dropped 11 spots (#950 → #961)
2026-10-15
Rank Moved
Rank rose 17 spots (#967 → #950)
2026-10-14
Rank Moved
Rank dropped 12 spots (#955 → #967)
2026-10-13
Rank Moved
Rank dropped 10 spots (#945 → #955)
2026-10-12
Rank Moved
Rank rose 23 spots (#968 → #945)
2026-10-10
Tool Surface Changed
Detected tool/plugin surface changed: none → declared
2026-10-10
Provider Added
Runtime surface grew — new detected provider dependency: Anthropic
2026-10-10
Grade Changed
Trust grade D → C
2026-10-10
Rank Moved
Rank rose 135 spots (#1100 → #965)
2026-10-10
HVTrust Changed
HVTrust up 5.8pts (44.8 → 50.6)
2026-10-10
Activity Score Changed
Activity score up 14pts (24 → 37)
2026-09-26
Rank Moved
Rank rose 11 spots (#1069 → #1058)
2026-09-25
Rank Moved
Rank dropped 10 spots (#1059 → #1069)
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Rank Moved
Rank rose 161 spots (#1211 → #1050)
2026-09-23
HVTrust Changed
HVTrust up 27.1pts (18.3 → 45.4)
2026-09-22
Newly Listed
First tracked at rank #1211
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-20
Rank Moved
Rank dropped 12 spots (#1038 → #1050)
2026-09-18
Rank Moved
Rank rose 23 spots (#1057 → #1034)
2026-09-12
Scorecard Added
OSSF Scorecard: 2.4/10
2026-09-12
Rank Moved
Rank rose 261 spots (#1320 → #1059)
2026-09-12
HVTrust Changed
HVTrust up 26.3pts (18.6 → 44.9)
2026-09-02
Rank Moved
Rank dropped 15 spots (#1272 → #1287)
2026-09-01
Rank Moved
Rank dropped 18 spots (#1254 → #1272)
2026-08-31
Rank Moved
Rank dropped 13 spots (#1241 → #1254)
2026-08-30
Rank Moved
Rank dropped 18 spots (#1223 → #1241)
2026-08-29
Rank Moved
Rank dropped 49 spots (#1174 → #1223)
2026-08-29
Activity Score Changed
Activity score down 8pts (36 → 29)
2026-08-28
Rank Moved
Rank dropped 18 spots (#1156 → #1174)
2026-08-27
Rank Moved
Rank dropped 14 spots (#1142 → #1156)
2026-08-26
Rank Moved
Rank dropped 59 spots (#1083 → #1142)
2026-08-19
Rank Moved
Rank dropped 19 spots (#1054 → #1073)
2026-08-18
Rank Moved
Rank dropped 25 spots (#1029 → #1054)
2026-08-17
Rank Moved
Rank rose 12 spots (#1041 → #1029)
2026-08-16
Rank Moved
Rank dropped 28 spots (#1013 → #1041)
GitHub → npm: storeshots-mcp

Embed Badge Badge guide for maintainers →

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

Other agents in MCP Servers

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