Merchant Context
REMOTE · API.MERCHANT.ATOMANDBITS.COM · SCANNED SEP 27
Resolve sourced merchant facts and safe actions before an agent acts.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security46
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- Authorisation not fully verified: no authorisation is required to call this server, and 1 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. See how to fix → View diagnostics → Unverified
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 406, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability73
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 647 tokens (~71/item across 9 items; 9 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage76
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 27% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Merchant Context MCP server?
Merchant Context is a hosted endpoint at https://api.merchant.atomandbits.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · api.merchant.atomandbits.com
claude mcp add --transport http ihint-merchant-context 'https://api.merchant.atomandbits.com/mcp'
{
"mcpServers": {
"ihint-merchant-context": {
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
} {
"servers": {
"ihint-merchant-context": {
"type": "http",
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
} [mcp_servers.ihint-merchant-context] url = "https://api.merchant.atomandbits.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"ihint-merchant-context": {
"type": "remote",
"url": "https://api.merchant.atomandbits.com/mcp",
"enabled": true
}
}
} openclaw mcp add ihint-merchant-context --url 'https://api.merchant.atomandbits.com/mcp' --transport streamable-http
mcp_servers:
ihint-merchant-context:
url: "https://api.merchant.atomandbits.com/mcp" {
"McpServers": {
"ihint-merchant-context": {
"Transport": "http",
"Url": "https://api.merchant.atomandbits.com/mcp"
}
}
} assistant mcp add ihint-merchant-context -t streamable-http -u 'https://api.merchant.atomandbits.com/mcp'
{
"mcpServers": {
"ihint-merchant-context": {
"type": "http",
"url": "https://api.merchant.atomandbits.com/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 10 Sept 26 +3
- Stability: fail → pass ▲ security
- 2 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80.
- 31 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73.
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- Stability: 0.20 → fail ▼ security
- Tool “check_merchant” rewrote its description, which is the text the model reads security
- Tool “inspect_merchant” rewrote its description, which is the text the model reads security
- Tool coverage: 100% → 27% ▼ functional
- Schema quality: 41 → 71 ▼ functional
- “inspect_merchant” added a required parameter “approved”, so existing callers break ▼ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- Server version: 0.2.0 → 0.3.0 functional
- New tool “compare_offers” functional
- New tool “get_safe_actions” functional
- New tool “preflight” functional
- New tool “refresh_merchant” functional
- New tool “resolve_merchant” functional
- New tool “search_merchants” functional
- “inspect_merchant” reworded the description of “merchant_url” cosmetic
- 5 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 4 Aug 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 27 Sept 2026 · Probed https://api.merchant.atomandbits.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=atomandbits.com | CN=WE1,O=Google Trust Services,C=US | 4 Aug 2026 | 2 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 94d7980be672236c13654e1bbbd93231 |
| SANs: atomandbits.com, api.merchant.atomandbits.com, *.api.merchant.atomandbits.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of api.merchant.atomandbits.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| atomandbits.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://api.merchant.atomandbits.com/mcp | Verified | 200 | |
| http (plaintext) | http://api.merchant.atomandbits.com/mcp | Inconclusive | 406 |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_merchant ~44
Run a free merchant-site diagnostic. Agents should use resolve_merchant before relying on merchant facts or actions.
| Name | Type | Req | Description |
|---|---|---|---|
| merchant_url | string | yes | Public HTTPS merchant URL to check |
No output schema declared.
No examples provided.
compare_offers ~46
Compare only sourced offer fields from two or more merchants. Unknown values stay unknown and payment never changes order.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | – |
| merchant_urls | array | yes | – |
No output schema declared.
No examples provided.
get_safe_actions ~75
Return current merchant-owned action URLs, exact inputs, authority, confirmation, expiry, retry rules, recovery, and attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | – | – |
| allowed_authority | array | – | – |
| client_id | string | – | – |
| human_confirmation_available | boolean | – | – |
| merchant_url | string | yes | – |
No output schema declared.
No examples provided.
get_service_info ~21
Describe the Merchant Context service, price, and inspection checks.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
inspect_merchant ~69
Compatibility alias for refresh_merchant. Show the price and get explicit human approval first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Stable, non-secret identifier for the calling agent |
| approved | boolean | yes | Explicit human approval for this priced refresh |
| merchant_url | string | yes | Public HTTPS merchant URL |
No output schema declared.
No examples provided.
preflight ~122
Resolve one merchant, evaluate sourced intent constraints, select a safe action, state approval, and return attribution.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | – | – |
| allowed_authority | array | – | – |
| client_id | string | – | – |
| geography | string | – | – |
| human_confirmation_available | boolean | – | – |
| item_or_service | string | – | – |
| max_stale_seconds | integer | – | – |
| maximum_price_amount | number | – | – |
| maximum_price_currency | string | – | – |
| merchant_url | string | yes | – |
| timing | string | – | – |
No output schema declared.
No examples provided.
refresh_merchant ~72
Pay for a fresh merchant inspection and cache refresh. Show the price and get explicit human approval first.
| Name | Type | Req | Description |
|---|---|---|---|
| agent_id | string | yes | Stable, non-secret identifier for the calling agent |
| approved | boolean | yes | Explicit human approval for this priced refresh |
| merchant_url | string | yes | Public HTTPS merchant URL |
No output schema declared.
No examples provided.
resolve_merchant ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| client_id | string | – | Stable, non-secret identifier for the calling client |
| merchant_url | string | yes | Public HTTPS merchant URL |
No output schema declared.
No examples provided.
search_merchants ~128
Search cached merchant records by sourced offer, place, price, timing, policy, action support, and freshness. Payment and adoption never change order.
| Name | Type | Req | Description |
|---|---|---|---|
| action_type | string | – | – |
| client_id | string | – | Stable, non-secret identifier for the calling client |
| freshness | string | – | – |
| geography | string | – | – |
| item_or_service | string | – | – |
| max_stale_seconds | integer | – | – |
| maximum_price_amount | number | – | – |
| maximum_price_currency | string | – | – |
| policy | string | – | – |
| timing | string | – | – |
No output schema declared.
No examples provided.
What is the Merchant Context MCP server?
Merchant Context is an MCP server listed in the public MCP registry as io.github.ihint/merchant-context. Resolve sourced merchant facts and safe actions before an agent acts. This page covers its hosted endpoint (https://api.merchant.atomandbits.com/mcp).
Is the Merchant Context MCP server safe to use?
Merchant Context scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Merchant Context MCP server expose?
Merchant Context exposes 9 tools: get_service_info, check_merchant, resolve_merchant, search_merchants, compare_offers, and 4 more. Their descriptions and schemas cost roughly 647 tokens of context every time the server is loaded.
Does the Merchant Context MCP server require authentication?
No. We connected to Merchant Context without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Merchant Context MCP server still maintained?
Merchant Context is still listed as active in the MCP registry. We last reached this channel on 27 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.