# HumansLikeStuff MCP (remote · mcp.humanslikestuff.com)

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

- Trust score: 80/100 (high trust)
- Change this week: 0
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-02

## Components

- remote · `mcp.humanslikestuff.com`: 80/100 (this document), [markdown](https://verifymcp.io/servers/com-humanslikestuff-mcp/mcp.md), [page](https://verifymcp.io/servers/com-humanslikestuff-mcp/mcp)

## Channel facts

- Endpoint: `https://mcp.humanslikestuff.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.4.0`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-02.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 639 tokens (~319/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 100/100
  - No destabilizing schema changes in the last 30 days.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the HumansLikeStuff MCP server?

HumansLikeStuff MCP is a hosted endpoint at https://mcp.humanslikestuff.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.

### Claude

```bash
claude mcp add --transport http com-humanslikestuff-mcp 'https://mcp.humanslikestuff.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-humanslikestuff-mcp": {
      "url": "https://mcp.humanslikestuff.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-humanslikestuff-mcp": {
      "type": "http",
      "url": "https://mcp.humanslikestuff.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-humanslikestuff-mcp]
url = "https://mcp.humanslikestuff.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-humanslikestuff-mcp": {
      "type": "remote",
      "url": "https://mcp.humanslikestuff.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-humanslikestuff-mcp --url 'https://mcp.humanslikestuff.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-humanslikestuff-mcp:
    url: "https://mcp.humanslikestuff.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-humanslikestuff-mcp": {
      "Transport": "http",
      "Url": "https://mcp.humanslikestuff.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-humanslikestuff-mcp -t streamable-http -u 'https://mcp.humanslikestuff.com/mcp'
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-28 (score 80, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-25 (score 80, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-09-24 (score 80, +1)

No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-22 (score 79, +1)

No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-20 (score 78, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 77, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 76, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 75, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (2)

### `request` (~438 tokens)

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.

Input parameters:

- `additional_constraints` (string): Optional material, quantity, timing, packaging, or coordination constraints supplied by the human.
- `arrival_deadline` (string): Optional requested US arrival date; a constraint, not a delivery promise.
- `artwork_references` (array): Optional artwork-reference URLs; HLS records them but does not fetch them during request intake.
- `branding_or_personalization` (string): Optional human-provided branding or personalization requirements.
- `budget_cents` (integer): Optional human-provided total budget in US cents; not a quote or authorization.
- `contact_email` (string, required): Ask the human for their real contact email for questions, quote approval, and payment instructions. Never invent, infer, or substitute an agent email.
- `idempotency_key` (string, required): Client-generated canonical UUID v4 for one intended new request. Reuse only to retry that same intent after an uncertain response.
- `message` (string): Optional human-provided recipient message.
- `outcome` (string, required): Describe the desired safe US physical outcome, especially sourcing, personalization, multiple recipients, or coordination—not general advice or a known-SKU checkout.
- `payment_approval_context` (string): Optional human approval context only. Never include card, bank-account, password, or secret data.
- `recipient_count` (integer): Optional number of human recipients, from 1 through 100.
- `shipping_addresses` (array): Optional exact US shipping destinations supplied by the human.
- `shipping_country` (string, required): HLS v0 ships only within the United States; use exactly US.

Output parameters:

- `accepted` (boolean): True means the request was recorded without automatic decline; it is not a fulfillment promise.
- `agent_authorized_charge` (boolean): Always false; an agent cannot authorize payment.
- `external_payment_available` (boolean): True only when this exact request exposes a usable live human-payment path.
- `human_action_required` (boolean): True only when the requesting human must answer a question or approve an available live payment.
- `next_action`: Bounded human-readable next-step guidance.
- `next_action_code` (string): Stable machine-readable code for the next supported action.
- `payment_mode` (string): Configured Stripe mode for this response.
- `request_id` (string): Opaque HLS request ID to save for exact-ID status checks.
- `state` (string): Current durable HLS request state.
- `terminal` (boolean): True only when no further lifecycle change is expected.

### `status` (~107 tokens)

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.

Input parameters:

- `request_id` (string, required): Exact opaque request_id previously returned by HLS; no list, search, or email lookup is available.

Output parameters:

- `fulfillment_notes`
- `human_action_required` (boolean): True only when the requesting human must answer a question or approve an available live payment.
- `next_action`
- `next_action_code` (string): Stable machine-readable code for the next supported action.
- `open_question`
- `payment` (object)
- `quote` (object)
- `request_id` (string): Exact opaque HLS request ID supplied by the caller.
- `shipping` (object)
- `state` (string): Current durable HLS request state.
- `terminal` (boolean): True only when no further lifecycle change is expected.
- `updated_at` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-humanslikestuff-mcp/mcp#diagnostics

## Score history

- 2026-10-02: 80
- 2026-10-01: 80
- 2026-09-30: 80
- 2026-09-29: 80
- 2026-09-28: 80
- 2026-09-27: 80
- 2026-09-26: 80
- 2026-09-25: 80
- 2026-09-24: 80
- 2026-09-23: 79
- 2026-09-22: 79
- 2026-09-21: 78
- 2026-09-20: 78
- 2026-09-19: 77
- 2026-09-18: 77
- 2026-09-17: 76
- 2026-09-16: 76
- 2026-09-15: 75
- 2026-09-14: 75
- 2026-09-13: 74
- 2026-09-12: 74
- 2026-09-11: 73
- 2026-09-10: 73
- 2026-09-09: 73
- 2026-09-08: 72
- 2026-09-07: 72
- 2026-09-06: 71
- 2026-09-05: 71
- 2026-09-04: 70
- 2026-09-03: 70

## Common questions

### What is the HumansLikeStuff MCP server?

HumansLikeStuff MCP is listed in the public MCP registry as com.humanslikestuff/mcp. Arrange US physical gifts and branded merchandise with human quote and payment approval. This page covers its hosted endpoint (https://mcp.humanslikestuff.com/mcp).

### Is the HumansLikeStuff MCP server safe to use?

HumansLikeStuff MCP scores 80 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 HumansLikeStuff MCP server expose?

HumansLikeStuff MCP exposes 2 tools: request, status. Their descriptions and schemas cost roughly 545 tokens of context every time the server is loaded.

### Does the HumansLikeStuff MCP server require authentication?

No. We connected to HumansLikeStuff MCP without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the HumansLikeStuff MCP server still maintained?

HumansLikeStuff MCP is still listed as active in the MCP registry. We last reached this channel on 2 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.humanslikestuff.com/mcp
- Website: https://humanslikestuff.com/connect
- Changelog RSS feed: https://verifymcp.io/servers/com-humanslikestuff-mcp/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-humanslikestuff-mcp/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-humanslikestuff-mcp/mcp