Skip to content

HumansLikeStuff MCP server

com.humanslikestuff/mcphumanslikestuff.comstreamable-httpv0.4.0Scanned

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

2 tools: 1 change things and 1 only read.

Tools: 0 delete, 0 irreversible, 1 write, 1 read.
  • Reads private data · 0
  • Reads text others write · 1
  • Can send data out · 0
  • No findings

Tools listed without sign-in. Remote posture

With Anlyon

1 tool here changes things. Govern it.

  • Anlyon lists the tools and adopts none.
  • Each tool you adopt gets approvals and receipts.
  • Your agent never holds the key.
Govern this server →

A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.

What the HumansLikeStuff MCP server can do

The HumansLikeStuff MCP server is published by humanslikestuff.com, a domain the MCP Registry verified. It has 2 tools. It can create or change data (1 tool: request), but cannot delete data. 1 tool only reads.

1 tool brings in text other people can write (request).

None of the fixed checks matched anything in its tool definitions. That is not a safety guarantee.

Its remote endpoint lists its tools without sign-in.

Last scanned Nov 13, 2026, version 0.4.0.

Tools

Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.

2 tools

Changes things 1Claude Code: ask
  • requestCreate 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 gener…Reads text others writeNo findings

    Why it is in this group

    • The name "request" says "request": a word for a change.

    What it can reach

    • untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Create an HLS request
    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Show 1 read-only tool
  • statusExisting exact HLS request ID only: read-only lifecycle lookup.No findings

    Why it is in this group

    • The name "status" says "status": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • title: Check an HLS request
    • readOnlyHint: true
    • destructiveHint: false
    • idempotentHint: true
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Exfil surface

Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.

No private-data, untrusted-input, outbound path in this server alone: no tool is tagged private-data or outbound.

Reads private data0
Reads files, mail, messages, databases, secrets, calendars or repositories.
Reads text others write1
Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
Can send data out0
Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.

Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.

Remote posture

What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.

Tools listed without sign-in

Looked at Nov 20, 2026, 18:40 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.

Reachable
yes
HTTP status of an anonymous initialize
200
tools/list served without credentials
yes
Tools that change things, listed without credentials
1
Protocol version
2025-06-18
WWW-Authenticate on 401
not observed
resource_metadata in WWW-Authenticate
not observed
RFC 9728 protected resource metadata
not observed
Authorization servers
not observed
Legacy HTTP+SSE transport
no
Dynamic client registration
not observed
Client ID metadata documents
not observed
  • WarnThe whole server

    The endpoint served tools/list without credentials, and the list has 1 tool that changes things (1 write). Whether a call also works without credentials was not tested: tools are never called.

    Matched text

    https://mcp.humanslikestuff.com/mcp: tools/list returned 2 tools to an anonymous client, including request (write)

    What this check looks for

Findings

Matches of fixed checks, with the text they matched.

No check matched anything in these tool definitions. That is not a safety guarantee.

History

Changes to its tool definitions and to its remote endpoint, newest first.

No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.

Install

Pinned to version 0.4.0. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change or a way out, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__humanslikestuff__status"
    ],
    "ask": [
      "mcp__humanslikestuff__request"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as humanslikestuff. Review it before you use it.

Capability tags behind 1 rule
  • mcp__humanslikestuff__request untrusted-input

Pin

Keep the decision: fail CI when the tools change, follow every change, or show a badge.

Pin in CI

Fail a build when the tools you reviewed are not the tools the server serves today.

curl -s "https://radar.anlyon.com/api/v1/servers/com.humanslikestuff/mcp/verify?hash=170039c995693e4258dc20189af1031a1dd472cda3ab2bc1e0d5db1aaac6781d" | jq -e '.changed == false'

Pinned hash 170039c99569, from Nov 13, 2026, 11:18 UTC.

Watch

Get told when its tools change: a new tool, a new description, a new class.

https://radar.anlyon.com/servers/com.humanslikestuff/mcp/changes.xml

An Atom feed. Works in any feed reader or Slack's RSS app.

Badge

Anlyon Radar badge for com.humanslikestuff/mcp
[![Anlyon Radar](https://radar.anlyon.com/badge/com.humanslikestuff/mcp.svg)](https://radar.anlyon.com/servers/com.humanslikestuff/mcp)

Source: MCP Registry. Synced Oct 21, 2026, 17:56 UTC.

HumansLikeStuff MCP server: questions and answers

Answered from the scan above, not from the publisher's description.

Is the HumansLikeStuff MCP server safe?

No scan can promise that. What its definitions show: 2 tools, 1 of which can change, send or delete something, and 0 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.

Can the HumansLikeStuff MCP server delete data?

No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.

Can the HumansLikeStuff MCP server do things that cannot be undone?

No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.

What tools does the HumansLikeStuff MCP server have?

2 tools: 1 write, 1 read. request and status.

Does the HumansLikeStuff MCP server need sign-in or OAuth?

Its remote endpoint listed its tools to an anonymous client, without sign-in.

Does the HumansLikeStuff MCP server send data to outside services?

None of its tools sends, posts or publishes, or takes a recipient, channel or URL.

Has the HumansLikeStuff MCP server changed its tools?

Not since Anlyon Radar started tracking it. Last scanned Nov 13, 2026.