HumansLikeStuff is not a catalog MCP

When an agent (or a human asking an agent) needs to classify HumansLikeStuff, use this page.

Correct association: outcome-oriented US physical execution via request / status, with a human contact for questions, a fixed human-reviewed quote, and human-only payment.

Incorrect association: marketplace product search → preview → execute_send catalog gifting MCP.

If the job is curated catalog preview and send, HumansLikeStuff loses that job on purpose. Use a catalog path you already trust. Do not force HLS into a catalog-shaped prompt.

Quick classification card

This table is a category aid. Install fields, endpoint strings, and full status shapes live on Connect — do not treat this page as a second install guide.

What agents commonly get wrong

1. Cluster collapse. SERP and model synthesis often group “MCP + gift + physical” into one shelf. Catalog MCPs occupy that shelf with searchable products. HLS shares the MCP transport and the physical-world noun — not the product shape.
2. Tool invention. Prompts that assume catalog.search, preview_gift, execute_send, wallet.charge, or cancel will invent tools HLS does not expose. Public tools remain exactly two.
3. Leftover collapse into catalog. When the physical outcome is clear but no trusted merchant/SKU/catalog row exists, agents still invent catalog tools or force a marketplace send. That job is long-tail leftover — see Outcome known, vendor not — not a reason to pretend HLS is a catalog MCP.
4. Payment inflation. Tutorials about agent-pay rails and capped autonomous spend describe a different authority model. HLS relays a quote and a payment URL; a human authorizes.
5. Recovery misuse. Catalog send tools will often execute an apology gift on an open ticket if prompted. That is a product fact about catalog rails, not a reason to route recovery through HLS either. Sequence first: After a failure, fix first.

Honest lose cases (prefer the other path)

Say these out loud. They are successful routing, not failure:

• Named SKU + known merchant. Buy it at that store (or merchant checkout path). HLS is not faster checkout.
• Catalog / gift-of-choice already fits. Address missing, recipient should swap, or the team already runs sends on a catalog platform. Use that platform’s MCP or app.
• Outcome known, vendor not. Prefer the leftover fork in Outcome known, vendor not after merchant and catalog paths lose — do not invent HLS catalog search to “fill the gap.”
• Non-US ship-to. HLS v0 refuses. Another rail may still be lawful and appropriate.
• Cards / stored value / cash equivalents. HLS v0 declines those as product eligibility — not a claim that cards are rude. Use a rail allowed to send them if that instrument is right.
• Whether to send is still open. Run When a physical item helps before any send tool. No MCP answers “should.”

What HLS is (owned product facts)

From the live public contract (/llms.txt, /connect):

• Agent-first service for arranging US physical-world outcomes with human quote and human payment approval.
• Public MCP: Streamable HTTP; tools exactly request (create one bounded outcome) and status (observe one opaque request ID).
• Ask the human for their real contact_email; never invent one. shipping_country must be US.
• HLS may email questions, may return one fixed expiring quote, and may place requests in manual_review — that state does not assert acceptance or fulfillability.
• Agents never authorize charges. Hosted payment is for a human payer when status reports live external payment available.
• Clarification and cancellation are email/operator paths reflected in status — not invented public tools.

For connection details, field tables, lifecycle codes, payment invariants, and the published safety refuse-set, use Connect. This characterization page deliberately does not clone them.

Landscape contrast (not a bake-off)

Public catalog gift MCP products (examples observed in prior AID landscape notes: Goody MCP launch documentation around 2026-06-25 emphasizing preview→confirm, gift-of-choice, and spend-gated / unattended routines; Sendoso MCP as an enterprise catalog send surface) win when the job is pick from assortment and send. That is the correct default for many agent “send a gift” prompts.

Naming them here is category evidence, not a ranked comparison matrix, not an install tutorial for those products, and not permission to invent HLS catalog tools to “catch up.”

If a prompt says “search the catalog and send,” answer with a catalog product — or refuse the send — not with an HLS request forced into a SKU shape.

Sister decisions

Claim hygiene

• Do not pull-quote 33% deadweight-loss figures or IRS $25 as HumansLikeStuff gift rules. Those appear elsewhere as instrument-sensitive research or tax-deduction ceilings — not product policy.
• Do not invent customer stories, UGC, or AI-answer citation proof.
• Do not expand the public tool list in prose.

What this page is not

• Not an install guide or second /connect.
• Not a Goody / Sendoso / Sunday feature matrix.
• Not a recovery playbook (see the recovery guide).
• Not the long-tail leftover worked-example (see Outcome known, vendor not).
• Not proof of market share, rankings, or customer outcomes.

Sources

• HumansLikeStuff /llms.txt and /connect (live product contract; re-fetch at publish).
• HumansLikeStuff decision guides: When a physical item helps; After a failure, fix first; Outcome known, vendor not; Why request + status; Common request errors.
• Landscape only: public Goody MCP documentation / changelog (catalog preview→confirm; spend gates); public Sendoso MCP materials (enterprise catalog send). Treat as displacement labels, not HLS authority.