HumansLikeStuff MCP
REMOTE · MCP.HUMANSLIKESTUFF.COM · SCANNED OCT 2
Arrange US physical gifts and branded merchandise with human quote and payment approval.
Available components
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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, 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 Usability71
- AI-judged instruction clarity (excellent).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 3 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
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.
remote · mcp.humanslikestuff.com
claude mcp add --transport http com-humanslikestuff-mcp 'https://mcp.humanslikestuff.com/mcp'
{
"mcpServers": {
"com-humanslikestuff-mcp": {
"url": "https://mcp.humanslikestuff.com/mcp"
}
}
} {
"servers": {
"com-humanslikestuff-mcp": {
"type": "http",
"url": "https://mcp.humanslikestuff.com/mcp"
}
}
} [mcp_servers.com-humanslikestuff-mcp] url = "https://mcp.humanslikestuff.com/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-humanslikestuff-mcp": {
"type": "remote",
"url": "https://mcp.humanslikestuff.com/mcp",
"enabled": true
}
}
} openclaw mcp add com-humanslikestuff-mcp --url 'https://mcp.humanslikestuff.com/mcp' --transport streamable-http
mcp_servers:
com-humanslikestuff-mcp:
url: "https://mcp.humanslikestuff.com/mcp" {
"McpServers": {
"com-humanslikestuff-mcp": {
"Transport": "http",
"Url": "https://mcp.humanslikestuff.com/mcp"
}
}
} assistant mcp add com-humanslikestuff-mcp -t streamable-http -u 'https://mcp.humanslikestuff.com/mcp'
{
"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.
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.
- 28 Sept 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
- 25 Sept 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
- 24 Sept 26 +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.
- 22 Sept 26 +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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
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 2 Oct 2026 · Probed https://mcp.humanslikestuff.com/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=humanslikestuff.com | CN=WE1,O=Google Trust Services,C=US | 23 Aug 2026 | 21 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 21a422e85ab0987213ef190627fd75c2 |
| SANs: humanslikestuff.com, mcp.humanslikestuff.com, *.mcp.humanslikestuff.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.humanslikestuff.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| humanslikestuff.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 |
|---|---|
| x-content-type-options | nosniff |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.humanslikestuff.com/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.humanslikestuff.com/mcp | Inconclusive | 405 |
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 →
request Create an HLS request ~438
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 | yes | 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 | yes | 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 | yes | 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 | yes | HLS v0 ships only within the United States; use exactly US. |
| Name | Type | Req | Description |
|---|---|---|---|
| accepted | boolean | yes | True means the request was recorded without automatic decline; it is not a fulfillment promise. |
| agent_authorized_charge | boolean | yes | Always false; an agent cannot authorize payment. |
| external_payment_available | boolean | yes | True only when this exact request exposes a usable live human-payment path. |
| human_action_required | boolean | yes | True only when the requesting human must answer a question or approve an available live payment. |
| next_action | – | yes | Bounded human-readable next-step guidance. |
| next_action_code | string | yes | Stable machine-readable code for the next supported action. |
| payment_mode | string | yes | Configured Stripe mode for this response. |
| request_id | string | yes | Opaque HLS request ID to save for exact-ID status checks. |
| state | string | yes | Current durable HLS request state. |
| terminal | boolean | yes | True only when no further lifecycle change is expected. |
No examples provided.
status Check an HLS request ~107
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.
| Name | Type | Req | Description |
|---|---|---|---|
| request_id | string | yes | Exact opaque request_id previously returned by HLS; no list, search, or email lookup is available. |
| Name | Type | Req | Description |
|---|---|---|---|
| fulfillment_notes | – | yes | – |
| human_action_required | boolean | yes | True only when the requesting human must answer a question or approve an available live payment. |
| next_action | – | yes | – |
| next_action_code | string | yes | Stable machine-readable code for the next supported action. |
| open_question | – | yes | – |
| payment | object | yes | – |
| quote | object | yes | – |
| request_id | string | yes | Exact opaque HLS request ID supplied by the caller. |
| shipping | object | yes | – |
| state | string | yes | Current durable HLS request state. |
| terminal | boolean | yes | True only when no further lifecycle change is expected. |
| updated_at | string | yes | – |
No examples provided.
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.