MyHairMail Agent Tools
REMOTE · MCP.MYHAIRMAILTOOLS.COM · SCANNED OCT 4
Open, read-only wig stock, restock ETAs and cross-brand color matching. No key; fair-use limits.
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 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS check failed: the endpoint is reachable over plaintext HTTP. See how to fix → View diagnostics → Fail
- 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 Usability67
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 939 tokens (~313/item across 3 items; 3 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 Management27
- Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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
- 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 4 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 MyHairMail Agent Tools MCP server?
MyHairMail Agent Tools is a hosted endpoint at https://mcp.myhairmailtools.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.myhairmailtools.com
claude mcp add --transport http com-myhairmailtools-agent-tools 'https://mcp.myhairmailtools.com/mcp'
{
"mcpServers": {
"com-myhairmailtools-agent-tools": {
"url": "https://mcp.myhairmailtools.com/mcp"
}
}
} {
"servers": {
"com-myhairmailtools-agent-tools": {
"type": "http",
"url": "https://mcp.myhairmailtools.com/mcp"
}
}
} [mcp_servers.com-myhairmailtools-agent-tools] url = "https://mcp.myhairmailtools.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-myhairmailtools-agent-tools": {
"type": "remote",
"url": "https://mcp.myhairmailtools.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-myhairmailtools-agent-tools --url 'https://mcp.myhairmailtools.com/mcp' --transport streamable-http
mcp_servers:
com-myhairmailtools-agent-tools:
url: "https://mcp.myhairmailtools.com/mcp" {
"McpServers": {
"com-myhairmailtools-agent-tools": {
"Transport": "http",
"Url": "https://mcp.myhairmailtools.com/mcp"
}
}
} assistant mcp add com-myhairmailtools-agent-tools -t streamable-http -u 'https://mcp.myhairmailtools.com/mcp'
{
"mcpServers": {
"com-myhairmailtools-agent-tools": {
"type": "http",
"url": "https://mcp.myhairmailtools.com/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.
- 4 Oct 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.
- 1 Oct 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.
- 29 Sept 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.
- 27 Sept 26 +7
- Stability: unverified → 0.03 ▲ functional
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Sept 26 +41
- Injection markers: unverified → pass ▲ security
- Transport: fail → pass ▲ security
- First check of Judged manipulation: pass security
- Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Tool coverage: 67 functional
- First check of Schema quality: fail functional
- First check of Schema quality: excellent functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail 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
- 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 4 Oct 2026 · Probed https://mcp.myhairmailtools.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=myhairmailtools.com | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 19 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 139577304c77b16e134d861a1145616e |
| SANs: myhairmailtools.com, *.myhairmailtools.com | ||||||
| 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 mcp.myhairmailtools.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| myhairmailtools.com. | 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.myhairmailtools.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.myhairmailtools.com/mcp | Served over HTTP | 200 |
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_stock Check wig stock by colour ~291
Live availability of one wig or hairpiece style at MyHairMail, per colour, from the manufacturer's factory feed (not a nightly sync). Distinguishes backordered and discontinued colours, which the Shopify catalog reports as 'available' or omits. availability is one of in_stock | backordered (orderable now, ships when restocked; restock_eta_week given when known) | out_of_stock | discontinued (will not restock). Returns price_usd, compare_at_price_usd and a product_url to buy on myhairmail.com. With color: one product; without color: up to 12 colours (has_more=true means query a specific colour). Not found: did_you_mean styles, or supported_brands if the brand is not carried. When a colour is not buyable now, the response includes next_step naming the tool that finds an equivalent. Never returns quantities. Terms: https://mcp.myhairmailtools.com/terms
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name, e.g. 'Jon Renau', 'Raquel Welch', 'Belle Tress' |
| color | string | – | Color code or name, e.g. '12FS8' or 'Shaded Praline'. Optional; if omitted, returns per-color availability for up to 12 colors. |
| style | string | yes | Style name, e.g. 'Luna', 'Vesper' |
| Name | Type | Req | Description |
|---|---|---|---|
| colors | array | – | – |
| did_you_mean | array | – | – |
| has_more | boolean | – | – |
| match | boolean | yes | – |
| next_step | object | – | – |
| note | string | – | – |
| product | object | – | – |
| retailer | string | yes | – |
| supported_brands | array | – | – |
No examples provided.
color_crossmatch Match a colour across wig brands ~253
Closest equivalent colours in ONE target brand for a known colour from a DIFFERENT brand, using MyHairMail's cross-brand colour mapping. Answers 'what is my shade called in brand X' — relevant when a colour is discontinued or out of stock, or when a shopper knows their shade in one brand and is shopping another. Returns up to 3 matches ranked by similarity (closest > close > approximate) with short tone notes, and when available an example_in_stock_style + product_url in the target brand. Same-brand requests are refused (use check_stock for other colours of the same brand). One source colour and one target brand per call; 'all brands' and wildcards are not supported. Unknown brand: supported_brands is returned. Terms: https://mcp.myhairmailtools.com/terms
| Name | Type | Req | Description |
|---|---|---|---|
| source_brand | string | yes | Brand of the known color, e.g. 'Jon Renau' |
| source_color | string | yes | Color code or name, e.g. '12FS8' or 'Shaded Praline' |
| target_brand | string | yes | Single brand to match into, e.g. 'Belle Tress'. Wildcards and 'all brands' are not supported. |
| Name | Type | Req | Description |
|---|---|---|---|
| match | boolean | yes | – |
| matches | array | – | – |
| note | string | – | – |
| reason | string | – | – |
| retailer | string | yes | – |
| source_brand | string | – | – |
| source_color | string | – | – |
| source_color_query | string | – | – |
| supported_brands | array | – | – |
| target_brand | string | – | – |
No examples provided.
get_restock_eta Get restock week for a colour ~209
Expected back-in-stock week for one colour of a MyHairMail wig that is backordered or out of stock, from live factory availability. restock_eta_week is the Monday (YYYY-MM-DD) of the ISO week of expected arrival; eta_display is human phrasing ('week of Nov 9'). preorder_available=true means it can be ordered now and ships when restocked. discontinued means it will not restock; the response then includes next_step naming the tool that finds an equivalent. For an in_stock colour this simply confirms availability. Never returns quantities. Terms: https://mcp.myhairmailtools.com/terms
| Name | Type | Req | Description |
|---|---|---|---|
| brand | string | yes | Brand name, e.g. 'Envy', 'Jon Renau' |
| color | string | yes | Colour name or code exactly as listed by check_stock, e.g. 'Prosecco' or 'FS26/31S6' |
| style | string | yes | Style name, e.g. 'Charlotte Hand-Tied' |
| Name | Type | Req | Description |
|---|---|---|---|
| did_you_mean | array | – | – |
| match | boolean | yes | – |
| next_step | object | – | – |
| note | string | – | – |
| product | object | – | – |
| retailer | string | yes | – |
| supported_brands | array | – | – |
No examples provided.
What is the MyHairMail Agent Tools MCP server?
MyHairMail Agent Tools is an MCP server listed in the public MCP registry as com.myhairmailtools/agent-tools. Open, read-only wig stock, restock ETAs and cross-brand color matching. No key; fair-use limits. This page covers its hosted endpoint (https://mcp.myhairmailtools.com/mcp).
Is the MyHairMail Agent Tools MCP server safe to use?
MyHairMail Agent Tools 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 MyHairMail Agent Tools MCP server expose?
MyHairMail Agent Tools exposes 3 tools: check_stock, get_restock_eta, color_crossmatch. Their descriptions and schemas cost roughly 753 tokens of context every time the server is loaded.
Does the MyHairMail Agent Tools MCP server require authentication?
No. We connected to MyHairMail Agent Tools without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the MyHairMail Agent Tools MCP server still maintained?
MyHairMail Agent Tools is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.