MCP.Market

Merchant Context MCP server

online · 100% uptime
by ihint·io.github.ihint/merchant-context·v0.3.0
No reviews yet

Resolve sourced merchant facts and safe actions before an agent acts.

B77/100grade B
Write a reviewRun it
What users say
No reviews yet
Be the first
Safety scan
B77/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Merchant Context yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Merchant Context tools (9, 2 write)

write = sends, deletes, buys or posts
  • check_merchantwrite actionFree

    Run a free merchant-site diagnostic. Agents should use resolve_merchant before relying on merchant facts or actions.

  • compare_offersFree

    Compare only sourced offer fields from two or more merchants. Unknown values stay unknown and payment never changes order.

  • get_safe_actionsFree

    Return current merchant-owned action URLs, exact inputs, authority, confirmation, expiry, retry rules, recovery, and attribution.

  • get_service_infoFree

    Describe the Merchant Context service, price, and inspection checks.

  • inspect_merchantFree

    Compatibility alias for refresh_merchant. Show the price and get explicit human approval first.

  • preflightFree

    Resolve one merchant, evaluate sourced intent constraints, select a safe action, state approval, and return attribution.

  • refresh_merchantwrite actionFree

    Pay for a fresh merchant inspection and cache refresh. Show the price and get explicit human approval first.

  • resolve_merchantFree

    Resolve cached merchant identity, sourced facts, offers, terms, freshness, and safe actions for free. Call this before relying on merchant facts or starting an action.

  • search_merchantsFree

    Search cached merchant records by sourced offer, place, price, timing, policy, action support, and freshness. Payment and adoption never change order.

Public scan report

scanner v0.1.10 · 2026-11-04 · same rubric, same numbers if you re-run it

1 high
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 3409ms17/20
  • Tool poisoning9 tool descriptions checked15/15
  • Auth qualityopen endpoint exposes 2 write-action tools with no auth3/15
  • Maintenancelast push 4 days ago15/15
  • Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10

Findings (1)

  • highWrite-action tools reachable without authenticationauth.open-write
Overall 77/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Merchant Context compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
77/100
higher than 50% of 4,460 AI and agents servers
Tools
9
the typical AI and agents server has 6
Tools that change things
22%
typical: 0%. Fewer write tools means less an agent can break
Uptime
100%
of our recent checks; the typical remote AI and agents server answers 100%
Response time
1,077 ms
faster than 8% of 2,331 AI and agents servers

What its tools let an agent do: 7 read · 2 change

Install Merchant Context in Claude Code, Cursor or VS Code

claude mcp add --transport http merchant-context https://api.merchant.atomandbits.com/mcp
Add to Cursor

What the publisher says

From the Merchant Context repository's README, as published. We do not edit it. Read it on GitHub

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

  1. Work through CHECKLIST.md.
  2. Copy examples/saas.json.
  3. Replace every sample value with a fact from your own site or system.
  4. Keep prices, stock, policies, and action URLs current.
  5. 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:

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Merchant Context: common questions

Is Merchant Context MCP server safe?
Mostly: it is graded B (77/100). Read the Merchant Context safety report
How do I install Merchant Context?
It runs remotely at api.merchant.atomandbits.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Merchant Context need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Merchant Context maintained?
The last commit was 5 days ago (2026-10-30). The latest release is v0.3.0.
Is Merchant Context up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Merchant Context?
Servers from other publishers that do the same job: Decionis MCP server, Agent-Native Chat MCP server and Emilia Protocol MCP server.
How does Merchant Context compare with other AI and agents MCP servers?
safety score 77/100 (higher than 50% of 4,460 AI and agents servers); tools 9 (the typical AI and agents server has 6); tools that change things 22% (typical: 0%. Fewer write tools means less an agent can break). Full comparison.

Alternatives to Merchant Context

Same job from other publishers: the closest match first, then the best rated.

  • Decionis
    Authorize consequential AI agent actions before execution
    A
  • Agent-Native Chat
    Minimal chat-first app with durable threads, actions, and the app-agent loop
    A
  • Emilia Protocol
    Exact-action approval for consequential agent actions: request, track, and verify signed receipts.
    B
  • three.ws Provenance
    Append-only, signed, on-chain-verifiable agent action log — record and audit what agents did.
    More from nirholas →
    B