Whatic IC Datasheets
REMOTE · WHATIC.IO · SCANNED OCT 4
IC datasheet search: parametric part finding, spec lookup, price comparison — grounded in real PDFs.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →
Endpoint Security74
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability43
- 0% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Fail
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 1291 tokens (~161/item across 8 items; 7 tools + 1 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
- Structured output schemas are declared (86% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the Whatic IC Datasheets MCP server?
Whatic IC Datasheets is a hosted endpoint at https://whatic.io/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · whatic.io
claude mcp add --transport http io-whatic-datasheets 'https://whatic.io/mcp'
{
"mcpServers": {
"io-whatic-datasheets": {
"url": "https://whatic.io/mcp"
}
}
} {
"servers": {
"io-whatic-datasheets": {
"type": "http",
"url": "https://whatic.io/mcp"
}
}
} [mcp_servers.io-whatic-datasheets] url = "https://whatic.io/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"io-whatic-datasheets": {
"type": "remote",
"url": "https://whatic.io/mcp",
"enabled": true
}
}
} openclaw mcp add io-whatic-datasheets --url 'https://whatic.io/mcp' --transport streamable-http
mcp_servers:
io-whatic-datasheets:
url: "https://whatic.io/mcp" {
"McpServers": {
"io-whatic-datasheets": {
"Transport": "http",
"Url": "https://whatic.io/mcp"
}
}
} assistant mcp add io-whatic-datasheets -t streamable-http -u 'https://whatic.io/mcp'
{
"mcpServers": {
"io-whatic-datasheets": {
"type": "http",
"url": "https://whatic.io/mcp"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 +2
- Stability: fail → pass ▲ security
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +7
- Authorization: unverified → partial ▲ security
- The server rewrote its instructions, which are the text every model session reads security
- Tool “find_parts” rewrote its description, which is the text the model reads security
- Tool “compare_parts” changed its title: Compare IC cost and availability cosmetic
- Tool “find_parts” changed its title: Shortlist ICs by spec cosmetic
- Tool “get_image” changed its title: Fetch datasheet figures cosmetic
- Tool “get_segments” changed its title: Expand datasheet refs cosmetic
- Tool “get_specs” changed its title: Read IC specs cosmetic
- Tool “lookup” changed its title: Look up datasheet sections cosmetic
- Tool “search” changed its title: Search datasheets cosmetic
- 28 Aug 26 0
- Stability: pass → fail ▼ security
- A breaking change shipped without a version bump: still 1.28.1 ▼ security
- Tool “get” was removed ▼ security
- Tool “find_parts” rewrote its description, which is the text the model reads security
- Tool “get_image” rewrote its description, which is the text the model reads security
- Tool “get_specs” rewrote its description, which is the text the model reads security
- Tool “lookup” rewrote its description, which is the text the model reads security
- Tool “search” rewrote its description, which is the text the model reads security
- Schema quality: 125 → 152 ▼ functional
- New tool “get_segments” functional
- “get_image” reworded the description of “refs” cosmetic
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 18 Aug 26 0
- Tool “find_parts” rewrote its description, which is the text the model reads security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 4 Oct 2026 · Probed https://whatic.io/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=whatic.io | CN=YE2,O=Let's Encrypt,C=US | 26 Sept 2026 | 25 Dec 2026 | ECDSA 256 | ECDSA-SHA384 | 6f3ec7b88f6a90808acc777f3c5ce3ee47b |
| SANs: whatic.io | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of whatic.io. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| io. | present | 57355 | 8 | Verified |
| whatic.io. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://whatic.io/mcp | Verified | 200 | |
| http (plaintext) | http://whatic.io/mcp | HTTPS enforced | 301 | https://whatic.io/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
compare_parts Compare IC cost and availability ~64
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).
| Name | Type | Req | Description |
|---|---|---|---|
| parts | array | yes | Two or more IC part numbers to rank relatively; needs >=2 priced parts for a verdict. |
Structured output declared, but exposes no named fields.
No examples provided.
find_parts Shortlist ICs by spec ~208
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.
| Name | Type | Req | Description |
|---|---|---|---|
| constraints | array | yes | Spec constraints; a part is ranked by how many it satisfies. |
| top_k | integer | – | Maximum number of parts to return, best first. |
Structured output declared, but exposes no named fields.
No examples provided.
get_image Fetch datasheet figures ~124
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.
| Name | Type | Req | Description |
|---|---|---|---|
| refs | array | yes | Opaque `ref` tokens (from search/lookup/get_segments) of image segments; non-image segments return an error record. |
No output schema declared.
No examples provided.
get_segments Expand datasheet refs ~54
Expand opaque `ref` tokens (from search/lookup) into full datasheet segment content.
| Name | Type | Req | Description |
|---|---|---|---|
| refs | array | yes | Opaque `ref` tokens from search/lookup hit records, to expand into full segment content. |
Structured output declared, but exposes no named fields.
No examples provided.
get_specs Read IC specs ~177
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.
| Name | Type | Req | Description |
|---|---|---|---|
| canonicals | – | – | Optional: restrict to these canonical parameter names; omit to return all available specs. |
| part_numbers | array | yes | Exact IC part numbers / MPNs, e.g. ['NE5532', 'LM358']. Family fallback is applied (e.g. TL084CDT -> TL084C). |
Structured output declared, but exposes no named fields.
No examples provided.
lookup Look up datasheet sections ~109
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).
| Name | Type | Req | Description |
|---|---|---|---|
| parts | – | – | Part numbers to scope and group the retrieval by; results are returned per part. |
| query | string | yes | What to retrieve, e.g. 'supply voltage' or 'absolute maximum ratings'. |
Structured output declared, but exposes no named fields.
No examples provided.
search Search datasheets ~196
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.
| Name | Type | Req | Description |
|---|---|---|---|
| k | integer | – | Maximum number of hit records to return. |
| q | string | yes | 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. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Whatic IC Datasheets MCP server?
Whatic IC Datasheets is an MCP server listed in the public MCP registry as io.whatic/datasheets. IC datasheet search: parametric part finding, spec lookup, price comparison, grounded in real PDFs. This page covers its hosted endpoint (https://whatic.io/mcp).
Is the Whatic IC Datasheets MCP server safe to use?
Whatic IC Datasheets scores 79 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the Whatic IC Datasheets MCP server expose?
Whatic IC Datasheets exposes 7 tools: find_parts, get_specs, compare_parts, search, lookup, and 2 more. Their descriptions and schemas cost roughly 932 tokens of context every time the server is loaded.
Does the Whatic IC Datasheets MCP server require authentication?
No. We connected to Whatic IC Datasheets without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Whatic IC Datasheets MCP server still maintained?
Whatic IC Datasheets is still listed as active in the MCP registry. We last reached this channel on 4 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.