Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Storefront Guard
Overview
Description from the maker (original English)
Verifies a merchant storefront is legitimate before an AI agent commits payment.
PopNx MCP’s three pillars
These three are never merged into one score: opinions, measurements and popularity are different things.
- User voiceiNo reviews yetReviews open together with accounts in a later step
- Our basic checksi1 of 1 passedChecked from public information; code not scanned yet
- UsageiNot measured yet★ –
What you can do with it
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
- Connection: Runs on your computer
- Transport: stdio
- Category: Online shops & payments
- You need to fill in: GOOGLE_SAFE_BROWSING_API_KEY, SAM_GOV_API_KEY, URLHAUS_AUTH_KEY
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on your computer with your user’s permissions (files, network, apps).
- You fill in yourself:
GOOGLE_SAFE_BROWSING_API_KEY,SAM_GOV_API_KEY,URLHAUS_AUTH_KEY
Values marked secret are keys to your account. Never share them or paste them into a chat.
You need
- npmNode.js installed (for the npx command)
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"storefront-guard": {
"command": "npx",
"args": [
"-y",
"storefront-guard-mcp-server"
],
"env": {
"GOOGLE_SAFE_BROWSING_API_KEY": "your-value",
"SAM_GOV_API_KEY": "your-value",
"URLHAUS_AUTH_KEY": "your-value"
}
}
}
}Run this in your terminal
claude mcp add storefront-guard --env GOOGLE_SAFE_BROWSING_API_KEY=your-value --env SAM_GOV_API_KEY=your-value --env URLHAUS_AUTH_KEY=your-value -- npx -y storefront-guard-mcp-serverFill in the empty values before running it.
Or copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"storefront-guard": {
"command": "npx",
"args": [
"-y",
"storefront-guard-mcp-server"
],
"env": {
"GOOGLE_SAFE_BROWSING_API_KEY": "your-value",
"SAM_GOV_API_KEY": "your-value",
"URLHAUS_AUTH_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Or copy the settings yourself
Paste into .vscode/mcp.json in your project
{
"servers": {
"storefront-guard": {
"type": "stdio",
"command": "npx",
"args": [
"-y",
"storefront-guard-mcp-server"
],
"env": {
"GOOGLE_SAFE_BROWSING_API_KEY": "your-value",
"SAM_GOV_API_KEY": "your-value",
"URLHAUS_AUTH_KEY": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
Values you fill in
- Google Safe Browsing API key for scam domain checks. Optional — degrades gracefully if not set.
- SAM.gov API key for US federal exclusions check. Optional — skipped if not set.
- URLhaus Auth-Key for malware URL lookups. Optional — degrades gracefully if not set.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
Runs on your computer; the tool list appears in your AI app after you install it.
Basic checksi
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
- ✓ Pass
Maker matches the repo
The registry name was verified with the GitHub account maxigirl123, which owns the repo
- … Not checked yet
Still maintained
We have not read this repo from GitHub yet
- … Not checked yet
Has a licence
We have not read this repo from GitHub yet
- – Not applicable
Endpoint responds
This one runs on your computer; there is no internet endpoint
- – Not applicable
Sign-in with OAuth
Runs on your computer and uses local settings instead
- … Not checked yet
No hidden instructions in tool descriptions
Runs on your computer; we can only read tool lists from internet endpoints
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1753 servers in this category
- Published to the registry more recently than 34% of the other 1753 servers in this category
- Basic checks equal to or better than 100% of the other 1753 servers in this category
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
Common questions
Is Storefront Guard safe?
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
What keys or codes does it need?
You need to fill in: GOOGLE_SAFE_BROWSING_API_KEY, SAM_GOV_API_KEY, URLHAUS_AUTH_KEY
Does it run on my computer or in the cloud?
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.2) reached the registry 2 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.
What can I use instead?
In the same category: Spree Commerce: open-source B2B and marketplace ecommerce, Stripe MCP, MCP Cn Commerce
Alternatives
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
Stripe MCP
Stripe’s official server lets AI view and manage customers, products, payments and invoices. Connect to Stripe’s cloud and sign in with OAuth.
MCP Cn Commerce
8 read-only MCP platform entries; support is operation-specific; merchant live acceptance pending
README from the maker
Open the README
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
Fortik
Real-time merchant verification for agentic commerce. A shopping agent calls verify_storefront with a domain before paying, and gets back a trust score with a plain-English verdict the agent can act on — in under two seconds.
Fortik is the trust check AI shopping agents run before checkout. It doesn't ask merchants to register in advance — it gathers evidence directly, in the moment, from independent public sources.
[fortik.io](https://fortik.io)
This is the mirror image of merchant-side agent-verification protocols like Visa's Trusted Agent Protocol: those let a *merchant* confirm an incoming *agent* is legitimate. Fortik lets the *agent* confirm the *merchant* is legitimate before committing payment.
What it checks
- Domain registration age & recent changes — via free public RDAP lookups. A domain registered days ago, or one whose registration data changed in the last two weeks, is a red flag.
- SSL certificate issuance history — via free public Certificate Transparency logs (crt.sh). A cert reissued very recently on an otherwise long-established domain can indicate a takeover or hosting change, even when the domain itself looks old and trustworthy.
- HTTPS validity — does the site currently serve a valid cert at all.
- Known-scam blocklist — URLhaus and Google Safe Browsing.
- Corporate registration — US entity lookup via OpenCorporates.
- Legal name verification — GLEIF entity registry cross-check.
- Web traffic rank — Tranco top-1M ranking.
- Federal exclusions — SAM.gov debarment check.
- FDA enforcement — corroborating signal when other risks are present.
Every deduction from the trust score comes with a plain-English reason in the reasons array — this is deliberately an explainable heuristic, not a black-box model.
Setup
Requires Node.js 18+.
npm install
npm run build
Copy .env.example to .env and fill in your keys.
Running it
As a local MCP server (stdio):
npm start
As a remote MCP server (streamable HTTP) with x402 payment:
npm run start:http
POST http://localhost:3000/mcp
As a pay-per-call x402 HTTP API:
npm run start:x402
POST http://localhost:4021/verify { "domain": "example-shop.com" }
As a REST API (API key auth):
npm run start:rest
POST http://localhost:4022/verify { "domain": "example-shop.com" }
Header: X-API-KEY: your-key
All three servers at once:
npm run start:all
MCP: http://localhost:3000/mcp
x402: http://localhost:4021/verify
REST: http://localhost:4022/verify
Feedback endpoint
Submit outcome data after a transaction to help build training data for future ML scoring:
POST http://localhost:4022/feedback
Header: X-API-KEY: your-key Body: { "domain": "example-shop.com", "outcome": "legit" | "scam" }
How to use the recommendation field
Every verification result includes a top-level recommendation string alongside the numeric trustScore. Agents should branch on it rather than implementing their own threshold logic against the raw score.
| Value | Suggested agent behavior |
|---|---|
proceed | Complete the transaction silently. Trust score is low-risk with high confidence. |
pause_for_confirmation | Stop before paying and show recommendationReason to the user. |
do_not_proceed | Block the transaction and actively notify the user — do not fail silently. |
recommendationReason is a one-line plain-English explanation safe to show directly to users.
Pricing
$0.01/call via x402. Set your wallet address in PAY_TO_ADDRESS and network in X402_NETWORK (default: base).
Environment variables
| Variable | Required | Description |
|---|---|---|
PAY_TO_ADDRESS | Yes (x402) | Your wallet address for USDC payments |
X402_NETWORK | No | Blockchain network (default: base) |
PRICE_USD | No | Per-call price (default: 0.01) |
API_KEYS | Yes (REST) | Comma-separated valid API keys |
GOOGLE_SAFE_BROWSING_API_KEY | No | Degrades gracefully if unset |
SAM_GOV_API_KEY | No | Degrades gracefully if unset |
URLHAUS_AUTH_KEY | No | Degrades gracefully if unset |
FEEDBACK_LOG | No | Path for feedback JSONL log (default: feedback.jsonl) |
MCP_PORT | No | MCP server port (default: 3000) |
X402_PORT | No | x402 server port (default: 4021) |
REST_PORT | No | REST API port (default: 4022) |