Skip to content
Whatic logo

Whatic MCP server

Which servers in the official MCP registry are Whatic's own, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-21

← Back to Whatic

Whose server it is
  • Registry nameio.whatic/datasheetsverified in the MCP registry

The registry name sits under whatic.io. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-21
  • Stateanswerschecked 2026-10-21
  • Tools7
  • Server calls itselfwhatic
  • Server version1.28.1
  • Protocol version2025-06-18

On 2026-10-21 the server answered initialize and tools/list without a sign-in. First answer in 169 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.
  • Checked on 4 of the 7 days it takes to judge reliability.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 4, the first on 2026-10-21
  • INITE MCP scoreafter a weeka score needs 7 daily checks: 4 so far
  • Answeredmeasuring4 of the 7 daily checks it takes to print a share
  • Median first answer512 ms
  • Space in an agent's context≈ 2,025 tokensthe definitions of all its tools (7), which an agent carries on every turn
  • Tool definitionsA · 100 of 100
  • Typed results6 of 7 toolsdeclared outputSchema: results come typed, read once
  • Every tool passes all six checks.

What an agent can do with it

  • not sure · Look up cited parametric specs for candidate components
  • not sure · Compare two candidate parts on noise and bandwidth
  • cannot · Calculate inductor sizing and peak currents with a calculator

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

None of the five warning signs in these definitions.

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (30%), doing the product's job (25%), definitions (20%), context (10%) and use (15%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers7 tools · read 2026-10-21
  • find_parts

    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…

  • get_specs

    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…

  • compare_parts

    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).

  • search

    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…

  • lookup

    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…

  • get_segments

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

  • get_image

    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…

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "datasheets": {
      "type": "http",
      "url": "https://whatic.io/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http whatic https://whatic.io/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://whatic.io/mcp as a custom connector in the settings.

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.