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.

A2A Cosmetics

REMOTE · MCP.A2A-COSMETICS.AI

Agent-to-Agent (A2A) hub for cosmetics: skin care, fragrance, sun care, dermocosmetics.

0 this week 83 Trust /100

Last scanned (17 hours ago)

Scores higher than 87% of remote servers

Reachable. Last reached 6 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 Security77
  • 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 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 is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
Schema Quality & AI Usability67
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 2463 tokens (~102/item across 24 items; 24 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage71
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 0% of tool parameters carry a description.Fail
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 24 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 25 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
What we tested

Checks we ran (13)

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

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.

  • 6 Nov 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
  • 5 Nov 26 0
    • Schema quality: 2102 → 2463 ▼ functional
    • Server version: 1.4.0 → 1.5.0 functional
    • New tool “get_product” functional
    • New tool “lookup_catalog” functional
    • New tool “search_catalog” functional
  • 4 Nov 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Schema quality: 1826 → 2102 ▼ functional
    • Server version: 1.3.6 → 1.4.0 functional
    • New tool “claim_seat” functional
  • 24 Oct 26 0
    • Server version: 1.3.5 → 1.3.6 functional
  • 21 Oct 26 0
    • Server version: 1.3.4 → 1.3.5 functional
  • 20 Oct 26 +1
    • Stability: 0.97 → pass security
  • 18 Oct 26 +1

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

  • 17 Oct 26 0
    • The server rewrote its instructions, which are the text every model session reads security
    • Tool “get_item” rewrote its description, which is the text the model reads security
    • Tool “verify_gtin” rewrote its description, which is the text the model reads security
    • Server version: 1.1.1 → 1.3.4 functional
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 6 Nov 2026 · Probed https://mcp.a2a-cosmetics.ai/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=a2a-cosmetics.ai CN=YE2,O=Let's Encrypt,C=US 20 Sept 2026 19 Dec 2026 ECDSA 256 ECDSA-SHA384 6319b4cd95ef002ef27f8b1a2e2e644915e
SANs: *.a2a-cosmetics.ai, a2a-cosmetics.ai
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 secure

Validation of mcp.a2a-cosmetics.ai. — Secure

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
ai. DS published 1814, 3799 8, 8 Verified
a2a-cosmetics.ai. DS published 2371 13 Verified
mcp.a2a-cosmetics.ai. Verified address RRset verified with the apex keys
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.a2a-cosmetics.ai/mcp Verified 200
http (plaintext) http://mcp.a2a-cosmetics.ai/mcp HTTPS enforced 301 https://mcp.a2a-cosmetics.ai/mcp
MCP tools · 24 exposed · ~2,245 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
a2a_handoff ~99

Hand the buyer to the right agent over Agent-to-Agent (A2A): with an allow decision the order intent goes to the counterparty's agent (envelope + card URL); with a deny, the market agent of the ship-to (the regulator's home page beside it) — a referral, never a sale to a consumer.

NameTypeReqDescription
counterparty_card_url–––
decision_id–––
intent_id–––

Structured output declared, but exposes no named fields.

No examples provided.

claim_seat ~232

A brand's agent claims its seat on A2A Cosmetics. Give the agent's card URL and the GTINs the brand claims: every GTIN must resolve on gtinfetch.ai to the maker the card names, and the category comes first (beauty and personal care proceed; a grocery record is referred to a2a-grocery.ai; peptides to a2a-peptides.ai; beer, wine and spirits are refused; an unresolved GTIN is refused). An accepted claim answers a challenge for the card's domain (a DNS TXT record or a well-known file); call again with the challenge_id once it is published: a pass moves the brand's rows from listed to claimed and answers the seat key. With the seat key, rows sets the seat's own price, availability, markets and claims, its own GTINs only. Every claim, accepted or refused, is logged. Verified is a person's step, never a tool's.

NameTypeReqDescription
card_urlstringyes–
challenge_id–––
gtins–––
rows–––
seat_key–––

Structured output declared, but exposes no named fields.

No examples provided.

compare_items ~47

Compare products, variants and shades side by side (two to eight GTINs or catalogue ids).

NameTypeReqDescription
decision_id–––
gtinsarrayyes–
market–––

Structured output declared, but exposes no named fields.

No examples provided.

create_order_intent ~84

Open an order between two agents: an order intent for a cleared product after the gate; the intent carries reason_code + rule_set_version and settles by x402 on a2a-x402.ai.

NameTypeReqDescription
decision_idstringyes–
gtinstringyes–
market–––
quantityintegeryes–
ship_to–––

Structured output declared, but exposes no named fields.

No examples provided.

find_verified_supplier ~86

Verified makers and brands for this product or product type in a market: supplier records (brand · manufacturer) with their claim status — verified first, then claimed, then listed. Takes the decision_id of an allow decision.

NameTypeReqDescription
decision_idstringyes–
gtin–––
limitinteger––
marketstringyes–
query–––

Structured output declared, but exposes no named fields.

No examples provided.

gate_transaction ~204

Allow or deny, with the reason and the rule. Takes a product (GTIN or catalogue id; optional), the ship-to market, the actor class and, when no record exists yet, the product type, ingredients (INCI) and claims. Returns one of twelve reason codes (ALLOW · REQUIRE_NOTIFICATION · REQUIRE_RESPONSIBLE_PERSON · DENY_NOT_A_COSMETIC_HERE · DENY_INGREDIENT_BANNED · DENY_INGREDIENT_LIMIT · DENY_CLAIM · DENY_MARKET · DENY_ACTOR_CLASS · DENY_UNLICENSED_AGENT · DENY_NO_GTIN · DENY_NOT_VERIFIED), the rule-set version, the source page and a decision_id for the downstream tools.

NameTypeReqDescription
actor_classstringyes–
channel–––
claims–––
credential–––
ingredients–––
product–––
product_type–––
ship_tostringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_availability ~77

In stock, and where: the availability block of a product (banners on the shelf of record, product URLs read live at load, store counts where the retailer record carries one) once gate_transaction has answered allow (decision_id).

NameTypeReqDescription
decision_idstringyes–
gtinstringyes–
market–––

Structured output declared, but exposes no named fields.

No examples provided.

get_enforcement_watch ~54

Recalls, bans and safety alerts, dated: enforcement events by market, ingredient, brand or since a date, each with its source page.

NameTypeReqDescription
market–––
query–––
since–––

Structured output declared, but exposes no named fields.

No examples provided.

get_ingredient_record ~67

One ingredient, and its status in every market: the standard ingredient name (INCI), aliases, and per rule set whether it is prohibited, restricted (with the limit or condition) or listed, each with the official list and its source page.

NameTypeReqDescription
ingredientstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_item ~97

Product record from gtinfetch.ai (signed); hub layer: seat, market, claim, price, availability. One product by GTIN, fully resolved: taxonomy path, variant or form, brand, market, claim status, market status, availability; after the gate also ingredients, claims, attributes, shades (parent and child) and offers.

NameTypeReqDescription
decision_id–––
gtinstringyes–
market–––

Structured output declared, but exposes no named fields.

No examples provided.

get_label_and_claims ~73

What the label must say, and which claims are allowed: the label requirements of the market and the claims rules of record (patterns that take a product out of the cosmetic class), each with its source page. Optional claims are checked against the rules.

NameTypeReqDescription
claims–––
marketstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_market_status ~73

Is this product type a cosmetic here? Product type by market: cosmetic, drug, special class (functional cosmetic, quasi-drug, grade 2, therapeutic good) or not permitted — with the rule-set version and the regulator's page.

NameTypeReqDescription
marketstringyes–
product_typestringyes–

Structured output declared, but exposes no named fields.

No examples provided.

get_notification_requirements ~69

What must be filed before sale in a market: the notification scheme, the responsible-person requirement and, for a product type in a special class, the extra step (review, registration, listing) — each with its source page.

NameTypeReqDescription
marketstringyes–
product_type–––

Structured output declared, but exposes no named fields.

No examples provided.

get_price ~70

The price for this buyer: the price basis (list · contract) from the supplier's offers on the record, once gate_transaction has answered allow (decision_id). Tiers buy services, never rank.

NameTypeReqDescription
decision_idstringyes–
gtinstringyes–
market–––

Structured output declared, but exposes no named fields.

No examples provided.

get_product ~112

Universal Commerce Protocol (UCP) product detail, version 2026-08-25 (dev.ucp.shopping.catalog.lookup). arguments: meta {'ucp-agent': {profile}} (required) and catalog {id: a GTIN or a variant id <market>:<gtin14>; context; filters}. One product of the priced subset with its variants per market, list price and claim_status; outside the subset, ucp.status error and not_found.

NameTypeReqDescription
catalog–––
meta–––

Structured output declared, but exposes no named fields.

No examples provided.

get_product_documents ~75

Safety report, certificate of analysis, data sheet: the documents on a product record (product information file pointer, safety assessment, certificate of analysis, safety data sheet), each a URL with its read date; decision_id required.

NameTypeReqDescription
decision_idstringyes–
gtinstringyes–
market–––

Structured output declared, but exposes no named fields.

No examples provided.

get_safety_label ~68

Warnings and age limits: the warning statements the market requires for a product type (sunscreen, hair dye, aerosols, children's products) and the safety-alert scheme of the regulator, each with its source page.

NameTypeReqDescription
marketstringyes–
product_type–––

Structured output declared, but exposes no named fields.

No examples provided.

log_audit ~54

Write a line to the audit record for a gate decision, an order intent or a handoff (returns the line id).

NameTypeReqDescription
kindstringyes–
note–––
reference_idstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

lookup_catalog ~114

Universal Commerce Protocol (UCP) catalogue lookup, version 2026-08-25 (dev.ucp.shopping.catalog.lookup). arguments: meta {'ucp-agent': {profile}} (required) and catalog {ids: product ids (GTIN) or variant ids (<market>:<gtin14>), up to 50; context; filters}. Found rows come back as products with their claim_status; an id outside the priced subset answers an info not_found message.

NameTypeReqDescription
catalog–––
meta–––

Structured output declared, but exposes no named fields.

No examples provided.

resolve_actor ~79

Who is asking? Brand, manufacturer, retailer or distributor (business to business); auditor (read-only); agent (inherits the class of the credential it presents — none returns DENY_UNLICENSED_AGENT). The consumer is never the counterparty. Returns communication_class: trade_information or public.

NameTypeReqDescription
actor_classstringyes–
credential–––

Structured output declared, but exposes no named fields.

No examples provided.

resolve_jurisdiction ~88

Where is this going? Resolve a ship-to (e.g. 'US', 'US-CA', 'UK', 'FR', 'EU-DE', 'JP') to one of the 18 markets and its rule set (13 rule sets; the six EU markets share one). UK is the label; machine fields carry the ISO code GB.

NameTypeReqDescription
ship_tostringyes–

Structured output declared, but exposes no named fields.

No examples provided.

search_catalog ~135

Universal Commerce Protocol (UCP) catalogue search, version 2026-08-25 (dev.ucp.shopping.catalog.search). arguments: meta {'ucp-agent': {profile}} (required) and catalog {query, context {address_country}, filters {categories, price {min, max} in minor units}, pagination {limit, cursor}}. Serves the priced subset: rows whose maker's list price is on the record (claimed seats with a listed price), keyed by GTIN, each with its claim_status. Every other row stays on search_cleared_items.

NameTypeReqDescription
catalog–––
meta–––

Structured output declared, but exposes no named fields.

No examples provided.

search_cleared_items ~109

Find products cleared for this market: validated product records in a market (query by product name, brand, product type or lane; optional lane filter: suncare · fragrance · dermocosmetics · peptides · korean · sustainable). Only validated rows are served; each item carries its claim status and market status.

NameTypeReqDescription
decision_id–––
lane–––
limitinteger––
marketstringyes–
product_type–––
query–––

Structured output declared, but exposes no named fields.

No examples provided.

verify_gtin ~79

Product record from gtinfetch.ai (signed); hub layer: seat, market, claim, price, availability. Is this GTIN real, and whose is it? Check-digit validation, the GS1 prefix, and the validated record(s) that carry it on this hub with their brand and claim status.

NameTypeReqDescription
gtinstringyes–

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the A2A Cosmetics MCP server?

A2A Cosmetics is a hosted endpoint at https://mcp.a2a-cosmetics.ai/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.a2a-cosmetics.ai

# add to Claude Code
claude mcp add --transport http greencore-solutions-a2a-cosmetics 'https://mcp.a2a-cosmetics.ai/mcp'
Common questions

What is the A2A Cosmetics MCP server?

A2A Cosmetics is an MCP server listed in the public MCP registry as io.github.greencore-solutions/a2a-cosmetics. Agent-to-Agent (A2A) hub for cosmetics: skin care, fragrance, sun care, dermocosmetics. This page covers its hosted endpoint (https://mcp.a2a-cosmetics.ai/mcp).

Is the A2A Cosmetics MCP server safe to use?

A2A Cosmetics scores 83 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 A2A Cosmetics MCP server expose?

A2A Cosmetics exposes 24 tools: resolve_jurisdiction, resolve_actor, gate_transaction, get_ingredient_record, get_market_status, and 19 more. Their descriptions and schemas cost roughly 2,245 tokens of context every time the server is loaded.

Does the A2A Cosmetics MCP server require authentication?

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

Is the A2A Cosmetics MCP server still maintained?

A2A Cosmetics is still listed as active in the MCP registry. We last reached this channel on 6 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 A2A Cosmetics MCP server?

VerifyMCP ran 13 checks on A2A Cosmetics, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. 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.