150,000+ agents registered. Trust scores show their math.Explore →
Explorer/MCP/sheetsdata/sheetsdata
REMOTE

SheetsData

sheetsdata/sheetsdata

Instant access to electronic component datasheets — specs, pinouts, package info, and more — extracted from manufacturer PDFs. No uploads needed. SheetsData extracts and structures data from thousands of electronic component datasheets so AI agents can look up any part's specifications in seconds. Instead of downloading PDFs and parsing tables manually, just pass a manufacturer part number (MPN) and get back structured electrical characteristics, pin configurations, absolute maximum ratings, and more. ## What you can do - **Find components** — Search across JLCPCB, Mouser, and DigiKey by part number or keyword, with real-time pricing and stock levels - **Read datasheets** — Access any section of a datasheet as structured text: pinout tables, electrical specs, register maps, timing diagrams, application circuits - **Compare parts** — Side-by-side comparison of up to 5 components with specs, pricing, and availability from multiple distributors - **Validate designs** — Check if a component will work within your operating conditions (voltage, current, temperature) against its absolute maximum ratings - **Find alternatives** — Discover substitute components with similar specs, same package, or compatible pinout when a part is unavailable or too expensive - **Analyze images** — Extract data from datasheet graphs, package drawings, and pin diagrams using vision AI ## Tools | Tool | Cost | Description | |------|------|-------------| | `search_parts` | Free | Search components by part number or keyword across JLCPCB, Mouser, and DigiKey | | `search_datasheets` | Free | Semantic search across extracted datasheets (e.g. "low-noise LDO with PSRR above 70dB") | | `prefetch_datasheets` | Free | Batch warm-up extraction for up to 20 parts (fire-and-forget) | | `check_extraction_status` | Free | Poll extraction progress after prefetch or read_datasheet | | `get_part_details` | 4¢ | Full specs, pricing, stock, and datasheet summary for a specific MPN | | `read_datasheet` | 6¢ | Read datasheet sections or semantic search within a datasheet | | `compare_parts` | 10¢ | Side-by-side comparison of 2–5 components | | `check_design_fit` | 10¢ | Validate operating conditions against datasheet limits | | `analyze_image` | 8¢ | Extract data from datasheet graphs, package drawings, and pin diagrams | | `find_alternative` | 10¢ | Find substitute components with similar specs or compatible pinout | ## Recommended workflow 1. `search_parts` to find candidates by keyword or part number 2. `get_part_details` or `compare_parts` to evaluate options 3. `read_datasheet` for detailed specs — start with `section='summary'` to get an overview and discover available sections, then fetch specific sections as needed 4. `check_design_fit` to validate against your design constraints 5. `read_datasheet` with `mode='search'` for any remaining questions about a specific part 6. `analyze_image` when you need data from a graph, package drawing, or pin diagram ## Tips - Use manufacturer part numbers (MPNs) like `TPS54302` or LCSC numbers like `C2837938` — bare values like "100nF" or "10K" are not part numbers - `search_datasheets` is best for broad spec-based discovery (e.g. "LDO with dropout below 200mV and quiescent current under 1uA") - `search_parts` is best for finding a specific part or browsing a category with pricing and stock - First extraction for a new part takes 10–20s as the PDF is downloaded and processed; subsequent calls are cached - Use `prefetch_datasheets` to warm up a batch of parts (e.g. from a BOM) before reading them individually - Prefer requesting specific sections from `read_datasheet` rather than reading everything at once to keep responses focused

10 tools available ↓
The Journeyman
A reasonable amount of history and nothing concerning in the scan.
Time indexed (3mo)
10toolsRemote/ HTTP3moindexed
100% uptime · 348ms avgChecked Jun 15, 2026
Quality Score
63/95
Deep
Risk Score
0/100
Clean
▸How is this calculated?
Quality Breakdown
Tenure12.4/20
93 days indexed
Capability17.3/25
Tools: 5.3/13 (10 tools)
Description: 5/5 ✓
Endpoint: 7/7 ✓
Adoption7.9/25
Use count: 7.9/20 (95 uses)
Multi-registry: 0/5 (1 registry)
Reliability25/25
Currently live: 10/10 ✓
Uptime history: 15/15 100% (45/45 checks)
Security scan: 0 pts in v1.0; ready to weight when coverage improves
Risk
0— Clean
No signals detected.
The scanner shows
10 tools. Nothing caught our attention.
First indexed Mar 19, 2026
Server Profile
⚙
Tools catalogued
10
10 tools available. Full list below.
☁
Hosting
Remote / HTTP
Runs on the internet. No access to your filesystem, SSH keys, or environment variables.
○
Registry presence
Not verified
Not yet verified by the Official MCP Registry.
●
Liveness
100%
Based on 48 checks. Average response: 348ms.
Publisher Verification
Not yet verified by the Official MCP Registry.
Endpoint
https://sheetsdata--sheetsdata.run.tools
Tools (10)
search_parts
Search for electronic components by part number, description, or keyword. Start here — this is the best entry point for finding components. Queries all configured providers in parallel. Results are merged by MPN with indicative pricing and stock from each source. Each result includes datasheet_status ('ready', 'extracting', or 'not_extracted') so you know which parts have datasheets available for read_datasheet. Best with specific part numbers or keywords (e.g. 'STM32F103', 'buck converter 3A'). For spec-based discovery in natural language, use search_datasheets instead.
search_datasheets
Semantic search across all extracted datasheets. Finds components matching natural language queries about specifications, features, or capabilities. Best for broad spec-based discovery across all parts (e.g. 'low-noise LDO with PSRR above 70dB'). Only searches datasheets that have been previously extracted — not all parts that exist. For finding specific parts by number, use search_parts instead.
prefetch_datasheets
Trigger background datasheet extraction for multiple parts at once (up to 20). Free, non-blocking — returns immediately with the status of each part: 'ready' (already extracted), 'queued' (extraction started), or 'error'. Use this to warm up datasheets for a BOM before calling read_datasheet. Example: prefetch_datasheets(['TPS54302', 'ADS1115', 'LP5907']) IMPORTANT — only pass specific manufacturer part numbers (MPNs). Before calling, verify each part number: - Must be a real MPN like 'STM32F446RCT6', 'TPS54302DDCR', 'C100nF' — NOT a description or value. - Do NOT pass bare values like '100nF', '10K', '4.7uF', '300ohm' — these are component values, not part numbers. - Do NOT pass generic descriptions like 'LED red', 'capacitor 100nF', 'resistor 0603'. - Do NOT pass BOM reference designators like 'R1', 'C5', 'U3'. - If the BOM only has values/descriptions without MPNs, use search_parts first to find the actual MPN. - Passives from BOMs often lack MPNs — skip them rather than prefetching a bare value.
check_extraction_status
Check the extraction status of one or more parts. Returns per-part status: 'ready' (datasheet extracted), 'extracting' (in progress), 'pending' (queued), 'failed' (extraction failed), or 'not_extracted' (unknown part). Includes current extraction step, elapsed time, and document ID for tracking. Free — use this to poll progress after prefetch_datasheets or read_datasheet.
get_part_details
Get full details for a specific electronic component by manufacturer part number (MPN) or LCSC number. Returns specs, pricing, and stock from all configured providers, plus the cached datasheet summary if available. Includes datasheet_status ('ready', 'extracting', or 'not_extracted') and available_sections when ready. Set prefetch_datasheet=true to trigger background extraction — no extra charge. Use after search_parts to drill into a specific result. The part_number must be a specific manufacturer part number (e.g. 'TPS54302DDCR', 'STM32F446RCT6') or LCSC number (e.g. 'C2837938'). Do NOT pass bare component values ('100nF', '10K'), descriptions ('buck converter'), or reference designators ('R1', 'U3').
read_datasheet
Read from a component's datasheet. Two modes: **Section mode** (default): Returns a named section. Start with section='summary' to get an overview and a list of available_sections. Then request specific sections by name. Section names are dynamic — any heading in the actual datasheet works (e.g. 'register_map', 'i2c_interface', 'power_management'). If a section name isn't found, automatically falls back to search mode. **Search mode**: Semantic search within the part's datasheet. Best for targeted questions (register bit fields, I2C config, specific specs). Use when you need to find specific information rather than a whole section. First call for a new part triggers extraction (30s-2min). Subsequent calls are cached. The part_number must be a specific manufacturer part number (e.g. 'TPS54302', 'STM32F446RCT6') or LCSC number (e.g. 'C2837938'). Do NOT pass bare component values ('100nF', '10K'), descriptions, or reference designators.
Show all 10 tools ↓
compare_parts
Compare 2-5 electronic components side by side. Returns merged details from all providers and cached datasheet summaries for each part, making it easy to compare specs, pricing, and availability. Includes datasheet_status per part. Example: compare_parts(['TPS54302', 'LM2596', 'MP2359'])
check_design_fit
Validate whether a component will work within your operating conditions. Checks the datasheet's absolute maximum ratings and recommended operating conditions against your design parameters. Returns PASS/FAIL/WARNING per parameter with margins. Example: check_design_fit('TPS54302', input_voltage=24, output_current=2.5, ambient_temp=70)
analyze_image
Analyze an image from a component's datasheet using vision AI. Use this when read_datasheet returns a section containing images and you need to extract data from a graph, package drawing, pin diagram, or circuit schematic. Pass the image_key from the read_datasheet response (the storage path in the image URL). Optionally pass a specific question to focus the analysis. IMPORTANT: For precise numeric values (electrical specs, max ratings), prefer read_datasheet text tables first — they are more reliable than vision-extracted graph data. Use analyze_image for visual information not available in text: package dimensions from drawings, pin assignments from diagrams, graph trends, and approximate values from characteristic curves. Examples: - analyze_image(part_number='IRFZ44N', image_key='images/abc123.png') → classifies and describes the image - analyze_image(part_number='IRFZ44N', image_key='images/abc123.png', question='What is the drain current at Vgs=5V?')
find_alternative
Find alternative/substitute components for a given part number. Searches across providers for parts with similar specs, same package, or compatible pinout. Useful when a part is out of stock, too expensive, or you need a second source. Example: find_alternative('TPS54302', constraints='same_package,in_stock')

Is this your server?

Create a free RNWY account to connect your on-chain identity to this server. MCP server claiming is coming; register now and you'll be first in line.

Create your account →
Similar servers
Press Release
press-release MCP — wraps StupidAPIs (requires X-API-Key)
MCP Server for LimeSurvey
Enables interaction with LimeSurvey API to create and manage surveys, questions, question groups, activate surveys, and export responses through standardized MCP endpoints.
io.github.zenml-io/mcp-zenml
MCP server for ZenML - browse stacks, pipelines, runs, artifacts & trigger pipeline runs via API
Linear
Linear MCP — wraps the Linear GraphQL API (OAuth)
HAPI MCP Server
HAPI MCP server: Dynamically exposes OpenAPI REST APIs as MCP tools for AI assistants
io.github.Vishisht16/humane-proxy
AI safety middleware — detects self-harm and criminal intent in LLM prompts.
Indexed from Smithery · Updates nightlyView on Smithery →