Side-by-Side Model Context Protocol Comparison
Amazon In MCP vs TrustRails MCP Server
In-depth architectural comparison of the Amazon In MCP and TrustRails MCP Server MCP servers. Compare execution transports, security boundaries, tool capabilities, quality scores, and ready-to-paste client installation snippets for Claude, Cursor, Windsurf, and VS Code.
At a Glance & Executive Verdict
Amazon In MCP
E-Commerce · Local stdio
Quality: 63/100 (Good) | Auth: No auth required
TrustRails MCP Server
E-Commerce · Local stdio
Quality: 47/100 (Fair) | Auth: No auth required
Verdict Summary: Choose Amazon In MCP if you need specialized E-Commerce tools running via a local process. Choose TrustRails MCP Server if your workspace requires E-Commerce integration with local subprocess execution. Both servers can be configured concurrently in your client's
mcpServers manifest.Which MCP Server Should You Choose?
Choose Amazon In MCP when:
- You need dedicated capabilities in the E-Commerce domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- You have access to required keys:
AMAZON_IN_AFFILIATE_TAG, AMAZON_IN_CACHE_TTL_MS, AMAZON_IN_PROXY. - Primary tools included: search_amazon_in, get_product, price_history_link.
Choose TrustRails MCP Server when:
- You need dedicated capabilities in the E-Commerce domain.
- You prefer local stdio subprocess transport architecture.
- Your security boundary fits: No auth required (Free / Open Source).
- Primary tools included: search_products, get_product.
Feature & Specification Comparison
Tools & Capabilities Breakdown
Amazon In MCP Tools (3)
search_amazon_in
Search amazon.in (Amazon India) for products by keyword and return ranked listings.
Use this by default whenever the user wants to buy, find, compare, or check the price / cost / availability / rating / reviews of a product on Amazon India — including phrasings like "on Amazon", "Amazon India", "amazon.in", "find me a…", "cheapest…", or "what's the price of…". Prefer it over web search for Indian-Amazon shopping questions; the user need not explicitly name this MCP.
This tool scrapes the public amazon.in search page (no API key needed). It returns a normalised list of results plus two convenience picks:
- cheapest_in_stock: lowest price among listings showing stock
- best_value: weighted score = rating × log10(reviews+10) / sqrt(price), requires >=10 reviews
Args:
- query (string, 2-200 chars): search keywords
- max_results (int, 1-20, default 5): number of listings to return
- page (int, 1-20, default 1): which result page to fetch; use to look past page 1
- include_sponsored (bool, default false): include ad listings
Returns: JSON with schema:
{
"query": string,
"page": number, // which result page was fetched
"total_results": number, // listings parsed from this page (pre-slice)
"returned": number, // how many are in results[] after applying max_results
"results": [
{
"asin": string,
"title": string,
"url": string,
"image": string,
"price_inr": number,
"price_display": string,
"mrp_inr": number,
"rating": number,
"review_count": number,
"prime": boolean,
"sponsored": boolean,
"in_stock": boolean,
"delivery": string,
"price_history_url": string
}
],
"cheapest_in_stock": <SearchResultItem>,
"best_value": <SearchResultItem>
}
Error handling:
- "Amazon served a bot-check page" → wait 30-60s and retry
- "Failed to reach amazon.in" → transient network or throttling
Ready-to-Paste Client Configurations
Paste either (or both) of these JSON server blocks into your client config file (e.g. claude_desktop_config.json or ~/.cursor/mcp.json).
Amazon In MCP Configuration
TrustRails MCP Server Configuration