io.whatic/datasheets

Est-ce que io.whatic/datasheets est sûr ?

Au dernier audit MCP Hub, le serveur MCP « io.whatic/datasheets » 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 7 outils

• compare_parts≈ 194 tokens

  Relative price tier, stock posture, and library class for a set of IC part numbers (a ranking from a distributor snapshot, not a live quote).

  Paramètres, retour & exemple (1)

  Paramètres

  • parts · array · requis
    Two or more IC part numbers to rank relatively; needs >=2 priced parts for a verdict.

  Exemple d'appel

  {"name": "compare_parts", "arguments": {"parts": []}}

  Exemple de retour

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

• find_parts≈ 1038 tokens

  Shortlist IC part numbers by parametric spec constraints, ranked by how many constraints each part satisfies, then by headroom past those thresholds, and spread across device families. Each constraint is {canonical, op: gte|lte|eq|range, value, unit?}. Returns per-constraint pass/fail/unknown, plus `matched` (parts meeting EVERY constraint), `ranked` (all parts scored, partial matches included) and `returned` (parts in this response). `truncated` means some qualifying parts are not on this page. When `matched` is 0 every result is a partial match. `canonical` MUST be one of the exact (case-sensitive) names enumerated in this tool's inputSchema, also readable as the whatic://parametric/canonicals resource.

  Paramètres, retour & exemple (2)

  Paramètres

  • top_k · integer · optionnel
    Maximum number of parts to return, best first.
  • constraints · array · requis
    Spec constraints; a part is ranked by how many it satisfies.

  Exemple d'appel

  {"name": "find_parts", "arguments": {"constraints": []}}

  Exemple de retour

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

• get_image≈ 228 tokens

  Fetch datasheet figure images (PNG/JPEG) for opaque `ref` tokens obtained from search/lookup/get_segments. Returns each image plus its caption/description/page metadata. Only `type='image'` segments have image data; a ref that is not one comes back as an error record whose `available_images` lists the document's figures nearest that ref's page and section, closest first.

  Paramètres, retour & exemple (1)

  Paramètres

  • refs · array · requis
    Opaque `ref` tokens (from search/lookup/get_segments) of image segments; non-image segments return an error record.

  Exemple d'appel

  {"name": "get_image", "arguments": {"refs": []}}

  Exemple de retour

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

• get_segments≈ 174 tokens

  Expand opaque `ref` tokens (from search/lookup) into full datasheet segment content.

  Paramètres, retour & exemple (1)

  Paramètres

  • refs · array · requis
    Opaque `ref` tokens from search/lookup hit records, to expand into full segment content.

  Exemple d'appel

  {"name": "get_segments", "arguments": {"refs": []}}

  Exemple de retour

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

• get_specs≈ 338 tokens

  Read canonical extracted specs (min/typ/max, unit, conditions) for known IC part numbers from a pre-extracted parametric index — not from datasheet text. This is the cheapest and most precise source for numeric parameters where it has coverage. Optionally restrict to specific canonical parameter names. A part absent from `results` (with a "No specs found" warning) means no index coverage, not that the datasheet lacks the parameter — fall back to `lookup` for that part.

  Paramètres, retour & exemple (2)

  Paramètres

  • canonicals · ? · optionnel
    Optional: restrict to these canonical parameter names; omit to return all available specs.
  • part_numbers · array · requis
    Exact IC part numbers / MPNs, e.g. ['NE5532', 'LM358']. Family fallback is applied (e.g. TL084CDT -> TL084C).

  Exemple d'appel

  {"name": "get_specs", "arguments": {"part_numbers": []}}

  Exemple de retour

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

• lookup≈ 257 tokens

  One-shot spec/section retrieval: full content of the most relevant datasheet segments for one or more parts (fuses search+get_segments). Already groups results per part (via `parts`), so prefer `lookup` over `search` when you know the part(s).

  Paramètres, retour & exemple (2)

  Paramètres

  • parts · ? · optionnel
    Part numbers to scope and group the retrieval by; results are returned per part.
  • query · string · requis
    What to retrieve, e.g. 'supply voltage' or 'absolute maximum ratings'.

  Exemple d'appel

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

  Exemple de retour

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

• search≈ 344 tokens

  Search the datasheet corpus; returns hit records (metadata + snippet, each with an opaque `ref`). Pass a ref list to `get_segments` for full content. If you already know the part number(s), prefer `lookup` — it fuses this search with `get_segments` in one call and groups full content per part. Use `search` when the part is unknown, or to triage snippets before pulling full content. For part-specific queries, pass scope='device:<MPN>' (e.g. scope='device:NE5532') to restrict hits to that part and avoid cross-part contamination.

  Paramètres, retour & exemple (3)

  Paramètres

  • k · integer · optionnel
    Maximum number of hit records to return.
  • q · string · requis
    Free-text query, e.g. 'input voltage noise density'.
  • scope · ? · optionnel
    Optional filter, e.g. 'device:NE5532', to restrict hits to one part and avoid cross-part matches.

  Exemple d'appel

  {"name": "search", "arguments": {"q": "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://whatic.io/mcp