Merchant Context MCP server
io.github.ihint/merchant-contextihintstreamable-httpv0.3.0Scanned
Resolve sourced merchant facts and safe actions before an agent acts.
9 tools: 1 do something that can't be undone, 2 change things and 6 only read.
- Reads private data · 0
- Reads text others write · 8
- Can send data out · 0
- 2 findings
Tools listed without sign-in. Remote posture
With Anlyon
1 tool here does something that can't be undone. Govern it.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Merchant Context MCP server can do
The Merchant Context MCP server is published by the GitHub account ihint. It has 9 tools. It can do things that cannot be undone, such as sending, paying or publishing (refresh_merchant) and create or change data (2 tools: check_merchant and inspect_merchant), but cannot delete data. 6 tools only read.
8 tools bring in text other people can write (check_merchant, resolve_merchant, search_merchants and 5 more).
The fixed checks matched 2 findings (annotation-conflict). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 19, 2026, version 0.3.0.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
9 tools
Can't be undone 1Claude Code: ask
refresh_merchantPay for a fresh merchant inspection and cache refresh.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "pay": a word that usually means money moves, which cannot be taken back.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Pay for a fresh merchant inspection and cache refresh. Show the price and get explicit human approval first.
Annotations the server declares
- title: Refresh merchant evidence
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Changes things 2Claude Code: ask
check_merchantRun a free merchant-site diagnostic.Reads text others write1 finding
Why it is in this group
- The description's first verb is "run": a word for a change.
- The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "check_merchant" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
Description, as the server wrote it Run a free merchant-site diagnostic. Agents should use resolve_merchant before relying on merchant facts or actions.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
inspect_merchantCompatibility alias for refresh_merchant.Reads text others write1 finding
Why it is in this group
- The name "inspect_merchant" says "inspect": a word for reading.
- The server marks it as not read-only (readOnlyHint: false).
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Warn
The server marks "inspect_merchant" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "inspect_merchant" says "inspect": a word for reading.
Description, as the server wrote it Compatibility alias for refresh_merchant. Show the price and get explicit human approval first.
Annotations the server declares
- title: Refresh merchant evidence
- readOnlyHint: false
- destructiveHint: false
- idempotentHint: false
- openWorldHint: true
Only reads 6Show 6 read-only tools
compare_offersCompare only sourced offer fields from two or more merchants.Reads text others writeNo findings
Why it is in this group
- The name "compare_offers" says "compare": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Compare only sourced offer fields from two or more merchants. Unknown values stay unknown and payment never changes order.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_safe_actionsReturn current merchant-owned action URLs, exact inputs, authority, confirmation, expiry, retry rules, recovery, and attribution.Reads text others writeNo findings
Why it is in this group
- The name "get_safe_actions" says "get": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Return current merchant-owned action URLs, exact inputs, authority, confirmation, expiry, retry rules, recovery, and attribution.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
get_service_infoDescribe the Merchant Context service, price, and inspection checks.No findings
Why it is in this group
- The name "get_service_info" says "get": a word for reading.
Description, as the server wrote it Describe the Merchant Context service, price, and inspection checks.
Annotations the server declares
- readOnlyHint: true
- openWorldHint: false
preflightResolve one merchant, evaluate sourced intent constraints, select a safe action, state approval, and return attribution.Reads text others writeNo findings
Why it is in this group
- The description's first verb is "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Resolve one merchant, evaluate sourced intent constraints, select a safe action, state approval, and return attribution.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
resolve_merchantResolve cached merchant identity, sourced facts, offers, terms, freshness, and safe actions for free.Reads text others writeNo findings
Why it is in this group
- The name "resolve_merchant" says "resolve": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it 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.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
search_merchantsSearch cached merchant records by sourced offer, place, price, timing, policy, action support, and freshness.Reads text others writeNo findings
Why it is in this group
- The name "search_merchants" says "search": a word for reading.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Description, as the server wrote it Search cached merchant records by sourced offer, place, price, timing, policy, action support, and freshness. Payment and adoption never change order.
Annotations the server declares
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: true
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.
- Reads private data0
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 19:05 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 3
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- HighThe whole server
The endpoint served tools/list without credentials, and the list has 3 tools that change things (1 irreversible, 2 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://api.merchant.atomandbits.com/mcp: tools/list returned 9 tools to an anonymous client, including refresh_merchant (irreversible), check_merchant (write), inspect_merchant (write)
Findings
Matches of fixed checks, with the text they matched.
- Warncheck_merchant
The server marks "check_merchant" read-only (readOnlyHint: true), and its own name, description or input give the class "write".
What this check looks forMatched text
annotations: {"readOnlyHint":true,"destructiveHint":false,"idempotentHint":true,"openWorldHint":true}; The description's first verb is "run": a word for a change.
- Warninspect_merchant
The server marks "inspect_merchant" as not read-only (readOnlyHint: false), and its words say it reads.
What this check looks forMatched text
annotations: {"readOnlyHint":false,"destructiveHint":false,"idempotentHint":false,"openWorldHint":true}; The name "inspect_merchant" says "inspect": a word for reading.
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
Install
Pinned to version 0.3.0. Values in angle brackets are yours to fill in.
claude mcp add --transport http merchant-context https://api.merchant.atomandbits.com/mcpclaude mcp add --transport http merchant-context https://api.merchant.atomandbits.com/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__merchant-context__get_service_info",
"mcp__merchant-context__resolve_merchant",
"mcp__merchant-context__search_merchants",
"mcp__merchant-context__compare_offers",
"mcp__merchant-context__get_safe_actions",
"mcp__merchant-context__preflight"
],
"ask": [
"mcp__merchant-context__check_merchant",
"mcp__merchant-context__refresh_merchant",
"mcp__merchant-context__inspect_merchant"
],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as merchant-context. Review it before you use it.
Capability tags behind 8 rules
- mcp__merchant-context__check_merchant untrusted-input
- mcp__merchant-context__resolve_merchant untrusted-input
- mcp__merchant-context__search_merchants untrusted-input
- mcp__merchant-context__compare_offers untrusted-input
- mcp__merchant-context__get_safe_actions untrusted-input
- mcp__merchant-context__preflight untrusted-input
- mcp__merchant-context__refresh_merchant untrusted-input
- mcp__merchant-context__inspect_merchant untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/io.github.ihint/merchant-context/verify?hash=be57afeb28f98bfef71b9b2ae8d126766ac81f3e744923e60d838555003ad706" | jq -e '.changed == false'Pinned hash be57afeb28f9, from Nov 19, 2026, 21:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/io.github.ihint/merchant-context/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/io.github.ihint/merchant-context)Source: MCP Registry · repository. Synced Oct 21, 2026, 18:36 UTC.
Merchant Context MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Merchant Context MCP server safe?
- No scan can promise that. What its definitions show: 9 tools, 3 of which can change, send or delete something, and 2 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Merchant Context MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Merchant Context MCP server do things that cannot be undone?
- Yes. 1 tool can send, pay, publish or merge: refresh_merchant.
What tools does the Merchant Context MCP server have?
- 9 tools: 1 irreversible, 2 write, 6 read. refresh_merchant, check_merchant, inspect_merchant, get_service_info, resolve_merchant, search_merchants, compare_offers, get_safe_actions and 1 more.
Does the Merchant Context MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Merchant Context MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Merchant Context MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 19, 2026.