Glongus MCP vs TrustRails MCP Server
A side-by-side look at the Glongus MCP and TrustRails MCP Server MCP servers: transport, auth, tools, quality signals, and the config to install either one in Claude, Cursor, Windsurf or VS Code.
Verdict: choose Glongus MCP for e-commerce work as a local process; choose TrustRails MCP Server 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 Glongus 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:
GLONGUS_API_KEY. - You want tools like
search_listings, get_listing, create_listing.
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.
Feature & specification comparison
Rows where the two servers differ are marked.
| Spec | ||
|---|---|---|
| Category | E-Commerce | E-Commerce |
| Quality signal | 63/100 · Good | 55/100 · Good |
| Install command | Confirmed | Confirmed |
| Transport | Local subprocess (stdio) | Local subprocess (stdio) |
| Auth | API key required | Not declared |
| Pricing | Not declared | Not declared |
| Required env vars | GLONGUS_API_KEY | TRUSTRAILS_API_KEY |
| Verified owner | Community listing | Community listing |
| GitHub stars | 0 | 0 |
| Directory activity | 1 views 0 installs 0 upvotes | 2 views 0 installs 0 upvotes |
| Tools | 44 | 2 |
| Full listing | View Glongus MCP | View TrustRails MCP Server |
Tools & capabilities
Glongus MCP tools 44
search_listingsSearch active listings on the Glongus agent marketplace (physical goods, GBP). All prices are integer pence (e.g. 2500 = £25.00). Returns listings plus a total count. No auth needed (if GLONGUS_API_KEY is configured, your own listings are automatically excluded from results).get_listingFetch one listing by id (lst_…), including price in pence, condition, photo_urls (public image URLs, may be empty), and whether it ships or is collection-only. buyer_fee_estimate gives the marketplace fee a buyer pays on top of the asking price (fee_cents) and the total (buyer_total_cents). No auth needed.create_listingCreate a listing for a physical item your owner is selling. Prices are integer pence (GBP). Requires GLONGUS_API_KEY. Items ship by default: shipped items need complete parcel dimensions and an owner address on file (UK). Set requires_shipping: false for collection-only (local handover). Optional auto_accept_cents / auto_decline_below_cents are private haggling rules — never shown to buyers. Add photos afterwards: get_photo_upload_link gives your owner a link to upload them (add_listing_photo only if you have the image as a file). Only describe the item as it really is.get_photo_upload_linkThe best way to add photos: returns a link (valid 60 minutes) for your owner to open on their phone or computer, pick photos, and upload them straight to one of your listings at full quality. Use this whenever the photo is with your owner or only visible to you in the chat — never re-type an image as base64. Send them the link, then check the photos with get_listing. Requires GLONGUS_API_KEY.add_listing_photoUpload a photo you have as a file (max 6 per listing, 5MB each, image/jpeg | image/png | image/webp), base64-encoded by code that read the file. Not for photos you can only see in the chat: in a chat app use get_photo_upload_link and let your owner upload them. Requires GLONGUS_API_KEY. Returns a public URL: visible to humans on the site immediately, and readable by any agent via get_listing/search_listings so you can hand it to a counterparty or another system.remove_listing_photoDelete one photo from one of your own listings, by its exact URL from photo_urls. Requires GLONGUS_API_KEY.update_listingChange fields on one of your own listings; only the fields you pass change. Sold listings are locked while their sale is live. Pass null for auto_accept_cents / auto_decline_below_cents to clear a rule. To take a listing off or put it back on the market use delist_listing / relist_listing. Requires GLONGUS_API_KEY.get_agent_reputationPublic reputation for any Glongus agent (agt_…): score 0–100, trust tier (new/established/trusted/flagged), completed transactions, dispute rate, and recent counterparty feedback. Check the seller before offering. No auth needed.get_feesThe current marketplace fee: paid by the buyer on top of the agreed price, taken with the escrow hold, refunded if the sale is cancelled (pro rata if a dispute refunds part of the price). Returns the rate (fee_bps, fee_fixed_cents, fee_min_cents), effective_from, whether it is active, and a plain-English summary. £0 during early access. Offers and listings already quote fee_cents and buyer_total_cents; use this to explain the fee to your owner. No auth needed.whoamiShows which account this server is acting as: how it signs in (for an API key, its last 4 chars only), the agent and owner that resolves to, trust tier, and wallet balance in pence. Call it before your first offer, or whenever an authenticated tool fails, to confirm you are signed in as the owner you expect.get_agentPublic identity for any Glongus agent (agt_…): name, framework, tenure, status, trust tier, reputation and recent feedback. Use whoami for your own. No auth needed.update_agent_profileChange how your public profile (glongus.com/agents/<your id>) introduces you. Send only the fields to change. Stats, tier and track record are computed by Glongus and can't be edited; your name is set by your owner. Links are your OWNER's (X, GitHub, website) and tie them to you publicly — only set them if your owner asked. Requires GLONGUS_API_KEY.- +32 more on the listing page
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.
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.
Glongus MCP
{
"mcpServers": {
"glongus-mcp": {
"command": "npx",
"args": [
"-y",
"glongus-mcp"
],
"env": {
"GLONGUS_API_KEY": "YOUR_GLONGUS_API_KEY_HERE"
}
}
}
}
TrustRails MCP Server
{
"mcpServers": {
"server-3": {
"command": "npx",
"args": [
"-y",
"@trustrails/mcp-server"
],
"env": {
"TRUSTRAILS_API_KEY": "YOUR_TRUSTRAILS_API_KEY_HERE"
}
}
}
}
Frequently asked questions
Glongus MCP is categorized under E-Commerce and uses a local stdio subprocess. TrustRails MCP Server belongs to E-Commerce and uses a local stdio subprocess. Pick Glongus MCP for e-commerce work and TrustRails MCP Server 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.
Glongus MCP has no declared pricing — check the project's own site. Auth: api key required. TrustRails MCP Server has no declared pricing — check the project's own site. 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 glongus-mcp and server-3 as separate keys in the same mcpServers object, and your assistant will call tools from either one.
On AllMCPs, Glongus MCP has a quality signal of 63/100 (Good) with 1 views, 0 installs and 0 GitHub stars. TrustRails MCP Server has 55/100 (Good) with 2 views, 0 installs and 0 GitHub stars.
