Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

BayDeep — E-commerce MCP Gateway

REMOTE · MCP.BAYDEEP.COM

E-commerce MCP gateway: live product deals, attributed buy links, order tracking, flights.

Available components

+3 this week 66 Trust /100

Last scanned (18 hours ago)

Scores higher than 51% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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 Security57
Transport & Reachability100
Schema Quality & AI Usability65
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1519 tokens (~138/item across 11 items; 11 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage78
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 35% 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
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 12 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
What we tested

Checks we ran (12)

  • TLS certificate
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Authorization in Endpoint SecurityAuthorisation not fully verified: no authorisation is required to call this server, and 11 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

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.

  • 21 Nov 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.

  • 18 Nov 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.

  • 16 Nov 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.

  • 14 Nov 26 +1

    No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

  • 12 Nov 26 +1
    • “affiliate_orders” reworded the description of “end_time” cosmetic
    • “affiliate_orders” reworded the description of “start_time” cosmetic
    • “affiliate_orders” made “end_time” optional cosmetic
    • “affiliate_orders” made “start_time” optional cosmetic

    4 cosmetic changes on this day. Switch on “Show cosmetic changes” to see them.

  • 11 Nov 26 +1
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “affiliate_orders” rewrote its description, which is the text the model reads security
    • Tool “convert_link” rewrote its description, which is the text the model reads security
    • Tool “mint_free_key” rewrote its description, which is the text the model reads security
    • Stability: unverified → 0.03 ▲ functional
  • 10 Nov 26 60

    First indexed and scored.

Diagnostics

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 21 Nov 2026 · Probed https://mcp.baydeep.com/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mcp.baydeep.com CN=YE2,O=Let's Encrypt,C=US 9 Nov 2026 7 Feb 2027 ECDSA 256 ECDSA-SHA384 64f12cab070ada69c949d3cb7c4d34d183e
SANs: api.baydeep.com, mcp.baydeep.com
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of mcp.baydeep.com. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
com. DS published 19718 13 Verified
baydeep.com. No DS 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://mcp.baydeep.com/mcp Verified 200
http (plaintext) http://mcp.baydeep.com/mcp HTTPS enforced 301 https://mcp.baydeep.com/mcp
MCP tools · 11 exposed · ~1,124 tokens

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 →

Tool Tokens
affiliate_orders ~139

YOUR attributed affiliate orders in a time range (source for your commission settlement & refund tracking). Orders are filtered to your key's tracking_id; each order carries share_eligible + share_amount and the page ends with share_summary — each order carries share_eligible and share_amount fields. Requires a free API key.

NameTypeReqDescription
end_timestring–DEFAULT: now
pagenumber––
page_sizenumber––
start_timestring–ISO 8601 or yyyy-MM-dd HH:mm:ss (UTC assumed). DEFAULT: 90 days ago
statusstring–PENDING | PAID | CLOSED ...

No output schema declared.

No examples provided.

catalog_overview ~74

WHAT BAYDEEP SELLS: product types currently in the catalog (physical goods from AliExpress, flight fares via Travelpayouts/Aviasales), item counts, top categories, and HOW to search/book each type. Call this FIRST when unsure what the catalog contains. Works WITHOUT any API key. Read-only.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

categories ~27

AliExpress affiliate category tree (for building category filters or browse UX). Requires a free API key.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

convert_link ~94

Convert any aliexpress.com product/shop/search URL(s) into YOUR affiliate-attributed link(s) (max 10 per call). ALWAYS run items through this before presenting a buy link — attribution is how agent-driven purchases are tracked. Requires a free API key.

NameTypeReqDescription
link_typenumber–2=short link (default), 0=original
urlsstringyescomma separated URLs, max 10

No output schema declared.

No examples provided.

flight_search ~149

Search FLIGHT FARES in the catalog (Aviasales/Travelpayouts partners, fares refreshed daily). Filter by origin/destination IATA code (e.g. PEK, JFK, SIN) and optional departure date (YYYY-MM-DD). Items sorted by price; book_url is ALREADY affiliate-attributed — link the user straight to it (no convert_link needed). Works WITHOUT any API key. Read-only.

NameTypeReqDescription
datestring–departure date YYYY-MM-DD (optional)
destinationstring–destination IATA code, e.g. SIN
originstring–origin IATA code, e.g. PEK
page_sizenumber––

No output schema declared.

No examples provided.

hot_products ~91

LIVE AliExpress hot-selling products (no keyword; optional category). Good for "what's trending" / deal feeds. Consumes platform quota. Read-only. Requires a free API key.

NameTypeReqDescription
category_idstring––
currencystring––
languagestring––
pagenumber––
page_sizenumber––
ship_tostring––

No output schema declared.

No examples provided.

mint_free_key ~151

SELF-SERVE a free API key — NO signup, NEVER expires, unlocks ALL tools (live AliExpress search, hot products, attributed convert links, your orders). Call this FIRST if any other tool says a key is required. Store the returned key and send it as X-API-Key header (or Authorization: Bearer) on subsequent calls. Rate limit: 30 req/min. Attribution is bound to this key. Optional client_ref ([A-Za-z0-9-], <=40) = your own end-user id, echoed back on your orders.

NameTypeReqDescription
client_refstring–optional: your stable anonymized end-user id ([A-Za-z0-9-], <=40)

No output schema declared.

No examples provided.

product_detail ~49

Full detail for up to 10 AliExpress product ids (comma separated or array). Read-only. Requires a free API key.

NameTypeReqDescription
product_idsstringyescomma separated ids, max 10

No output schema declared.

No examples provided.

search_products ~169

LIVE AliExpress affiliate product search (100M+ item pool, ships to 200+ countries; prices in the target currency). Consumes platform quota — do not poll; prefer shelf_search for repeated lookups. Returns items with price, coupon, sales, rating, commission_rate and detail_url. Read-only. Requires a free API key.

NameTypeReqDescription
category_idstring––
currencystring––
languagestring––
pagenumber––
page_sizenumber––
qstringyes–
ship_tostring–ISO country code, default US
sortstring–SALE_PRICE_ASC | SALE_PRICE_DESC | AVERAGE_RATE_ASC | AVERAGE_RATE_DESC | ORDINAL_ASC | ORDINAL_DESC

No output schema declared.

No examples provided.

shelf_item ~45

Get one LOCAL shelf item by goods_id (full normalized fields; works for goods and flight fares). Works WITHOUT any API key. Read-only.

NameTypeReqDescription
goods_idstringyes–

No output schema declared.

No examples provided.

shelf_search ~136

Search the LOCAL shelf — physical goods (AliExpress) AND flight fares (Travelpayouts). No platform quota consumed — works WITHOUT any API key (30 req/min per IP). sort=relevance(default when q given)|price|sales|latest; price_min/price_max filter. Goods items carry detail_url (attribute via convert_link with a free key); flight items carry book_url directly. Read-only.

NameTypeReqDescription
pagenumber––
page_sizenumber––
price_maxnumber––
price_minnumber––
qstring––
sortstring––

No output schema declared.

No examples provided.

Install

How do I install the BayDeep — E-commerce MCP Gateway server?

BayDeep — E-commerce MCP Gateway is a hosted endpoint at https://mcp.baydeep.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 · mcp.baydeep.com

# add to Claude Code
claude mcp add --transport http meshtok-baydeep 'https://mcp.baydeep.com/mcp'
Common questions

What is the BayDeep — E-commerce MCP Gateway server?

BayDeep — E-commerce MCP Gateway is listed in the public MCP registry as io.github.MeshTok/baydeep. E-commerce MCP gateway: live product deals, attributed buy links, order tracking, flights. This page covers its hosted endpoint (https://mcp.baydeep.com/mcp).

Is the BayDeep — E-commerce MCP Gateway server safe to use?

BayDeep — E-commerce MCP Gateway scores 66 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 BayDeep — E-commerce MCP Gateway server expose?

BayDeep — E-commerce MCP Gateway exposes 11 tools: mint_free_key, search_products, hot_products, product_detail, convert_link, and 6 more. Their descriptions and schemas cost roughly 1,124 tokens of context every time the server is loaded.

Does the BayDeep — E-commerce MCP Gateway server require authentication?

No. We connected to BayDeep — E-commerce MCP Gateway without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the BayDeep — E-commerce MCP Gateway server still maintained?

BayDeep — E-commerce MCP Gateway is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What did VerifyMCP test on the BayDeep — E-commerce MCP Gateway server?

VerifyMCP ran 12 checks on BayDeep — E-commerce MCP Gateway, covering TLS certificate, HTTPS, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about BayDeep — E-commerce MCP Gateway: Authorization. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.