openisd-mcp
Related Servers
Alternatives to openisd-mcp
No user-submitted related servers found.
Related Servers
- AlicenseBqualityAmaintenanceEnables AI agents to turn natural-language hardware prompts into deterministic schematics and netlists, query live LCSC parts data, validate designs, calculate trace impedance, and estimate PCBA BOM costs through stdio MCP tools and resources.80981 PyPI1MIT
- AlicenseAqualityAmaintenanceProvides AI agents with instant, structured access to electronic component datasheets, pinouts, and electrical specifications without requiring PDF uploads. It enables seamless part searching, design validation, and side-by-side component comparisons across major hardware providers.14153 npm13MIT
- AlicenseAqualityDmaintenanceEnables AI agents to perform unit-aware engineering calculations with automatic unit conversion, dependency resolution, and access to 500+ units across 75+ categories through the CalcsLive calculation engine.314 npmMIT

TiresVote MCPofficial
AlicenseAqualityBmaintenanceEnables agents to search a public tire catalog and professional tire test data — finding tire models, checking their known size variants, comparing 2-4 models, and collecting cited test results — through 12 read-only tools and four workflow prompts over stdio.12MIT- AlicenseNot gradedqualityBmaintenanceSpacecraft component specifications read from vendor datasheets (2,500+ products, 24 categories): search by engineering requirements, compare, budget mass and power, read datasheet digests and facts, find data gaps, and assemble a bus around parts you lock. Every value cites its datasheet page; missing data is named, never guessed.11 npm1MIT
- AlicenseNot gradedqualityDmaintenanceProvides audio inspection, conversion, processing, and generation capabilities via SoX, enabling AI agents to 'hear' and manipulate audio files through structured JSON interfaces.MIT
TDQS
Scored across 6 tools
Each tool has a clearly distinct purpose: searching, loading, designing, simulating, adding, and evaluating. There is no overlap or ambiguity in what each tool does.
Most tools follow a verb_noun pattern (e.g., search_drivers, get_driver, design_box, add_driver, evaluate_design). The single exception is 'simulate', which is a bare verb but still clear and consistent in style.
Six tools cover the core workflow of speaker design (search, load, design, simulate, add, evaluate) without bloat. Each tool earns its place and the set feels well-scoped for the server's purpose.
The surface covers the main lifecycle: discovery, loading, design creation, simulation, custom additions, and full evaluation. Minor gaps exist (e.g., no update or delete for drivers), but these are non-essential and the core domain is well covered.