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.maxigirl123/storefront-guard

NPM · STOREFRONT-GUARD-MCP-SERVER · SCANNED SEP 24

Verifies a merchant storefront is legitimate before an AI agent commits payment.

Available components

npm · storefront-guard-mcp-server 77
+3 this week 77 Trust /100
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 Security98
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • 42 of 131 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency32
Schema Quality & AI Usability63
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 627 tokens (~627/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management87
  • Stability observed for 26 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 1 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
Install

How do I install the io.github.maxigirl123/storefront-guard MCP server?

io.github.maxigirl123/storefront-guard runs locally as an npm package, launched with npx -y storefront-guard-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

npm · storefront-guard-mcp-server

# add to Claude Code
claude mcp add maxigirl123-storefront-guard -- npx -y storefront-guard-mcp-server
// .cursor/mcp.json
{
  "mcpServers": {
    "maxigirl123-storefront-guard": {
      "command": "npx",
      "args": [
        "-y",
        "storefront-guard-mcp-server"
      ]
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "maxigirl123-storefront-guard": {
      "command": "npx",
      "args": [
        "-y",
        "storefront-guard-mcp-server"
      ]
    }
  }
}
# add to Codex CLI
codex mcp add maxigirl123-storefront-guard -- npx -y storefront-guard-mcp-server
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "maxigirl123-storefront-guard": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "storefront-guard-mcp-server"
      ],
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add maxigirl123-storefront-guard --command npx --arg -y --arg storefront-guard-mcp-server
# ~/.hermes/config.yaml
mcp_servers:
  maxigirl123-storefront-guard:
    command: "npx"
    args: ["-y", "storefront-guard-mcp-server"]
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "maxigirl123-storefront-guard": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "storefront-guard-mcp-server"
      ]
    }
  }
}
# add to Vellum
assistant mcp add maxigirl123-storefront-guard -t stdio -c npx -a -y storefront-guard-mcp-server
// mcp.json
{
  "mcpServers": {
    "maxigirl123-storefront-guard": {
      "command": "npx",
      "args": [
        "-y",
        "storefront-guard-mcp-server"
      ]
    }
  }
}
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.

  • 23 Sept 26 +1

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

  • 21 Sept 26 +1

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

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 15 Sept 26 +2
    • CVE-2026-82562 no longer affects this package ▲ security
    • CVE-2026-82417 no longer affects this package ▲ security
    • Known CVEs: fail → pass ▲ security
  • 13 Sept 26 +1

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

  • 11 Sept 26 +1

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

  • 9 Sept 26 +1

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

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 24 Sept 2026 · Analysed npm/storefront-guard-mcp-server@0.3.2

Provenance No attestation

The registry publishes no build provenance for this version, so there is nothing to verify.

Result No attestation
Ecosystem npm

Background: How many MCP packages publish verified provenance →

Dependencies 131 packages
Packages resolved 131
Stale 42
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 1 exposed · ~627 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
verify_storefront ~627

Checks whether a merchant storefront looks like the same legitimate entity it appeared to be recently, BEFORE an agent commits payment to it. This is the mirror image of merchant-side agent-verification protocols (e.g. Visa's Trusted Agent Protocol): those let a merchant confirm an incoming agent is legitimate. This tool lets the AGENT confirm the MERCHANT is legitimate before paying. It does NOT guarantee a storefront is safe - it is a fast, explainable pre-purchase signal built from free public data sources (domain registration history via RDAP, SSL certificate issuance history via Certificate Transparency logs, HTTPS validity, and a known-scam-domain check). Treat a "high" risk result as a strong reason to pause and get human confirmation before paying, and a "low" risk result as one input among others, not a guarantee. Args: - domain (string): the bare domain of the storefront to check, e.g. "example-shop.com" Returns: { "domain": string, "trustScore": number, // 0-100, higher = more trustworthy "riskLevel": "low" | "medium" | "high" | "unknown", "confidence": "low" | "medium" | "high", // how many signals could actually be resolved "reasons": string[], // human-readable explanation for the score "recommendation": "proceed" | "pause_for_confirmation" | "do_not_proceed", "recommendationReason": string, // one-line explanation of why this recommendation was made "signals": { ...raw signal data for audit/debugging... }, "checkedAt": string // ISO timestamp - this is a point-in-time result, do not cache it } Recommendation values and suggested agent behavior: - "proceed": trust score is high with high confidence — complete the transaction silently, no user confirmation needed - "pause_for_confirmation": score is borderline or confidence is insufficient — pause and show recommendationReason to the user before completing payment - "do_not_proceed": domain matched a scam list or trust score is…

NameTypeReqDescription
domainstringyesThe bare domain of the storefront to verify, e.g. 'example-shop.com'. Strip protocol and path if given a full URL.

No output schema declared.

No examples provided.

Common questions

What is the io.github.maxigirl123/storefront-guard MCP server?

io.github.maxigirl123/storefront-guard is an MCP server listed in the public MCP registry as io.github.maxigirl123/storefront-guard. Verifies a merchant storefront is legitimate before an AI agent commits payment. This page covers its npm package (storefront-guard-mcp-server).

Is the io.github.maxigirl123/storefront-guard MCP server safe to use?

io.github.maxigirl123/storefront-guard scores 77 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 24 September 2026. It declares no install or post-install scripts. 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.maxigirl123/storefront-guard MCP server expose?

io.github.maxigirl123/storefront-guard exposes 1 tool: verify_storefront. Their descriptions and schemas cost roughly 627 tokens of context every time the server is loaded.

Is the io.github.maxigirl123/storefront-guard MCP server still maintained?

io.github.maxigirl123/storefront-guard is still listed as active in the MCP registry. We last reached this channel on 24 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.