A2A Cosmetics
REMOTE · MCP.A2A-COSMETICS.AI · SCANNED SEP 22
Agent-to-Agent (A2A) hub for cosmetics: skin care, fragrance, sun care, dermocosmetics.
Available components
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 Usability69
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1757 tokens (~87/item across 20 items; 20 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management7
- Stability observed for 2 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 20 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 21 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
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
claude mcp add --transport http greencore-solutions-a2a-cosmetics 'https://mcp.a2a-cosmetics.ai/mcp'
{
"mcpServers": {
"greencore-solutions-a2a-cosmetics": {
"url": "https://mcp.a2a-cosmetics.ai/mcp"
}
}
} {
"servers": {
"greencore-solutions-a2a-cosmetics": {
"type": "http",
"url": "https://mcp.a2a-cosmetics.ai/mcp"
}
}
} [mcp_servers.greencore-solutions-a2a-cosmetics] url = "https://mcp.a2a-cosmetics.ai/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"greencore-solutions-a2a-cosmetics": {
"type": "remote",
"url": "https://mcp.a2a-cosmetics.ai/mcp",
"enabled": true
}
}
} openclaw mcp add greencore-solutions-a2a-cosmetics --url 'https://mcp.a2a-cosmetics.ai/mcp' --transport streamable-http
mcp_servers:
greencore-solutions-a2a-cosmetics:
url: "https://mcp.a2a-cosmetics.ai/mcp" {
"McpServers": {
"greencore-solutions-a2a-cosmetics": {
"Transport": "http",
"Url": "https://mcp.a2a-cosmetics.ai/mcp"
}
}
} assistant mcp add greencore-solutions-a2a-cosmetics -t streamable-http -u 'https://mcp.a2a-cosmetics.ai/mcp'
{
"mcpServers": {
"greencore-solutions-a2a-cosmetics": {
"type": "http",
"url": "https://mcp.a2a-cosmetics.ai/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 22 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 0
- Stability: unverified → 0.03 ▲ functional
- 20 Sept 26 68
First indexed and scored.
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 22 Sept 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 insecure
Validation of mcp.a2a-cosmetics.ai. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| ai. | present | 3799 | 8 | Verified |
| a2a-cosmetics.ai. | 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://mcp.a2a-cosmetics.ai/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.a2a-cosmetics.ai/mcp | HTTPS enforced | 301 | https://mcp.a2a-cosmetics.ai/mcp |
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 →
a2a_handoff 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.
| Name | Type | Req | Description |
|---|---|---|---|
| counterparty_card_url | – | – | – |
| decision_id | – | – | – |
| intent_id | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
compare_items Compare Items ~47
Compare products, variants and shades side by side (two to eight GTINs or catalogue ids).
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | – | – | – |
| gtins | array | yes | – |
| market | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
create_order_intent 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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| gtin | string | yes | – |
| market | – | – | – |
| quantity | integer | yes | – |
| ship_to | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
find_verified_supplier 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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| gtin | – | – | – |
| limit | integer | – | – |
| market | string | yes | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
gate_transaction 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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_class | string | yes | – |
| channel | – | – | – |
| claims | – | – | – |
| credential | – | – | – |
| ingredients | – | – | – |
| product | – | – | – |
| product_type | – | – | – |
| ship_to | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_availability 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).
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| gtin | string | yes | – |
| market | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_enforcement_watch 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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | – | – | – |
| query | – | – | – |
| since | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_ingredient_record 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ingredient | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_item Get Item ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | – | – | – |
| gtin | string | yes | – |
| market | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_label_and_claims 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.
| Name | Type | Req | Description |
|---|---|---|---|
| claims | – | – | – |
| market | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_market_status 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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
| product_type | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_notification_requirements 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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
| product_type | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_price 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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| gtin | string | yes | – |
| market | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_product_documents 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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | string | yes | – |
| gtin | string | yes | – |
| market | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
get_safety_label 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.
| Name | Type | Req | Description |
|---|---|---|---|
| market | string | yes | – |
| product_type | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
log_audit Log Audit ~54
Write a line to the audit record for a gate decision, an order intent or a handoff (returns the line id).
| Name | Type | Req | Description |
|---|---|---|---|
| kind | string | yes | – |
| note | – | – | – |
| reference_id | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_actor 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.
| Name | Type | Req | Description |
|---|---|---|---|
| actor_class | string | yes | – |
| credential | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
resolve_jurisdiction 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.
| Name | Type | Req | Description |
|---|---|---|---|
| ship_to | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
search_cleared_items 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.
| Name | Type | Req | Description |
|---|---|---|---|
| decision_id | – | – | – |
| lane | – | – | – |
| limit | integer | – | – |
| market | string | yes | – |
| product_type | – | – | – |
| query | – | – | – |
Structured output declared, but exposes no named fields.
No examples provided.
verify_gtin Verify Gtin ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| gtin | string | yes | – |
Structured output declared, but exposes no named fields.
No examples provided.
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 69 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 20 tools: resolve_jurisdiction, resolve_actor, gate_transaction, get_ingredient_record, get_market_status, and 15 more. Their descriptions and schemas cost roughly 1,606 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 22 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.