HumansLikeStuff MCP

com.humanslikestuffPublished by humanslikestuff.comOfficial publisherv0.4.0Updated Oct 27, 2026

Arrange US physical gifts and branded merchandise with human quote and payment approval.

VerifiedStreamable HTTPWeb executableProductivity & WorkflowBusiness & Commerce

Overview

AI-generated overview

Remote MCP server that lets an assistant file a request for a human-run US physical errand, such as gifts or branded merchandise, and check its status.

What you can do
  • Create a new request for a safe US physical outcome that needs sourcing, personalization, multiple recipients or coordination
  • Supply a real contact email so the human service can follow up
  • Look up the read-only lifecycle status of an existing request by its exact ID
  • See bounded public state, questions, quotes and payment instructions returned for a request
When to use it
Useful when a user wants something physically arranged in the US — a gift, branded merchandise or a coordinated delivery — and needs a human to source it, quote it and get payment approval. Not intended for general advice or for tasks that need no real-world fulfillment.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. A genuine contact email is required when creating a request, and an existing request ID is needed for status lookups.
Before you install
Requests are handled by a human service and involve quotes and payment, so costs may follow; payment requires human approval. The contact email is shared with the service and must be real, not fabricated. Creating a request is a write action; status lookups are read-only and do not authorize payment.

Installation

In SourceWeft

  1. Open HumansLikeStuff MCP in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/com.humanslikestuff%2Fmcp/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

{
  "mcpServers": {
    "humanslikestuff": {
      "type": "http",
      "url": "https://mcp.humanslikestuff.com/mcp"
    }
  }
}

Tools

2

request

Create an HLS request

Create one new HLS request to the human-operated service for a safe US physical outcome that benefits from sourcing, personalization, multiple recipients, or coordination—not general advice. Ask the human for a real contact_email and never fabricate one. Human contact and human payment approval are required; HLS may review and fulfill manually and never autonomously charges. If the exact SKU and merchant are known and direct agent checkout is straightforward, prefer direct merchant execution. Generate one idempotency_key per intended new request and reuse it only to retry that same intent after an uncertain response.

Parametersmessageoutcomerequiredbudget_centscontact_emailrequiredidempotency_keyrequiredrecipient_countarrival_deadlineshipping_countryrequiredartwork_referencesshipping_addressesadditional_constraintspayment_approval_context+1 more

status

Check an HLS request

Existing exact HLS request ID only: read-only lifecycle lookup. It does not create or modify a request/order or authorize payment. For long-running or manual work, check status or wait rather than creating another request. Returns only bounded public state, question, quote/payment instruction, fulfillment/shipping update, and next action; it does not list or search requests.

Parametersrequest_idrequired

Version history

1
  1. v0.4.0LatestSep 16, 2026

Score

72% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts

    Publish an icon in the registry entry.

  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.