The Happy Hamper
REMOTE · WWW.THEHAPPYHAMPER.COM
Laundry pickup and delivery in St George, Utah: check an address, book and manage pickups.
Available components
Last scanned (7 hours ago)
Scores higher than 52% of remote servers
Reachable. Last reached 5 Nov 2026.
Category E-commerce
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
- Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (update_subscription). See how to fix → View diagnostics → Fail
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- 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 (good).Pass
- Tool/resource definitions use about 1942 tokens (~102/item across 19 items; 19 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
- Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage85
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 55% 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 19 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 20 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
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 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.
- 2 Nov 26 +1
- The server rewrote its instructions, which are the text every model session reads security
- 1 Nov 26 0
- The server rewrote its instructions, which are the text every model session reads security
- Tool “change_subscription” rewrote its description, which is the text the model reads security
- Stability: unverified → 0.03 ▲ functional
- 31 Oct 26 64
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 5 Nov 2026 · Probed https://www.thehappyhamper.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.thehappyhamper.com | CN=WE1,O=Google Trust Services,C=US | 19 Sept 2026 | 18 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c42c286c047979d70e53c728a3452777 |
| SANs: www.thehappyhamper.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 www.thehappyhamper.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| thehappyhamper.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 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=15552000; includeSubDomains |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | no-referrer |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.thehappyhamper.com/mcp | Verified | 200 | |
| http (plaintext) | http://www.thehappyhamper.com/mcp | HTTPS enforced | 301 | https://www.thehappyhamper.com/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 →
add_address Add an address ~134
Save a pickup or dropoff address. The reply's serviceZoneId is null when we don't pick up there. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| label | string | – | e.g. "Home" |
| line1 | string | yes | Street address, e.g. 123 Main St |
| line2 | string | – | Apartment or unit |
| note | string | – | Address notes: a gate code, where the bags will be, where to leave the clean laundry |
| postalCode | string | yes | ZIP code |
| state | string | yes | e.g. UT |
No output schema declared.
No examples provided.
add_card Add a card ~39
A link where the customer adds their card on our site; booking needs one. You can't take card details yourself. Needs the customer's Happy Hamper login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
book_one_time_pickup Book a one-time pickup ~128
One pickup on a date (check it with quote_one_time_pickup first). Get the customer's go-ahead on the price first. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| addressId | integer | yes | Pickup address |
| bags | – | yes | Bags each pickup is booked with: 1 or 2 (the 1-bag or 2-bag price) |
| date | string | yes | YYYY-MM-DD |
| discountCode | string | – | – |
| dropoffAddressId | integer | – | – |
| express | boolean | – | 24-hour turnaround, for a fee |
No output schema declared.
No examples provided.
cancel_pickup Cancel a pickup ~49
Cancel one upcoming pickup (a subscription carries on). Before 8:00 AM on the day, nothing is charged. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| pickupId | integer | yes | – |
No output schema declared.
No examples provided.
change_subscription Change a subscription's day, address or bags ~116
Moves a subscription to another option, address or number of bags: it starts again, with its pickups booked right away, each at the price for its date. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| addressId | integer | – | New pickup address |
| bags | – | – | Bags each pickup is booked with: 1 or 2 (the 1-bag or 2-bag price) |
| dropoffAddressId | integer | – | – |
| serviceZoneScheduleId | integer | – | – |
| subscriptionId | integer | yes | – |
No output schema declared.
No examples provided.
check_address Check an address ~101
Whether we pick up at an address, and if we do, its pickup options: each day and how often (every week or every other week), the first pickup, when it comes back, and the prices with any subscriber discount.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| line1 | string | yes | Street address, e.g. 123 Main St |
| postalCode | string | yes | ZIP code |
| state | string | yes | e.g. UT |
No output schema declared.
No examples provided.
get_account Their account ~45
The customer's profile, addresses (with their ids), Laundry preferences, whether a card is saved, subscriptions and one-time bookings, and upcoming pickups. Needs the customer's Happy Hamper login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_pickup_options Pickup options at an address ~71
The subscriptions the customer can start at one of their addresses: each option's serviceZoneScheduleId, day, how often, first pickup (nextDate), when it comes back (backDate), and prices with their discount. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| addressId | integer | yes | – |
No output schema declared.
No examples provided.
get_service_info What we charge and where ~41
The areas we pick up in, the current prices (in cents, before tax) and the subscriber discount, and the first day a pickup can be booked.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
join_waitlist Join the waitlist ~82
Leave an email for an address we don't pick up at yet; we email them when we do.
| Name | Type | Req | Description |
|---|---|---|---|
| city | string | yes | – |
| string | yes | – | |
| line1 | string | yes | Street address, e.g. 123 Main St |
| postalCode | string | yes | ZIP code |
| state | string | yes | e.g. UT |
No output schema declared.
No examples provided.
list_past_pickups Past pickups ~30
The customer's last 20 finished pickups, newest first. Needs the customer's Happy Hamper login.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
quote_one_time_pickup Price a one-time pickup ~67
What a one-time pickup at one of their addresses would cost on a date, whether that date can be booked, and when it would come back. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| addressId | integer | yes | – |
| date | string | yes | YYYY-MM-DD |
No output schema declared.
No examples provided.
set_laundry_preferences Set Laundry preferences ~63
The detergent and scent every load is washed with, unless a subscription or pickup says otherwise. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| detergent | string | yes | free_clear is fragrance-free, and takes no scent |
| scent | – | yes | null = unscented |
No output schema declared.
No examples provided.
start_subscription Start a subscription ~138
Regular pickups on an option from get_pickup_options. Get the customer's go-ahead on the day and price first. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| addressId | integer | yes | Pickup address |
| bagCount | integer | – | Bags every pickup has, extra ones included (extras cost more) |
| bags | – | yes | Bags each pickup is booked with: 1 or 2 (the 1-bag or 2-bag price) |
| discountCode | string | – | – |
| dropoffAddressId | integer | – | Where it comes back; the pickup address if left out |
| serviceZoneScheduleId | integer | yes | – |
No output schema declared.
No examples provided.
uncancel_pickup Bring back a canceled pickup ~48
Bring back a pickup canceled by mistake, as it was (until 1:00 AM on its day). Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| pickupId | integer | yes | – |
No output schema declared.
No examples provided.
update_address Change an address ~94
Change an address's label or Address notes, or its street (only until a pickup has been booked there). Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| addressId | integer | yes | – |
| city | string | – | – |
| label | – | – | – |
| line1 | string | – | – |
| line2 | – | – | – |
| note | – | – | Address notes |
| postalCode | string | – | – |
| state | string | – | – |
No output schema declared.
No examples provided.
update_pickup Change an upcoming pickup ~110
Change one upcoming pickup before we collect it: its bag count, Job notes, 24-hour turnaround, or detergent and scent. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| bagCount | integer | – | Bags every pickup has, extra ones included (extras cost more) |
| express | boolean | – | 24-hour turnaround, for a fee |
| jobNotes | – | – | – |
| pickupId | integer | yes | – |
| wash | – | – | Detergent and scent; null goes back to their Laundry preferences |
No output schema declared.
No examples provided.
update_profile Change their name or phone ~42
Change the customer's name or phone number. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| name | string | – | – |
| phone | string | – | A US phone number |
No output schema declared.
No examples provided.
update_subscription Pause, resume, cancel or adjust a subscription ~152
Pause (until a date, or until resumed), resume or cancel a subscription, or change its bag count, Job notes, or detergent and scent. Canceling also cancels its upcoming pickups. Needs the customer's Happy Hamper login.
| Name | Type | Req | Description |
|---|---|---|---|
| action | string | – | – |
| bagCount | integer | – | Bags every pickup has, extra ones included (extras cost more) |
| cancelReason | string | – | – |
| jobNotes | – | – | Job notes for every pickup; blank clears them |
| pausedUntil | string | – | With pause: pickups start again on this date (YYYY-MM-DD) |
| subscriptionId | integer | yes | – |
| wash | – | – | Detergent and scent; null goes back to their Laundry preferences |
No output schema declared.
No examples provided.
How do I install the The Happy Hamper MCP server?
The Happy Hamper is a hosted endpoint at https://www.thehappyhamper.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 · www.thehappyhamper.com
claude mcp add --transport http com-thehappyhamper-laundry 'https://www.thehappyhamper.com/mcp'
What is the The Happy Hamper MCP server?
The Happy Hamper is an MCP server listed in the public MCP registry as com.thehappyhamper/laundry. Laundry pickup and delivery in St George, Utah: check an address, book and manage pickups. This page covers its hosted endpoint (https://www.thehappyhamper.com/mcp).
Is the The Happy Hamper MCP server safe to use?
The Happy Hamper scores 66 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 The Happy Hamper MCP server expose?
The Happy Hamper exposes 19 tools: get_service_info, check_address, join_waitlist, get_account, update_profile, and 14 more. Their descriptions and schemas cost roughly 1,550 tokens of context every time the server is loaded.
Does the The Happy Hamper MCP server require authentication?
No. We connected to The Happy Hamper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the The Happy Hamper MCP server still maintained?
The Happy Hamper is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.