io.github.sangha-lightanchor/shop-search
REMOTE · AMAZON.LIGHTANCHOR.AI · SCANNED SEP 20
Product search for AI agents: Amazon + Shopify, cart-to-checkout buy path. Pay-per-call, no API key.
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 Security63
- 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 2 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 is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 Usability81
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 176 tokens (~88/item across 2 items; 2 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management70
- Stability observed for 21 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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 io.github.sangha-lightanchor/shop-search MCP server?
io.github.sangha-lightanchor/shop-search is a hosted endpoint at https://amazon.lightanchor.ai/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 · amazon.lightanchor.ai
claude mcp add --transport http sangha-lightanchor-shop-search 'https://amazon.lightanchor.ai/mcp'
{
"mcpServers": {
"sangha-lightanchor-shop-search": {
"url": "https://amazon.lightanchor.ai/mcp"
}
}
} {
"servers": {
"sangha-lightanchor-shop-search": {
"type": "http",
"url": "https://amazon.lightanchor.ai/mcp"
}
}
} [mcp_servers.sangha-lightanchor-shop-search] url = "https://amazon.lightanchor.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"sangha-lightanchor-shop-search": {
"type": "remote",
"url": "https://amazon.lightanchor.ai/mcp",
"enabled": true
}
}
} openclaw mcp add sangha-lightanchor-shop-search --url 'https://amazon.lightanchor.ai/mcp' --transport streamable-http
mcp_servers:
sangha-lightanchor-shop-search:
url: "https://amazon.lightanchor.ai/mcp" {
"McpServers": {
"sangha-lightanchor-shop-search": {
"Transport": "http",
"Url": "https://amazon.lightanchor.ai/mcp"
}
}
} assistant mcp add sangha-lightanchor-shop-search -t streamable-http -u 'https://amazon.lightanchor.ai/mcp'
{
"mcpServers": {
"sangha-lightanchor-shop-search": {
"type": "http",
"url": "https://amazon.lightanchor.ai/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.
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.
- 18 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 14 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
- 12 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.
- 5 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
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 20 Sept 2026 · Probed https://amazon.lightanchor.ai/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.lightanchor.ai | CN=YR1,O=Let's Encrypt,C=US | 18 Aug 2026 | 16 Nov 2026 | RSA 2048 | SHA256-RSA | 67676c5d315adf44cc761a67eefd46f8bbf |
| SANs: *.lightanchor.ai, lightanchor.ai | ||||||
| CN=YR1,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | a20253f15f2691c05dc1ce13b9bcca4e |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of amazon.lightanchor.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| lightanchor.ai. | 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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://amazon.lightanchor.ai/mcp | Verified | 200 | |
| http (plaintext) | http://amazon.lightanchor.ai/mcp | HTTPS enforced | 308 | https://amazon.lightanchor.ai/mcp |
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 →
get_paid_endpoints ~59
FREE: how to use the full paid API (product search across Amazon+Shopify, cart-to-checkout execution, ASIN snapshots, listing audits, review insights, merchant trust checks). Pay-per-call via MPP, no API key.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
shop_search_preview ~69
FREE preview of Shop Search: top Amazon result for a product query (full version returns 20+ results incl. live Shopify stores with cart-to-checkout routes). Use for quick product lookups.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Product query, e.g. "korean sunscreen spf50" |
No output schema declared.
No examples provided.
What is the io.github.sangha-lightanchor/shop-search MCP server?
io.github.sangha-lightanchor/shop-search is an MCP server listed in the public MCP registry as io.github.sangha-lightanchor/shop-search. Product search for AI agents: Amazon + Shopify, cart-to-checkout buy path. Pay-per-call, no API key. This page covers its hosted endpoint (https://amazon.lightanchor.ai/mcp).
Is the io.github.sangha-lightanchor/shop-search MCP server safe to use?
io.github.sangha-lightanchor/shop-search scores 78 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 io.github.sangha-lightanchor/shop-search MCP server expose?
io.github.sangha-lightanchor/shop-search exposes 2 tools: shop_search_preview, get_paid_endpoints. Their descriptions and schemas cost roughly 128 tokens of context every time the server is loaded.
Does the io.github.sangha-lightanchor/shop-search MCP server require authentication?
No. We connected to io.github.sangha-lightanchor/shop-search without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.sangha-lightanchor/shop-search MCP server still maintained?
io.github.sangha-lightanchor/shop-search is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.