Skip to main content
Glama
pitkonst

@whatic/mcp

by pitkonst
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to @whatic/mcp

No user-submitted related servers found.

    Related Servers

    • szlcsc-mcp

      zhr1008
      A
      license
      B
      quality
      A
      maintenance
      MCP server for LCSC China (szlcsc.com) enabling component search, parametric filtering, price/stock lookup, datasheet downloads, and EDA asset conversion to Altium formats with local library management.
      2
      25
      MIT

    • local-stdio-mcp

      huandao-gonglu
      F
      license
      Not graded
      quality
      D
      maintenance
      A minimal and extensible local MCP server that provides core utilities like ping and echo alongside a file search tool integrated with the Everything CLI. It enables fast local file searching and service testing through a standardized stdio transport layer.
      -

    • jlcpcb-mcp

      Eyalm321
      A
      license
      A
      quality
      C
      maintenance
      MCP server for JLCPCB/LCSC component search, live stock and pricing, datasheets, and PCB/3D printing ordering via authenticated API.
      28
      1
      MIT

    • grok-mcp

      dq52099
      F
      license
      Not graded
      quality
      C
      maintenance
      MCP server providing web search, news search, and X/Twitter search capabilities via HTTP or stdio.
      -

    • awesome-mcp-tools-mcp

      adw0rd
      A
      license
      A
      quality
      F
      maintenance
      Search and explore a catalog of 2,000+ MCP servers — full-text search, trending, hot, categories, and side-by-side comparison — from any MCP client. A zero-dependency stdio bridge over the hosted awesome-mcp.tools endpoint.
      8
      12 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.2/5.0

    Scored across 7 tools

    Disambiguation4/5

    find_parts, get_specs, compare_parts, and get_image are clearly distinct, while search, lookup, and get_segments overlap in the retrieval workflow but have explicit descriptions that differentiate triage, fused retrieval, and ref expansion. Minor boundary ambiguity remains between get_specs and lookup, but the descriptions provide enough guidance.

    Naming Consistency4/5

    Most tools follow a predictable verb_noun pattern: find_parts, get_specs, compare_parts, get_segments, get_image. The bare-verb names search and lookup are minor deviations that remain readable and do not obscure their purpose.

    Tool Count5/5

    Seven tools form a well-scoped toolkit for IC parametric discovery and datasheet retrieval. Each tool earns its place by covering a distinct step in the workflow without unnecessary duplication or bloat.

    Completeness5/5

    The toolset covers the full read-only datasheet research lifecycle: parametric discovery, normalized spec lookup, distributor comparison, corpus search, full segment retrieval, and figure extraction. There are no obvious dead ends or missing operations for the stated domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources