Is io.github.ihint/merchant-context safe to use?

io.github.ihint/merchant-context has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.

How do I install io.github.ihint/merchant-context?

io.github.ihint/merchant-context supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.

What AI clients work with io.github.ihint/merchant-context?

io.github.ihint/merchant-context is compatible with claude-desktop, cursor, claude-code. It uses http transport.

Is io.github.ihint/merchant-context actively maintained?

io.github.ihint/merchant-context is actively maintained — last commit was 1 day ago.

io.github.ihint/merchant-context

wrangler

Check whether a merchant exposes the public files buyer agents need.

19.4M/wk GitHub npm

No known CVEs

MIT license

Actively maintained

Last commit 1d ago

Works with most clients

Transport: http

0 tools

Grade F

MCPpedia last refreshed this data 11h ago

Edit this pageView history

io.github.ihint/merchant-context is an MCP server that check whether a merchant exposes the public files buyer agents need. Its tool list has not been published yet over http, requires no API key, and scores 64/100 on MCPpedia's security, maintenance and efficiency rubric.

E-Commerce

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktophttp · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-ihint-merchant-context": {
      "args": [
        "-y",
        "wrangler"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-ihint-merchant-context)](https://mcppedia.org/s/io-github-ihint-merchant-context)

Read me

What io.github.ihint/merchant-context does

Merchant Context is an open merchant preflight for agent builders.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'wrangler' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

64/100across 5 weighted dimensions

How we score →

0255075100

−36

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

4 fixed

CVE-2026-0933high · fixed

Wrangler affected by OS Command Injection in `wrangler pages deploy`

**Summary** A command injection vulnerability (CWE-78) has been found to exist in the `wrangler pages deploy` command. The issue occurs because the `--commit-hash` parameter is passed directly to a shell command without proper validation or sanitization, allowing an attacker with control of `--commit-hash` to execute arbitrary commands on the system running Wrangler. **Root cause** The `commitHash` variable, derived from user input via the `--commit-hash` CLI argument, is interpolated directl

Affected: >= 2.0.15Fixed in 3.114.17source →

CVE-2023-7080critical · fixedCVSS 9.3

Arbitrary remote code execution within `wrangler dev` Workers sandbox

### Impact The V8 inspector intentionally allows arbitrary code execution within the Workers sandbox for debugging. `wrangler dev` would previously start an inspector server listening on all network interfaces. This would allow an attacker on the local network to connect to the inspector and run arbitrary code. Additionally, the inspector server did not validate `Origin`/`Host` headers, granting an attacker that can trick any user on the local network into opening a malicious website the ability

Affected: >= 3.0.0Fixed in 3.19.0source →

CVE-2023-7079medium · fixedCVSS 6.9

Arbitrary remote file read in Wrangler dev server

### Impact Sending specially crafted HTTP requests and inspector messages to Wrangler's dev server could result in any file on the user's computer being accessible over the local network. An attacker that could trick any user on the local network into opening a malicious website could also read any file. ### Patches This issue was fixed in `wrangler@3.19.0`. Wrangler will now only serve files that are part of your bundle, or referenced by your bundle's source maps. ### Workarounds Configure Wr

Affected: >= 3.9.0Fixed in 3.19.0source →

CVE-2023-3348medium · fixedCVSS 5.7

Cloudflare Wrangler directory traversal vulnerability

### Impact The Wrangler command line tool (<=wrangler@3.1.0 or <=wrangler@2.20.1) was affected by a directory traversal vulnerability when running a local development server for Pages (wrangler pages dev command). This vulnerability enabled an attacker in the same network as the victim to connect to the local development server and access the victim's files present outside of the directory for the development server. ### Patches Wrangler2: Upgrade to v2.20.1 or higher. Wrangler3: Upgrade to v3

Affected: >= 0Fixed in 2.20.1source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.ihint/merchant-context safe to use?: io.github.ihint/merchant-context has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.ihint/merchant-context?: io.github.ihint/merchant-context supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.ihint/merchant-context?: io.github.ihint/merchant-context is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Is io.github.ihint/merchant-context actively maintained?: io.github.ihint/merchant-context is actively maintained — last commit was 1 day ago.

Similar servers

Others in ecommerce

View all →

Ru Marketplace Mcp93

Девять российских маркетплейсов и китайский Taobao как MCP-серверы: Wildberries, Ozon, Яндекс Маркет, Детский мир, Авито, Мегамаркет, Lamoda, DNS, Ситилинк. Плюс сравнение цен по всем сразу. Только чтение, ключи не нужны.

73 8

io.github.geoacpfilho/paygate-monetize-monetization-x40290

Monetize any MCP server: x402 paywall, pay-per-call billing in USDC on Base, agent marketplace.

io.github.A1-x-Tech/mcp-shopify-admin89

MCP server for the Shopify Admin API: products, orders, customers, inventory, discounts.

Sfcc Dev MCP Server88

MCP server for Salesforce B2C Commerce Cloud development assistance

27 9

MCP Security Weekly

Get CVE alerts and security updates for io.github.ihint/merchant-context and similar servers.

Community

Discussion

Start a conversation

Ask a question, share a tip, or report an issue.

Has anyone used this with Cursor?How do you handle auth?Any alternatives?

Edit this pageView history

E-Commerce

Step 1

Install in your client

Config is the same across clients — only the file and path differ.

Supported in Claude Desktophttp · Node 18+

Paste into ~/Library/Application Support/Claude/claude_desktop_config.json

{
  "mcpServers": {
    "io-github-ihint-merchant-context": {
      "args": [
        "-y",
        "wrangler"
      ],
      "command": "npx"
    }
  }
}

Are you the author?

Add this badge to your README to show your security score and help users find safe servers.

Embed in your READMEAbout badges →

[![MCPpedia Score](https://mcppedia.org/api/badge/io-github-ihint-merchant-context)](https://mcppedia.org/s/io-github-ihint-merchant-context)

Read me

What io.github.ihint/merchant-context does

Merchant Context is an open merchant preflight for agent builders.

Test This Server

Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.

npx -y 'wrangler' 2>&1 | head -1 && echo "✓ Server started successfully"

After testing, let us know if it worked:

README

Merchant Context

Merchant Context is an open merchant preflight for agent builders.

It starts with a practical question:

Can an agent tell what you sell, who it is for, what it costs, which rules apply, and what action comes next without guessing?

This repo contains:

Canonical sources

Product and machine brief: https://merchant.atomandbits.com/llms.txt
Version 0.1 schema: https://merchant.atomandbits.com/schema/merchant-context-v0.1.json
UCP discovery: https://merchant.atomandbits.com/.well-known/ucp
Open source and history: https://github.com/ihint/merchant-context

The domain schema and schema/merchant-context.schema.json must stay semantically equal. Versioned releases preserve old contracts.

Status

This is an early public draft from Atom & Bits. It is not a new payment or checkout protocol. It does not certify ACP, UCP, MCP, A2A, x402, or Web Bot Auth support.

The UCP profile declares no services, checkout capabilities, or payment handlers. It gives agents an explicit discovery response without claiming operations that do not exist.

The goal is to give merchants one testable context layer that can map to those systems as they mature.

No outside adoption is claimed from internal tests, registry views, repository activity, or self-funded payments.

Agent endpoints

MCP: https://api.merchant.atomandbits.com/mcp
Free MCP tool: resolve_merchant
Free HTTP: POST https://api.merchant.atomandbits.com/v1/resolve
Paid MCP tool: refresh_merchant
Paid HTTP x402: POST https://api.merchant.atomandbits.com/v1/refresh
Price: $0.01 USDC on Base
First verified settlement: Base transaction 0x2f0f…57af

The first paid call settled on 2026-08-04 and returned a live inspection of https://merchant.atomandbits.com.

Quick start

Work through CHECKLIST.md.
Copy examples/saas.json.
Replace every sample value with a fact from your own site or system.
Keep prices, stock, policies, and action URLs current.
Run python3 scripts/validate.py before publishing.

Add it to an agent

The remote MCP endpoint works with clients that support Streamable HTTP:

https://api.merchant.atomandbits.com/mcp

Start with resolve_merchant.

It is free.

A cache hit makes no merchant fetch and no paid inspection call.

See the agent integration guide for Codex, Claude Code, Gemini CLI, Cursor, and the OpenAI Responses API.

Agents that support the open Agent Skills format can use skills/merchant-context.

Design rules

Facts beat slogans.
A URL is not an API.
Agents must not infer price, stock, policy, or authority.
Each claim should name its source and update time.
A purchase or other high-impact action should state when human approval is required.
Existing standards win. Map to them instead of inventing a private dialect.

Agent service

The worker directory contains the hosted MCP service under test. It exposes:

resolve_merchant, a free sourced merchant record with freshness, unknowns, safe actions, and attribution;
search_merchants, a neutral search over cached sourced records;
compare_offers, a sourced comparison that keeps unknown values;
get_safe_actions, a merchant-owned action handoff with approval and recovery rules;
preflight, the reusable resolution and action gate;
check_merchant, a free merchant-site diagnostic;
refresh_merchant, a $0.01 x402 fresh inspection that needs explicit approval;
`ins

... View full README on GitHub

Loading README…

Scored, not listed

Why this score

Five weighted categories — click any category to see the underlying evidence.

Score breakdown

64/100across 5 weighted dimensions

How we score →

0255075100

−36

Security

Maintenance

Efficiency

Documentation

Compatibility

Categoriesclick a row to see evidence

Security

OSV.dev

4 fixed

CVE-2026-0933high · fixed

Wrangler affected by OS Command Injection in `wrangler pages deploy`

Affected: >= 2.0.15Fixed in 3.114.17source →

CVE-2023-7080critical · fixedCVSS 9.3

Arbitrary remote code execution within `wrangler dev` Workers sandbox

Affected: >= 3.0.0Fixed in 3.19.0source →

CVE-2023-7079medium · fixedCVSS 6.9

Arbitrary remote file read in Wrangler dev server

Affected: >= 3.9.0Fixed in 3.19.0source →

CVE-2023-3348medium · fixedCVSS 5.7

Cloudflare Wrangler directory traversal vulnerability

Affected: >= 0Fixed in 2.20.1source →

Community

Reviews

Be the first to review

Have you used this server?

Share your experience — it helps other developers decide.

How easy was setup?Did it work reliably?How was the documentation?

Frequently Asked Questions

Is io.github.ihint/merchant-context safe to use?: io.github.ihint/merchant-context has no known CVEs as of the latest MCPpedia security scan. It does not require authentication, so any local process can connect — keep this in mind in shared environments. Licensed under MIT.
How do I install io.github.ihint/merchant-context?: io.github.ihint/merchant-context supports copy-paste install configs on its MCPpedia page for Claude Desktop, Cursor, and Claude Code. Scroll to the Quick Install section and select your client.
What AI clients work with io.github.ihint/merchant-context?: io.github.ihint/merchant-context is compatible with claude-desktop, cursor, claude-code. It uses http transport.
Is io.github.ihint/merchant-context actively maintained?: io.github.ihint/merchant-context is actively maintained — last commit was 1 day ago.