TrustRails MCP Server vs Keepa MCP
A side-by-side look at the TrustRails MCP Server and Keepa MCP MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose TrustRails MCP Server for e-commerce work as a local process; choose Keepa MCP for e-commerce as a local process. You can also run both side by side in one mcpServers block.
Which MCP server should you choose?
Choose TrustRails MCP Server when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- You have the keys it needs:
TRUSTRAILS_API_KEY. - You want tools like
search_products, get_product.
Choose Keepa MCP when
- You need dedicated capabilities in the E-Commerce domain.
- You prefer a local stdio subprocess transport.
- Its auth model fits you: API key required.
- You have the keys it needs:
KEEPA_API_KEY. - You want tools like
get_product, get_price_history, get_sales_rank_history.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 55/100 · Good | 60/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | Not declared | API key required |
| Pricing | Not declared | Not declared |
| Required env vars | TRUSTRAILS_API_KEY | KEEPA_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 2 views 0 installs 0 upvotes | 9 views 0 installs 0 upvotes |
| Tools | 2 | 6 |
| Full listing | View TrustRails MCP Server | View Keepa MCP |
Tools & capabilities
TrustRails MCP Server tools 2
search_productsHOW TO CALL THIS TOOL — read before every call: Decompose the user's request into filters first. Only what's left over goes in query. STEP 1: brand name → brand filter. STEP 2: product category → category filter. STEP 3: price → min_price/max_price. STEP 4: RAM, storage, screen size, resolution, refresh rate, wattage, Wi-Fi generation → constraints. STEP 5: what remains → query. BAD: query='Sony headphones under £200' | GOOD: brand='Sony', category='Headphones', max_price=200, no query. BAD: query='tablet' | GOOD: category='Tablets', no query. BAD: query='macbook neo' | GOOD: brand='Apple', category='Laptops', query='neo'. BAD: query='Samsung QLED TV' | GOOD: brand='Samsung', category='TVs', query='qled'. If brand+category alone cover what the user wants, omit query entirely. Only put differentiating terms in query: model lines (neo, ultra, oled), variants, model numbers (WH-1000XM5, s25 ultra). Query words must appear in the title, except words naming the category ('router' in Networking) and bare numbers or specs ('4070', '16GB'), which are ignored when finding products and only rank them. Put a model number with its prefix ('RTX 4070', not '4070') and check each title for it. Leave out use-case words like gaming, cheap or best. CROSS-CATEGORY NOTE: Gaming headsets → category='Headphones', query='gaming headset'. The Gaming category is consoles/controllers/accessories only. Always set lite=true (it still carries `attributes`). If 0 results, broaden the query or drop filters (but never present a near miss as meeting a requirement). Searches 26,000+ UK electronics products across 7 retailers with price comparison. Prices are in GBP. Every listing is new (refurbished and used are excluded). PRICE COMPARISON: for a final pick with offer_count > 1, get_product returns offers[] (sorted in-stock first, then cheapest): show the cheapest in-stock retailer, the other prices with the difference and the exact saving among in-stock offers. Before claiming a saving, read offers[].title (from get_product): they must name the same model; if they differ, don't claim one. Before recommending any pick, check its title is the product type asked for (not a cable, accessory or adapter). COMPARING SPECS: compare products from the `attributes` in the search results, not by calling get_product on each. Every spec known for a product is there as {status, value}, or {status, values} when conflicting, without sources; names and units are as in `constraints`. 'confirmed' (two or more retailers state the same value) and 'inferred' (one retailer's title states it) are both the product's spec: state the value. Only `conflicting` (retailers disagree: say so, don't pick one) or a missing name (unknown) needs a caveat. A product with no `attributes` has none of these seven specs known: say so only if the user asked about one. Call get_product only for your final 1-3 picks, and only when you need what search lacks: what only the retailer's description has (processor, GPU, ports, weight, battery), or every retailer's offer and buy link (search results carry only the best offer's purchase_url (cheapest in stock)). A pick with offer_count 1 needs no call unless the user asked for a description-only detail. Don't guess those details from titles. SPEC REQUIREMENTS: put exact requirements in `constraints`, not in query, and always set `category` (and brand if known) with `constraints`: a search of only specs is rejected. If a requirement is ambiguous (e.g. '16GB' could be RAM or storage), ask the user or search without that constraint. With constraints, every product has `constraint_status` per name: 'matched' = a retailer's title states a value that meets it. 'unverified' = not known to meet it: check `attributes[name]`, where `conflicting` means retailers disagree and missing means unknown. Never treat 'unverified' as a match or say a product meets a requirement because it was returned: tell the user it is unconfirmed. Products whose stated value fails are left out (`excluded_by_constraints`). Matched results come first, also with sort='price_asc'. With constraints, `total` counts the products that match every constraint and `unverified_total` the unverified products that passed the other filters (only some may be in `products`). If `total` is 0, say no product is known to meet every requirement and offer the unverified ones only as unconfirmed. If `candidates_truncated` is true, the first 2,000 candidates in the chosen sort order were checked and more exist: add a brand or category, or a narrower query, and search again before saying nothing matches. If the search was already narrowed, tell the user the results may be incomplete. STOCK: availability is in_stock, low_stock, out_of_stock or unknown (the retailer gave no stock signal: say so, don't assume). When availability is out_of_stock, mention it as an alternative and suggest checking back — do not silently omit it. purchase_url is a trustrails.app/go/ redirect through an affiliate link; TrustRails may earn a commission, and the price is the same. Colour variants have separate barcodes and are separate products: when price matters, search again without the colour or check other colours of the same model.get_productGet full details for a single product by ID. Returns `attributes`: structured specs read from retailer titles, each name mapping to {status, value, sources}; a conflicting one has values: [{value, sources}] instead of value and sources. Names and units as in the search constraints argument. status: 'confirmed' = two or more retailers state the same value; 'inferred' = one retailer's title states it; 'conflicting' = retailers state different values (none is picked, tell the user they disagree; a retailer can appear under two values, so read offers[].title to see which listing states which); a missing name = unknown. Also returns specs.description, the retailer's own prose: use it only for details attributes do not cover (processor, GPU, ports, weight, battery, features); if it doesn't give a detail, tell the user it isn't listed. It can describe another configuration or a maximum ('up to 32GB'), so it never overrides or fills in an attribute: if an attribute is missing or conflicting, that spec is unknown or unconfirmed, and you may mention what the description says only as 'the retailer's description mentions X, unconfirmed'. It also returns pricing, availability, delivery time, and all retailer offers with per-retailer pricing (offers[].stock is a unit count only when the retailer supplies one, otherwise null). Accepts both canonical product IDs and original retailer offer IDs. Use this after search_products only for your final 1-3 picks, and only when you need what search lacks: details only the description has, or every retailer's offer and buy link. Search results already carry `attributes` to compare specs.
Keepa MCP tools 6
get_productFetch current product details from Keepa for a given Amazon ASIN. Returns: title, brand, category path, current Amazon price, new (3P) price, buy box price, review count, star rating, number of new offers, and latest sales rank. Prices are in USD. A value of "N/A" means the price type is not currently available. Args: - asin (string): Amazon ASIN, e.g. "B08N5WRWNW" - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "What is the current price of ASIN B08N5WRWNW?" -> use get_product with asin="B08N5WRWNW" - "Show me product details for B07PXGQC1Q" -> use get_product with asin="B07PXGQC1Q" Error handling: - Returns an instructional message if KEEPA_API_KEY is missing. - Returns a not-found message for invalid ASINs.get_price_historyFetch historical price data for an Amazon ASIN from Keepa. Returns a decoded, downsampled time series (at most 60 data points) for: - Amazon price (sold by Amazon directly) - New (3P) price (lowest new third-party price) - Used price (lowest used price) - Buy box price Keepa stores prices in cents. All prices returned are in USD. Keepa time values (minutes since 2011-01-01) are decoded to ISO dates. Args: - asin (string): Amazon ASIN - range (string, optional): Time range. "30d", "6m", "1y", "all". Default: "90d" - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Show price history for B08N5WRWNW over the past year" -> range="1y" - "What has the Amazon price been for B07PXGQC1Q in the last 30 days?" -> range="30d"get_sales_rank_historyFetch historical sales rank data for an Amazon ASIN from Keepa. Sales rank (BSR) is a proxy for demand: lower rank = faster sales velocity. Returns a decoded, downsampled time series plus a trend summary. The trend summary indicates whether demand is improving (rank decreasing), worsening (rank increasing), or stable. Args: - asin (string): Amazon ASIN - range (string, optional): Time range. "30d", "6m", "1y", "all". Default: "90d" - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Is demand trending up or down for B08N5WRWNW?" -> use get_sales_rank_history - "Show 6-month BSR history for B07PXGQC1Q" -> range="6m"search_productsSearch for Amazon products on Keepa by keyword. Returns a list of matching ASINs. Use get_product on any returned ASIN to fetch full product details, prices, and history. Args: - keyword (string): Search term, e.g. "wireless earbuds" - category_id (number, optional): Restrict to a Keepa category id. - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Find products for 'yoga mat'" -> keyword="yoga mat" - "Search Electronics for 'USB-C hub'" -> keyword="USB-C hub", category_id=172282get_best_sellersGet the top-selling ASINs in a Keepa category. Returns an ordered list of ASINs. Find category ids at: https://keepa.com/#!categorytree/1 Common category ids (amazon.com): - 172282: Electronics - 1055398: Computers & Accessories - 3760901: Camera & Photo - 2619533: Musical Instruments - 284507: Kitchen & Dining Args: - category_id (number): Keepa category id - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "What are the best sellers in Electronics?" -> category_id=172282 - "Top Kitchen products" -> category_id=284507get_dealsFetch current Amazon price-drop deals from Keepa. Returns products where the price has dropped significantly, filtered by minimum price drop percentage and minimum rating. Args: - min_price_drop_pct (number, optional): Minimum % price drop (1-99). Default: 20 - min_rating (number, optional): Min rating 0-50 (45 = 4.5 stars). Default: 40 - page (number, optional): Page offset for pagination. Default: 0 - domain (number, optional): Keepa domain id (default 1 = amazon.com) Examples: - "Show me deals with at least 30% off" -> min_price_drop_pct=30 - "Find highly-rated products on sale" -> min_rating=45, min_price_drop_pct=20
Ready-to-paste client configs
Paste either block (or both) into your client config, e.g. claude_desktop_config.json or ~/.cursor/mcp.json. We only show a config when the install command is confirmed.
TrustRails MCP Server
{
"mcpServers": {
"server-3": {
"command": "npx",
"args": [
"-y",
"@trustrails/mcp-server"
],
"env": {
"TRUSTRAILS_API_KEY": "YOUR_TRUSTRAILS_API_KEY_HERE"
}
}
}
}
Keepa MCP
{
"mcpServers": {
"keepa-mcp": {
"command": "npx",
"args": [
"-y",
"keepa-mcp"
],
"env": {
"KEEPA_API_KEY": "YOUR_KEEPA_API_KEY_HERE"
}
}
}
}
Frequently asked questions
TrustRails MCP Server is categorized under E-Commerce and uses a local stdio subprocess. Keepa MCP belongs to E-Commerce and uses a local stdio subprocess. Pick TrustRails MCP Server for e-commerce work and Keepa MCP for e-commerce.
Copy the mcpServers block from the config section on this page into your client's config (for example claude_desktop_config.json or ~/.cursor/mcp.json), then fully restart the client.
TrustRails MCP Server has no declared pricing — check the project's own site. Keepa MCP has no declared pricing — check the project's own site. Auth: api key required. If a server needs environment variables such as API keys, define them under the env key in your client's MCP config.
Yes. MCP clients support multiple servers: add server-3 and keepa-mcp as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, TrustRails MCP Server has a quality signal of 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars. Keepa MCP has 60/100 (Good) with 9 views, 0 installs and 0 GitHub stars.
