_ registry / mcp http-sse · checked 1h ago

HumansLikeStuff

https://mcp.humanslikestuff.com

Registry code: b9c469d29a10d891

api record

Use request only for a new outcome-shaped US physical request that needs HLS sourcing, personalization, multi-recipient handling, or coordination. If a known SKU and merchant make direct checkout straightforward, use the direct merchant instead. Before request, ask the human for their real contact email; never invent one. Save the returned request_id and use status with that exact ID. Humans approve payments; agents never authorize charges. Wait on manual work instead of creating duplicates.

endpoint
https://mcp.humanslikestuff.com/mcp
protocol
http-sse ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is HumansLikeStuff live?
Yes — it answered the hub's last check (checked 1h ago). It answered 99% of checks over the last 30 days.
Is HumansLikeStuff free to use?
Yes — the hub reached it with no key and no payment.
What tools does HumansLikeStuff have?
2 tools: status, request.
Is HumansLikeStuff safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.3%

90 days 99.6%· all time 99.6%

latency
238ms

last good check

priced tools
0

of 2 tools

_ answered our checks, 90 days 268 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
used for
  • request sourcing of a physical gift in the us
  • send personalized items to multiple recipients
  • check status of a sourcing request
takes → gives
text, data → data
tools
1 reads1 changes data
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 2 tools
2 never probed 0 of 2 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • status reads unknown 19h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "request_id"
      ],
      "properties": {
        "request_id": {
          "type": "string",
          "pattern": "^req_[A-Za-z0-9_-]{32}$",
          "description": "Exact opaque request_id previously returned by HLS; no list, search, or email lookup is available."
        }
      },
      "additionalProperties": false
    }
    arguments 15 lines
  • request changes data unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "https://json-schema.org/draft/2020-12/schema",
      "required": [
        "idempotency_key",
        "outcome",
        "contact_email",
        "shipping_country"
      ],
      "properties": {
        "message": {
          "type": "string",
          "maxLength": 2000,
          "description": "Optional human-provided recipient message."
        },
        "outcome": {
          "type": "string",
          "maxLength": 2000,
          "minLength": 1,
          "description": "Describe the desired safe US physical outcome, especially sourcing, personalization, multiple recipients, or coordination—not general advice or a known-SKU checkout."
        },
        "budget_cents": {
          "type": "integer",
          "maximum": 100000000,
          "minimum": 0,
          "description": "Optional human-provided total budget in US cents; not a quote or authorization."
        },
        "contact_email": {
          "type": "string",
          "format": "email",
          "pattern": "^(?!\\.)(?!.*\\.\\.)([A-Za-z0-9_'+\\-\\.]*)[A-Za-z0-9_+-]@([A-Za-z0-9][A-Za-z0-9\\-]*\\.)+[A-Za-z]{2,}$",
          "maxLength": 254,
          "description": "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": {
          "type": "string",
          "pattern": "^[0-9a-f]{8}-[0-9a-f]{4}-4[0-9a-f]{3}-[89ab][0-9a-f]{3}-[0-9a-f]{12}$",
          "description": "Client-generated canonical UUID v4 for one intended new request. Reuse only to retry that same intent after an uncertain response."
        },
        "recipient_count": {
          "type": "integer",
          "maximum": 100,
          "minimum": 1,
          "description": "Optional number of human recipients, from 1 through 100."
        },
        "arrival_deadline": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Optional requested US arrival date; a constraint, not a delivery promise."
        },
        "shipping_country": {
          "type": "string",
          "const": "US",
          "description": "HLS v0 ships only within the United States; use exactly US."
        },
        "artwork_references": {
          "type": "array",
          "items": {
            "type": "string",
            "format": "uri",
            "maxLength": 2048
          },
          "maxItems": 20,
          "description": "Optional artwork-reference URLs; HLS records them but does not fetch them during request intake."
        },
        "shipping_addresses": {
          "type": "array",
          "items": {
            "type": "object",
            "required": [
              "recipient_name",
              "address_line_1",
              "city",
              "state",
              "postal_code"
            ],
            "properties": {
              "city": {
                "type": "string",
                "maxLength": 100,
                "minLength": 1,
                "description": "US destination city."
              },
              "state": {
                "type": "string",
                "pattern": "^[A-Za-z]{2}$",
                "description": "Two-letter US state code."
              },
              "company": {
                "type": "string",
                "maxLength": 200,
                "description": "Optional company or organization at this US destination."
              },
              "postal_code": {
                "type": "string",
                "pattern": "^\\d{5}(?:-\\d{4})?$",
                "description": "Five-digit or ZIP+4 US postal code."
              },
              "address_line_1": {
                "type": "string",
                "maxLength": 200,
                "minLength": 1,
                "description": "Primary street-address line for this US destination."
              },
              "address_line_2": {
                "type": "string",
                "maxLength": 200,
                "description": "Optional secondary address line, such as a suite or unit."
              },
              "recipient_name": {
                "type": "string",
                "maxLength": 200,
                "minLength": 1,
                "description": "Human recipient name for this US destination."
              }
            },
            "description": "One complete US shipping destination supplied by the human.",
            "additionalProperties": false
          },
          "maxItems": 100,
          "description": "Optional exact US shipping destinations supplied by the human."
        },
        "additional_constraints": {
          "type": "string",
          "maxLength": 4000,
          "description": "Optional material, quantity, timing, packaging, or coordination constraints supplied by the human."
        },
        "payment_approval_context": {
          "type": "string",
          "maxLength": 1000,
          "description": "Optional human approval context only. Never include card, bank-account, password, or secret data."
        },
        "branding_or_personalization": {
          "type": "string",
          "maxLength": 4000,
          "description": "Optional human-provided branding or personalization requirements."
        }
      },
      "additionalProperties": false
    }
    arguments 140 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id b9c469d29a10d891.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/b9c469d29a10d891/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/b9c469d29a10d891/badge.svg)](https://brick.blue/agent/b9c469d29a10d891?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
60%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.