Open-source B2B and marketplace ecommerce; new stores include an MCP server for AI agents.
Merchant Context
Overview
Description from the maker (original English)
Resolve sourced merchant facts and safe actions before an agent acts.
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 in the cloud
- Transport: Streamable HTTP
- Category: Online shops & payments
Install
Pick the AI app you use, then copy the settings.
Before you install
- Basic checks: 1 of 1 passed
- Runs on the maker’s server: what you ask it goes through their server.
- The registry lists no key to fill in.
You need
- Runs in the cloudNothing to install; it connects over the internet
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Works in Claude on the web, desktop and mobile:
- Open Settings → Connectors
- Press Add custom connector
- Paste the address below and press Add
- If it asks you to sign in, sign in with the maker
https://api.merchant.atomandbits.com/mcpRun this in your terminal
claude mcp add --transport http merchant-context https://api.merchant.atomandbits.com/mcpOr copy the settings yourself
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"merchant-context": {
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
}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": {
"merchant-context": {
"type": "http",
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
}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.
ChatGPT connects only to servers on the internet:
- Open ChatGPT on the web → Settings → Connectors (Apps)
- Press Create or Add (some plans need Developer mode under Advanced first)
- Paste the address below, give it a name and save
- If it asks you to sign in, sign in with the maker
https://api.merchant.atomandbits.com/mcpMenu names can differ slightly by plan and over time.
Your choice stays on this device in a cookie; no account needed.
These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
What it can do
We have not read this server’s tool list yet; we check endpoints in rotation.
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 ihint, 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 checked yet
Endpoint responds
Not checked yet; we check endpoints in rotation
- … Not checked yet
Sign-in with OAuth
Not checked yet; we check endpoints in rotation
- … Not checked yet
No hidden instructions in tool descriptions
Not checked yet; we read the tool list when we check the endpoint
Compared with others in Online shops & paymentsi
- More stars than 0% of the other 1748 servers in this category
- Published to the registry more recently than 27% of the other 1748 servers in this category
- Basic checks equal to or better than 100% of the other 1748 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 Merchant Context 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?
The registry does not list a required key, though some servers ask you to sign in on first use.
Does it run on my computer or in the cloud?
It runs in the maker’s cloud. Connect over the internet with nothing to install, but what you send passes through the maker’s servers.
Is it still maintained?
The GitHub repo last changed –, and the latest version (0.3.0) reached the registry 3 months ago.
Which apps can use it?
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. It connects by URL, so apps that accept remote MCP servers work too, such as ChatGPT in developer mode.
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.
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:
- a merchant publishing checklist;
- a draft merchant-context schema;
- a worked SaaS example; and
- a map of the main commerce and discovery standards.
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.pybefore 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;inspect_merchant, a first-release compatibility alias for paid refresh;- direct HTTP routes under
/v1; and /.well-known/merchant-context, a public service record for agents and registries.
The inspector accepts public HTTPS origins only. It blocks local and IP targets, checks each redirect, caps response size and time, and returns no page body. The payment path records hashes, not wallet addresses or signed payment tokens.
Run its local checks:
cd worker
npm install npm test npm run typecheck npx wrangler deploy --dry-run
Contributing
Issues, examples, and corrections are welcome. Read CONTRIBUTING.md before opening a pull request.
License
MIT. See LICENSE.