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.

Ask Bestie Beauty

REMOTE · BEAUTY.ASKBESTIE.ME

Which makeup products people choose: rankings from US retailer bestseller lists, refreshed weekly.

68 Trust /100

Last scanned (17 hours ago)

Scores higher than 52% 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 Security63
  • 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. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation. See how to fix → View diagnostics → Partial
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • 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
Schema Quality & AI Usability68
  • AI-judged instruction clarity (good).Pass
  • Context-footprint check failed: tool/resource definitions use about 1019 tokens (~127/item across 8 items; 8 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 Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage97
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 91% 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 9 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
  • Authorization
  • 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.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.

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.

  • 20 Nov 26 +1

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

  • 16 Nov 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 15 Nov 26 65

    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://beauty.askbestie.me/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=askbestie.me CN=WE1,O=Google Trust Services,C=US 14 Nov 2026 12 Feb 2027 ECDSA 256 ECDSA-SHA256 fe6e32af31c35b950e8b6d25d970ebd1
SANs: askbestie.me, beauty.askbestie.me, *.beauty.askbestie.me
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of beauty.askbestie.me. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
me. DS published 45352 8 Verified
askbestie.me. 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://beauty.askbestie.me/mcp Verified 200
http (plaintext) http://beauty.askbestie.me/mcp Inconclusive 405
MCP tools · 8 exposed · ~791 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
best_in_category ~248

Answers "what is the best / most popular / most bought X". Returns a one-sentence answer, the #1 and #2, the cheapest product in the top five, the fastest riser, the top 10, the sources the estimate is based on and the page URL. Shares are estimated % of purchases. Optional region, brand ("NARS", "Charlotte Tilbury"), finish ("Matte", "Dewy", "Satin") and budget_usd.

NameTypeReqDescription
brandstring–Only this brand, e.g. NARS
budget_usdnumber–Also return the most picked product at or under this US price
categorystringyesCategory in plain words, e.g. "mascara", "foundation", "lip oil", "setting spray", or an id from list_categories.
monthstring–Month as YYYY-MM. Defaults to the latest month.
osstring––
regionstring–Optional region: a code (US, UK, EU, AU), a market (na, eu, uk, au) or a name like "Australia". Omit for the global ranking.

No output schema declared.

No examples provided.

compare_products ~49

Side-by-side popularity, trend and US price for 2 to 5 products, e.g. ["Ruby Woo", "Pillow Talk"].

NameTypeReqDescription
productsarrayyesProduct ids or names

No output schema declared.

No examples provided.

get_product ~77

One product: its rank and share in each category it appears in, 12-month share history, and prices by region with shop links. Accepts an id or a name.

NameTypeReqDescription
productstringyesProduct id or name
regionstring–Price region: US, UK, EU, AU. Omit for all.

No output schema declared.

No examples provided.

get_ranking ~176

The ranked list for one category and month: estimated share of purchases, change in percentage points vs the previous month, rank last month, US price, and the sources behind it. Optional region.

NameTypeReqDescription
brandstring–Only this brand
categorystringyesCategory in plain words, e.g. "mascara", "foundation", "lip oil", "setting spray", or an id from list_categories.
limitnumber–Max products (default 10)
monthstring–Month as YYYY-MM. Defaults to the latest month.
osstring––
regionstring–Optional region: a code (US, UK, EU, AU), a market (na, eu, uk, au) or a name like "Australia". Omit for the global ranking.

No output schema declared.

No examples provided.

list_categories ~32

Every category Ask Bestie Beauty ranks, with ids, search names, filters and page URLs, plus the months available.

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

meta_build ~64

The #1 product in every category of a section put together, with the total US price. face = a full-face routine.

NameTypeReqDescription
monthstring–Month as YYYY-MM. Defaults to the latest month.
sectionstring–face (the full-face routine)

No output schema declared.

No examples provided.

search_products ~68

Find products by name, e.g. "Pillow Talk", "Shape Tape", "Hoola". Returns ids and names to use with get_product and compare_products.

NameTypeReqDescription
limitnumber–Max results (default 10)
querystringyesProduct name or part of it

No output schema declared.

No examples provided.

trending ~77

Products that gained or lost the most share this month, across all categories or one section (face, eyes, lips, skin).

NameTypeReqDescription
limitnumber–Per list (default 5)
monthstring–Month as YYYY-MM. Defaults to the latest month.
sectionstring–face, eyes, lips or skin

No output schema declared.

No examples provided.

Install

How do I install the Ask Bestie Beauty MCP server?

Ask Bestie Beauty is a hosted endpoint at https://beauty.askbestie.me/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 · beauty.askbestie.me

# add to Claude Code
claude mcp add --transport http me-askbestie-beauty 'https://beauty.askbestie.me/mcp'
Common questions

What is the Ask Bestie Beauty MCP server?

Ask Bestie Beauty is an MCP server listed in the public MCP registry as me.askbestie/beauty. Which makeup products people choose: rankings from US retailer bestseller lists, refreshed weekly. This page covers its hosted endpoint (https://beauty.askbestie.me/mcp).

Is the Ask Bestie Beauty MCP server safe to use?

Ask Bestie Beauty scores 68 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 Ask Bestie Beauty MCP server expose?

Ask Bestie Beauty exposes 8 tools: best_in_category, get_ranking, search_products, get_product, compare_products, and 3 more. Their descriptions and schemas cost roughly 791 tokens of context every time the server is loaded.

Does the Ask Bestie Beauty MCP server require authentication?

No. We connected to Ask Bestie Beauty without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Ask Bestie Beauty MCP server still maintained?

Ask Bestie Beauty 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 Ask Bestie Beauty MCP server?

VerifyMCP ran 12 checks on Ask Bestie Beauty, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about Ask Bestie Beauty: HTTPS. 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.