mcpbeat

Whatic IC Datasheets MCP Server

io.whatic/datasheets
answering

Whatic IC Datasheets is answering right now. Last checked 13 min ago. It exposes 7 tools.

IC datasheet search: parametric part finding, spec lookup, price comparison — grounded in real PDFs.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
154 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 13 min ago.

run in your terminal
claude mcp add datasheets --transport http https://whatic.io/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "datasheets": {
      "url": "https://whatic.io/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.datasheets]
url = "https://whatic.io/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "datasheets": {
      "url": "https://whatic.io/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "datasheets": {
      "url": "https://whatic.io/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

compare
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).
get
get
Expand opaque `ref` tokens (from search/lookup) into full datasheet segment content.
image
get_image
Fetch datasheet figure images (PNG/JPEG) for opaque `ref` tokens obtained from search/lookup/get. Returns each image plus its caption/description/page metadata. Only `type='image'` segments have image data.
lookup
lookup
One-shot spec/section retrieval: full content of the most relevant datasheet segments for one or more parts (fuses search+get). Already groups results per part (via `parts`), so prefer `lookup` over `search` when you know the part(s).
parts
find_parts
Shortlist IC part numbers by parametric spec constraints, ranked by how many constraints each part satisfies. Each constraint is {canonical, op: gte|lte|eq|range, value, unit?}. Returns per-constraint pass/fail/unknown. `canonical` MUST be one of the exact names below (case-sensitive): abs_max_current, abs_max_voltage, adc_resolution, block_erase_time, breakdown_voltage_ds, channel_count, clamping_voltage, clock_frequency, cmrr, cmti, coil_power, coil_resistance, coil_voltage, collector_emitter_voltage, contact_current, contact_resistance, core_size, cpu_speed, current_rating, dark_current, data_rate, data_retention, dc_resistance, drain_current, driver_count, dropout_voltage, dynamic_range, eeprom_size, emitter_base_voltage, fall_time, forward_current, forward_voltage, gain_bandwidth, gate_charge, impedance, input_bias_current, input_capacitance, input_offset_current, input_offset_current_drift, input_offset_voltage, input_offset_voltage_drift, input_voltage_noise_density, insertion_loss, io_count, isolation_voltage, junction_capacitance, load_capacitance, memory_size, operate_time, operating_frequency, operating_temperature, output_capacitance, output_count, output_current, output_noise_voltage, output_power, output_voltage, output_voltage_high, output_voltage_low, page_program_time, peak_pulse_current, power_dissipation, program_erase_cycles, program_memory_size, propagation_delay, psrr, quiescent_current, ram_size, rds_on, receiver_count, rectified_current, release_time, response_time, reverse_leakage_current, reverse_recovery_time, reverse_transfer_capacitance, reverse_voltage, rise_time, sample_rate, sensitivity, settling_time, slew_rate, standby_current, supply_voltage_range, switching_frequency, switching_voltage, vgs_threshold, zener_voltage
search
search
Search the datasheet corpus; returns hit records (metadata + snippet, each with an opaque `ref`). Pass a ref list to `get` for 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.
specs
get_specs
Read canonical extracted specs (min/typ/max, unit, conditions) for known IC part numbers. Optionally restrict to specific canonical parameter names.

Endpoints

URLTransportStateLatencyChecked
https://whatic.io/mcp streamable-http answering 184 ms 13 min ago

Whatic IC Datasheets — questions

Answers built from our own checks of this server.

What can Whatic IC Datasheets do?
It exposes 7 tools, read directly from the server on our last check. Among them: compare_parts, find_parts, get, get_image, get_specs, lookup and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
Is Whatic IC Datasheets working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 154 ms. The bar chart above shows every period we have measured.
How do I connect Whatic IC Datasheets?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does Whatic IC Datasheets need an API key?
No. Whatic IC Datasheets completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is Whatic IC Datasheets?
It answers our handshake in 154 ms on average, which is faster than 72% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.