Pick My Costume
REMOTE · MCP.PICKMYCOSTUME.COM
Recommends Halloween costumes you can actually build, with step-by-step DIY build guides.
Available components
Last scanned (19 hours ago)
Scores higher than 56% of remote servers
Reachable. Last reached 21 Nov 2026.
Category Entertainment and Games
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 404, 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
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability68
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 800 tokens (~266/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 Management53
- Stability observed for 16 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
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
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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 404, 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 →
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 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 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 40 to 43. That category is still filling its 30-day observation window: 12 days of observed history at the previous scan, 13 at this one. The score rises as the window fills, whether or not the server changes.
- 16 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 33 to 37. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 11 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Nov 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.
- 11 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.
- 9 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 7 Nov 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.
- 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
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://mcp.pickmycostume.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=pickmycostume.com | CN=WE1,O=Google Trust Services,C=US | 2 Oct 2026 | 31 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | 3b5f7e478164a00c13c241cff680bc49 |
| SANs: pickmycostume.com, mcp.pickmycostume.com, *.mcp.pickmycostume.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.pickmycostume.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| com. | DS published | 19718 | 13 | Verified |
| pickmycostume.com. | 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://mcp.pickmycostume.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.pickmycostume.com/mcp | Inconclusive | 404 |
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 →
get_build_guide Get a build guide ~102
Returns the step-by-step build instructions for one costume idea: the decision summary (time and effort level), the materials list with buy-vs-own tags, numbered build steps, safety notes, and common parent questions with answers. Accepts a costume idea id or a costume name.
| Name | Type | Req | Description |
|---|---|---|---|
| idea_id | string | yes | Costume idea id from pick_costume (e.g. 'classic-ghost', 'ballerina'), or a costume name like 'ghost'. |
No output schema declared.
No examples provided.
pick_costume Pick a costume ~352
Ranks Halloween costume ideas from a fixed catalog of 169 against the supplied audience, interests, vibe, effort level, and owned materials, and returns the top 3 matches. Each pick includes a why-line explaining the match, a thumbnail image, a link to its full build page, and the estimated time and effort. Owned items boost ranking: ideas whose materials are covered by the supplied owned items rank higher. Interest is the strongest ranking signal: ideas matching the stated interest outrank others.
| Name | Type | Req | Description |
|---|---|---|---|
| effort | string | – | Effort: 'easy'/'last-minute'/'couch-level', 'crafty'/'medium', or 'all-out'/'ambitious'. |
| group_size | number | – | Optional: how many people need costumes (for family/group picks). |
| interest | string | – | Optional but powerful: what the wearer is into, e.g. 'dinosaurs', 'animals', 'princesses', 'superheroes', 'video games', 'tv characters', 'food', 'sports'. This is the strongest ranking signal: ideas… |
| owned_items | array | – | Optional: things the user already owns, e.g. ['bedsheet'], ['cardboard', 'tape']. Ideas buildable from owned items rank higher. |
| vibe | string | – | Vibe: 'funny', 'scary' (or 'spooky'), 'cute' (or 'sweet'), 'chill' (or 'low-key'). |
| who_for | string | yes | Who the costume is for: e.g. 'toddler', '3-year-old', 'kid', 'adult', 'couple', 'family', 'group of 5'. |
No output schema declared.
No examples provided.
search_by_owning Search by owned items ~212
Ranks the fixed costume catalog by how many of each idea's materials are covered by the supplied household items, so ideas needing the least extra shopping rank highest. Each result includes what the idea still needs, with each still-needed item tagged buy, own, either, or make. Common household basics are assumed present in every home; the exact assumed list is returned with each call. An optional audience narrows results to who the costume is for.
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | Household items the user owns, e.g. ['bedsheet', 'cardboard', 'red t-shirt']. Common household basics (scissors, tape, markers, cardboard, a white t-shirt, a bedsheet, socks, and more) are assumed pr… |
| who_for | string | – | Optional: who the costume is for, e.g. 'toddler', 'adult', 'couple'. Narrows results to that audience when given. |
No output schema declared.
No examples provided.
How do I install the Pick My Costume MCP server?
Pick My Costume is a hosted endpoint at https://mcp.pickmycostume.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.pickmycostume.com
claude mcp add --transport http com-pickmycostume-pick-my-costume 'https://mcp.pickmycostume.com/mcp'
What is the Pick My Costume MCP server?
Pick My Costume is an MCP server listed in the public MCP registry as com.pickmycostume/pick-my-costume. Recommends Halloween costumes you can actually build, with step-by-step DIY build guides. This page covers its hosted endpoint (https://mcp.pickmycostume.com/mcp).
Is the Pick My Costume MCP server safe to use?
Pick My Costume scores 71 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 Pick My Costume MCP server expose?
Pick My Costume exposes 3 tools: pick_costume, get_build_guide, search_by_owning. Their descriptions and schemas cost roughly 666 tokens of context every time the server is loaded.
Does the Pick My Costume MCP server require authentication?
No. We connected to Pick My Costume without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Pick My Costume MCP server still maintained?
Pick My Costume 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 Pick My Costume MCP server?
VerifyMCP ran 12 checks on Pick My Costume, 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 Pick My Costume: 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.