com.humanslikestuff/mcp

Est-ce que com.humanslikestuff/mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « com.humanslikestuff/mcp » est classé « Non encore testé ». Référencé dans l'annuaire. Seul le pentest comportemental fait foi, et il n'a pas encore été exécuté sur ce serveur. Le verdict est réévalué en continu ; consultez la fiche pour l'état à jour.

Méthode : MCP Hub analyse la description de chaque outil (couche 1) et, pour le verdict fort, exécute le serveur dans une micro-VM isolée avec leurres et réseau bloqué (couche 2). On publie des noms et des compteurs, jamais le contenu brut renvoyé par un outil.

Les 2 outils

• request≈ 1608 tokens

  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.

  Paramètres, retour & exemple (13)

  Paramètres

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

  Exemple d'appel

  {"name": "request", "arguments": {"outcome": "texte", "contact_email": "texte", "idempotency_key": "texte", "shipping_country": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"state": "received", "accepted": true, "terminal": true, "request_id": "texte", "next_action": "texte", "payment_mode": "test", "next_action_code": "texte", "human_action_required": true, "agent_authorized_charge": true, "external_payment_available": true}}

• status≈ 1117 tokens

  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.

  Paramètres, retour & exemple (1)

  Paramètres

  • request_id · string · requis
    Exact opaque request_id previously returned by HLS; no list, search, or email lookup is available.

  Exemple d'appel

  {"name": "status", "arguments": {"request_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}], "structuredContent": {"quote": {}, "state": "received", "payment": {}, "shipping": {}, "terminal": true, "request_id": "texte", "updated_at": "texte", "next_action": "texte", "open_question": "texte", "next_action_code": "texte", "fulfillment_notes": "texte", "human_action_required": true}}

C'est votre serveur ?

Revendiquez-le sur l'espace créateur (preuve GitHub, domaine ou npm) pour afficher le badge « propriétaire vérifié » et lancer un pentest comportemental à la demande afin d'obtenir le badge « Vérifié ».

Créer un compte / revendiquer →

Source

https://mcp.humanslikestuff.com/mcp