IC datasheet search: parametric part finding, spec lookup, price comparison — grounded in real PDFs.
Inferred from the transports this listing declares (streamable-http). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Read from a real MCP initialize → tools/list handshake against the declared endpoint. No tool was ever invoked — tools/list is the read-only introspection call the protocol defines for this. It reflects what the server advertised at that moment; a hosted endpoint is not pinned to any version and can change without notice.
https://whatic.io/mcp7 tools · 576msfind_partsShortlist 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…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…
| Parameter | Type | Description |
|---|---|---|
| constraints* | array | Spec constraints; a part is ranked by how many it satisfies. |
| top_k | integer | Maximum number of parts to return, best first. |
get_specsRead 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 na…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 na…
| Parameter | Type | Description |
|---|---|---|
| part_numbers* | array | Exact IC part numbers / MPNs, e.g. ['NE5532', 'LM358']. Family fallback is applied (e.g. TL084CDT -> TL084C). |
| canonicals | — | Optional: restrict to these canonical parameter names; omit to return all available specs. |
compare_partsRelative price tier, stock posture, and library class for a set of IC part
numbers (a ranking from a distributor snapshot, not a live quote).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).
| Parameter | Type | Description |
|---|---|---|
| parts* | array | Two or more IC part numbers to rank relatively; needs >=2 priced parts for a verdict. |
searchSearch 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 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…
| Parameter | Type | Description |
|---|---|---|
| q* | string | Free-text query, e.g. 'input voltage noise density'. |
| scope | — | Optional filter, e.g. 'device:NE5532', to restrict hits to one part and avoid cross-part matches. |
| k | integer | Maximum number of hit records to return. |
lookupOne-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).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).
| Parameter | Type | Description |
|---|---|---|
| query* | string | What to retrieve, e.g. 'supply voltage' or 'absolute maximum ratings'. |
| parts | — | Part numbers to scope and group the retrieval by; results are returned per part. |
get_segmentsExpand opaque `ref` tokens (from search/lookup) into full datasheet segment
content.Expand opaque `ref` tokens (from search/lookup) into full datasheet segment content.
| Parameter | Type | Description |
|---|---|---|
| refs* | array | Opaque `ref` tokens from search/lookup hit records, to expand into full segment content. |
get_imageFetch 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…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…
| Parameter | Type | Description |
|---|---|---|
| refs* | array | Opaque `ref` tokens (from search/lookup/get_segments) of image segments; non-image segments return an error record. |
7 of 7 tools published a description.
Tool names and descriptions are written by the publisher and shown verbatim as inert text. They are the strings an MCP client passes to a model, so Forge scans them for prompt-injection patterns — any finding appears with the security scan above. “Privileged” is a keyword match on the tool name, not an audit of what the tool does: a benign-sounding name can still do anything.
IC datasheet search: parametric part finding, spec lookup, price comparison — grounded in real PDFs.
Linked names open Forge’s index of every entry observed exposing that tool. Browse all indexed tools.
This entry publishes no npm package, so Forge has no dependency tree for it. That is a gap in coverage — not a statement that it has no dependencies.