Apostle — AI Men's Skincare Commerce
REMOTE · SEARCHSHOPAI-MCP.FLY.DEV
Search, compare, and buy Apostle men's skincare: tinted moisturizer, face wash, and sets.
Available components
Last scanned (3 hours ago)
Scores higher than 66% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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 Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability49
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1269 tokens (~97/item across 13 items; 10 tools + 3 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management71
- Stability check failed: schema churn in the 30 days we've observed: 4 tool removals, 0 breaking changes, 0 auth/transport breaks, 0 additions. See how to fix → Fail
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 11 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
- Supports UI / widget rendering.Pass
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.
- 5 Nov 26 0
- Tool “create_checkout” rewrote its description, which is the text the model reads security
- 10 Oct 26 −4
- Stability: pass → fail ▼ security
- Schema quality: fail → pass ▲ functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 0
- “create_checkout” reworded the description of “decision_id” cosmetic
1 cosmetic change on this day. Switch on “Show cosmetic changes” to see it.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
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 5 Nov 2026 · Probed https://searchshopai-mcp.fly.dev/mcp/apostleman
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=*.fly.dev | CN=YE1,O=Let's Encrypt,C=US | 20 Oct 2026 | 18 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 5e6e25e6df778e81cd07b85fc9f12d4df7d |
| SANs: *.fly.dev | ||||||
| CN=YE1,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 5ddd70dd31f801c85c186a7a04b80afe |
| 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 searchshopai-mcp.fly.dev. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| dev. | present | 60074 | 8 | Verified |
| fly.dev. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://searchshopai-mcp.fly.dev/mcp/apostleman | Verified | 200 | |
| http (plaintext) | http://searchshopai-mcp.fly.dev/mcp/apostleman | HTTPS enforced | 301 | https://searchshopai-mcp.fly.dev/mcp/apostleman |
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 →
check_compatibility ~91
Check which products are compatible with a given product. For devices, shows required consumables (e.g., conductive gel for MIRA). For topicals, shows which devices they work with. Use when a customer asks 'what gel do I need with MIRA?' or 'does this serum work with CryoSculpt?'
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product name or SKU to check compatibility for |
No output schema declared.
No examples provided.
check_inventory ~61
Check if a product is currently available. Uses Shopify Storefront API to verify real-time stock status. Use when a customer asks 'is MIRA in stock?' or before recommending a product.
| Name | Type | Req | Description |
|---|---|---|---|
| product | string | yes | Product name or SKU to check availability for |
No output schema declared.
No examples provided.
compare_products ~95
Compare two or more products side by side. Use when the user asks to compare, says 'X vs Y', or wants to decide between options. Do not use for single product lookup — use get_product instead. Returns structured comparison with shared attributes, differences, tradeoffs, and a decision hint.
| Name | Type | Req | Description |
|---|---|---|---|
| products | array | yes | Product titles or SKUs to compare (e.g. ['MIRA', 'CryoSculpt']) |
No output schema declared.
No examples provided.
create_checkout ~160
Use when the user wants to buy one or more products. This store's availability is not confirmed here, so no checkout link is created: the tool returns the product page on the store's own site for each item. Pass variant IDs (items) and/or product URLs (product_urls). Use search_products first.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | – | Optional — leave unset unless an earlier create_checkout error asked for it. |
| discount_code | string | – | Discount code to apply (e.g. 'WELCOME10') |
| items | array | – | Products to add to cart by variant ID |
| note | string | – | Cart note visible to the merchant |
| product_urls | array | – | Products to add to cart by URL — resolved to variant IDs automatically |
No output schema declared.
No examples provided.
deals_discounts ~81
Show available bundles, deals, and ask about discount codes. Use when a customer asks about deals, bundles, savings, or says 'do you have any discounts?' Also use when multiple items are in cart to suggest bundle savings. Always ask if the customer has a discount code.
| Name | Type | Req | Description |
|---|---|---|---|
| discount_code | string | – | Customer's discount code if they have one |
No output schema declared.
No examples provided.
get_product ~119
Get full details for a specific product by SKU or title. Use when the user asks about a specific product by name (e.g. 'tell me about MIRA', 'show me the serum'). Do not use for browsing or recommendations — use search_products or skincare_recommend. Returns a widget card with the product details, image, price, and checkout button.
| Name | Type | Req | Description |
|---|---|---|---|
| sku | string | – | Exact product SKU (e.g. 'LL-4632379916336') |
| title | string | – | Product title to search for (fuzzy match) |
No output schema declared.
No examples provided.
get_research_note ~57
Get the summary and URL of a specific SearchShopAI Research Note by its slug (returned by search_research_notes).
| Name | Type | Req | Description |
|---|---|---|---|
| slug | string | yes | The note slug, e.g. 'the-ai-attribution-blind-spot' |
No output schema declared.
No examples provided.
search_products ~280
Browse and search the product catalog. Use when the user wants to see what's available, look up specific products, browse by category, compare options, or asks 'show me' / 'what do you have.' Do not use when the user needs personalized recommendations based on skin concerns — use skincare_recommend instead. Returns all matching products with prices, images, and checkout. Unlike skincare_recommend, this does not score or filter — it shows everything that matches so the user can decide.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | Filter by exact product category from the catalog (e.g. 'serum', 'treatment', 'cleanser', 'moisturizer'). Do not guess categories — only use this if the user explicitly mentions a catalog category. F… |
| max_price | number | – | Filter to products at or below this price |
| max_results | integer | – | Maximum products to return (default 10). Only set this if the user specifies a count — e.g. 'show me 2 devices' → 2. Otherwise leave it unset and the default will return all relevant matches up to 10. |
| query | string | yes | Search query (e.g. 'vitamin c serum', 'anti-aging', 'moisturizer under $50') |
No output schema declared.
No examples provided.
search_research_notes ~99
Search SearchShopAI's Research Notes blog — data studies, playbooks, and field notes on agentic commerce (AI attribution, MCP, AI catalog accuracy, ChatGPT ads). Returns matching articles with titles, summaries, and URLs. Use when asked what SearchShopAI has written or published about a topic.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | yes | Topic or keywords, e.g. 'attribution', 'MCP', 'hallucinated prices' |
No output schema declared.
No examples provided.
shop ~209
Start here for any shopping request. Pass the shopper's COMPLETE request in their own words and this tool will understand it and route to the right capability (personalized recommendation, catalog search, product lookup, or comparison), preserving every qualifier — concerns, skin type, budget, brand. Prefer this tool whenever the request is conversational or carries any nuance. The granular tools (search_products, get_product, compare_products, create_checkout) remain available as precise follow-ups.
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | – | Secondary hint only — brand filter if stated. |
| budget_max | number | – | Secondary hint only — maximum budget if stated. |
| intent | string | – | Secondary hint only — the primary signal is `request`. |
| product_refs | array | – | Secondary hint only — exact product titles/SKUs when already known. |
| request | string | yes | The shopper's complete request in their own words. Include every detail: concern, skin type, budget, brand, product names, questions. Do not summarize or drop qualifiers. |
No output schema declared.
No examples provided.
How do I install the Apostle — AI Men's Skincare Commerce MCP server?
Apostle — AI Men's Skincare Commerce is a hosted endpoint at https://searchshopai-mcp.fly.dev/mcp/apostleman, 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 · searchshopai-mcp.fly.dev
claude mcp add --transport http ai-searchshop-apostleman 'https://searchshopai-mcp.fly.dev/mcp/apostleman'
What is the Apostle — AI Men's Skincare Commerce MCP server?
Apostle — AI Men's Skincare Commerce is an MCP server listed in the public MCP registry as ai.searchshop/apostleman. Search, compare, and buy Apostle men's skincare: tinted moisturizer, face wash, and sets. This page covers its hosted endpoint (https://searchshopai-mcp.fly.dev/mcp/apostleman).
Is the Apostle — AI Men's Skincare Commerce MCP server safe to use?
Apostle — AI Men's Skincare Commerce scores 76 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 Apostle — AI Men's Skincare Commerce MCP server expose?
Apostle — AI Men's Skincare Commerce exposes 10 tools: shop, search_research_notes, get_research_note, search_products, get_product, and 5 more. Their descriptions and schemas cost roughly 1,252 tokens of context every time the server is loaded.
Does the Apostle — AI Men's Skincare Commerce MCP server require authentication?
No. We connected to Apostle — AI Men's Skincare Commerce without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Apostle — AI Men's Skincare Commerce MCP server still maintained?
Apostle — AI Men's Skincare Commerce is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.