dev.hackshop/hackshop-mcp

Est-ce que dev.hackshop/hackshop-mcp est sûr ?

Au dernier audit MCP Hub, le serveur MCP « dev.hackshop/hackshop-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 10 outils

• assess_hackability≈ 138 tokens

  Look up a device by id, exact name or substring and return hackability, brick risk, firmware links, curated firmware playbooks, community size, build page and agent platform support. Input: `device_name` 1-200 chars.

  Paramètres, retour & exemple (1)

  Paramètres

  • device_name · string · requis
    Device name or id, 1-200 characters.

  Exemple d'appel

  {"name": "assess_hackability", "arguments": {"device_name": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• check_firmware_compatibility≈ 383 tokens

  Fail-closed compatibility check for one firmware playbook. Required model, codename, revision, SoC or firmware identifiers must exactly match a curated target; missing facts return unknown and mismatches return unsupported.

  Paramètres, retour & exemple (2)

  Paramètres

  • observed · object · requis
  • playbook_id · string · requis

  Exemple d'appel

  {"name": "check_firmware_compatibility", "arguments": {"observed": {}, "playbook_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_firmware_playbooks≈ 233 tokens

  Find curated owner-authorized firmware, local-protocol and cloud-replacement playbooks. Results prefer the least-invasive path and are not compatibility approval; call check_firmware_compatibility before preparation.

  Paramètres, retour & exemple (5)

  Paramètres

  • limit · number · optionnel
  • query · string · requis
  • device_id · string · optionnel
  • intervention · string · optionnel · official_local_api | protocol_replacement | cloud_replacement | stock_firmware_overlay | custom_userspace | full_replacement | research_only
  • risk_tolerance · string · optionnel · low | moderate | high

  Exemple d'appel

  {"name": "find_firmware_playbooks", "arguments": {"query": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• find_reverse_engineering_examples≈ 403 tokens

  Search Hackshop's curated hardware reverse-engineering examples and research methods. With no query, returns the newest dated examples first. Evidence labels distinguish reproduced work, documented implementations, author demos and analysis methods; they do not imply compatibility with similar-looking hardware.

  Paramètres, retour & exemple (7)

  Paramètres

  • limit · number · optionnel
  • query · string · optionnel
    Optional case-insensitive search across title, device, exact models, summary, outcome and tags. Empty returns the latest examples.
  • method · string · optionnel · root | firmware | protocol | app_api | hardware_bus | repurpose | analysis_tool
  • category · string · optionnel · display | speaker | input | sensor | bulb | sbc | handheld | mini-pc
  • evidence · string · optionnel · reproduced | documented | author_demo | analysis_method
  • use_case · string · optionnel · calendar | ai_interface | info_panel | smart_home | art
    Filter source-backed design starters by intended use.
  • max_device_price_usd · number · optionnel
    Maximum lowest-listed device price in USD; unknown prices excluded. Accessories, host, shipping and tax are extra; availability is returned separately.

  Exemple d'appel

  {"name": "find_reverse_engineering_examples", "arguments": {"limit": 1, "query": "texte", "method": "root", "category": "display", "evidence": "reproduced", "use_case": "calendar"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_build_plan≈ 164 tokens

  Return the complete deterministic build plan for a catalog device id: difficulty, board-specific flash warnings, parts, shopping list with buy_options, prices checked date and purchase policy, steps, machine-readable assembly with verify checks, commands, links, caveats and an agent-ready brief. Input: `device_id` 1-200 chars.

  Paramètres, retour & exemple (1)

  Paramètres

  • device_id · string · requis
    Catalog device id, 1-200 characters.

  Exemple d'appel

  {"name": "get_build_plan", "arguments": {"device_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• get_firmware_playbook≈ 119 tokens

  Return a curated firmware playbook with exact targets, prerequisites, backups, recovery, independent risk axes, sources, validation checks and the human-only destructive-action boundary.

  Paramètres, retour & exemple (1)

  Paramètres

  • playbook_id · string · requis

  Exemple d'appel

  {"name": "get_firmware_playbook", "arguments": {"playbook_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• intake_gadget≈ 100 tokens

  Return the 4 intake questions (where it lives, how you interact, room sensing, budget), why each matters and how each answer maps to plan_gadget. Ask the human these, then call plan_gadget with `answers`. No input.

  Paramètres, retour & exemple (0)

  Exemple d'appel

  {"name": "intake_gadget", "arguments": {}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• plan_gadget≈ 867 tokens

  Deterministically plan a physical body for an AI agent using Meta Muse boards. Ask the intake questions first (intake_gadget, or the `questions` this returns until `intake.complete` is true), then pass the human's choices as `answers`. Inputs: `idea` 3-2000 chars (optional when `answers` or `needs` are given); `answers` {size, interaction, sensing, budget} using the intake option values; `platform` one of muse-esp32, muse-linux, any (default any); `budget_usd` number greater than 0, up to 100000; `owned_device_ids` up to 50 catalog ids; `needs` values: voice, screen, images, touch, camera, air-sensors, e-ink, battery, round, home-tunnel, big-screen, compute, linux; `size` one of pocket, desk, wall, hidden, any (default any); `limit` 1-5 (default 3). Boards that meet the hard needs and the budget rank first, cheapest first. Returns fit, notes, warnings, intake status, questions, picks with difficulty, terms and next steps.

  Paramètres, retour & exemple (8)

  Paramètres

  • idea · string · optionnel
    Gadget idea or use case, 3-2000 characters. Optional when `answers` or `needs` are given.
  • size · string · optionnel · pocket | desk | wall | hidden | any
    Preferred size or placement: pocket, desk, wall, hidden, any. Default any.
  • limit · number · optionnel
    Number of picks to return: 1-5, default 3.
  • needs · array · optionnel
    Optional explicit needs. Allowed: voice, screen, images, touch, camera, air-sensors, e-ink, battery, round, home-tunnel, big-screen, compute, linux.
  • answers · object · optionnel
    The human's intake answers, by question id, using the option values from intake_gadget.
  • platform · string · optionnel · muse-esp32 | muse-linux | any
    Platform filter: muse-esp32, muse-linux, or any. Default any.
  • budget_usd · number · optionnel
    Optional hardware budget in USD. Must be greater than 0, max 100000.
  • owned_device_ids · array · optionnel
    Catalog device ids the user already owns. Max 50.

  Exemple d'appel

  {"name": "plan_gadget", "arguments": {"idea": "texte", "size": "pocket", "limit": 1, "needs": [], "answers": {}, "platform": "muse-esp32"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• prepare_firmware_job≈ 390 tokens

  Prepare a non-executing firmware manifest after owner authorization and an exact compatibility match. Returns backup, recovery, sources, validation and stop points; never returns a flash command.

  Paramètres, retour & exemple (3)

  Paramètres

  • observed · object · requis
  • playbook_id · string · requis
  • owner_authorized · boolean · requis

  Exemple d'appel

  {"name": "prepare_firmware_job", "arguments": {"observed": {}, "playbook_id": "texte", "owner_authorized": true}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

• verify_firmware_artifact≈ 176 tokens

  Compare a caller-supplied filename, source URL and SHA-256 with Hackshop's curated metadata. Hackshop does not fetch, upload or redistribute the artifact; absent hashes return unknown.

  Paramètres, retour & exemple (4)

  Paramètres

  • sha256 · string · requis
  • filename · string · requis
  • source_url · string · requis
  • playbook_id · string · requis

  Exemple d'appel

  {"name": "verify_firmware_artifact", "arguments": {"sha256": "texte", "filename": "texte", "source_url": "texte", "playbook_id": "texte"}}

  Exemple de retour

  {"content": [{"type": "text", "text": "…"}]}

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://www.hackshop.dev/mcp