# io.github.mrfentmen/digikey-mcp (npm · digikey-mcp)

MCP server for Digi-Key: component search, pr MCP: real tools for real work.

- Trust score: 71/100 (medium)
- Change this week: +6
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- npm · `digikey-mcp`: 71/100 (this document), [markdown](https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp.md), [page](https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp)

## Channel facts

- Registry: `npm`
- Package: `digikey-mcp`
- Version: `1.0.0`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-11-21.

- **Supply Chain Security**: 81/100
  - No malware found by supply-chain analysis.
  - CVE check failed: a known high-severity CVE affects zod 3.25.76, a direct dependency. A fixed version is available.
  - No install/post-install scripts declared.
  - 31 of 93 dependencies flagged as unhealthy.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 19 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 550 tokens (~55/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 43/100
  - Stability observed for 13 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 10 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 10 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the io.github.mrfentmen/digikey-mcp server?

io.github.mrfentmen/digikey-mcp runs locally as an npm package, launched with npx -y digikey-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add mrfentmen-digikey-mcp -- npx -y digikey-mcp
```

### Cursor

```json
{
  "mcpServers": {
    "mrfentmen-digikey-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "digikey-mcp"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "mrfentmen-digikey-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "digikey-mcp"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add mrfentmen-digikey-mcp -- npx -y digikey-mcp
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "mrfentmen-digikey-mcp": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "digikey-mcp"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add mrfentmen-digikey-mcp --command npx --arg -y --arg digikey-mcp
```

### Hermes

```yaml
mcp_servers:
  mrfentmen-digikey-mcp:
    command: "npx"
    args: ["-y", "digikey-mcp"]
```

### Netclaw

```json
{
  "McpServers": {
    "mrfentmen-digikey-mcp": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "digikey-mcp"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add mrfentmen-digikey-mcp -t stdio -c npx -a -y digikey-mcp
```

### Other

```json
{
  "mcpServers": {
    "mrfentmen-digikey-mcp": {
      "command": "npx",
      "args": [
        "-y",
        "digikey-mcp"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-11-20 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-18 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-16 (score 69, +4)

- [functional improvement] Stability: unverified → 0.27

### 2026-11-08 (score 65)

First indexed and scored.

## MCP tools (10)

### `search_keywords` (~85 tokens)

Search the Digi-Key catalogue by keyword (part number, description, series). Prices are in the customer currency of the account that owns DIGIKEY_CLIENT_ID.

Input parameters:

- `keywords` (string, required): Search terms, e.g. 'lm358 op-amp soic'
- `limit` (integer): Results to return (max 50)
- `offset` (integer): Results to skip

### `search_by_mpn` (~58 tokens)

Look up a single manufacturer part number precisely. Use this when you already know the MPN and want that exact part rather than a keyword match.

Input parameters:

- `mpn` (string, required): Manufacturer part number, e.g. 'LM358P'

### `get_product_details` (~57 tokens)

Full details for one part: description, category, status, package variations and datasheet link.

Input parameters:

- `productNumber` (string, required): Digi-Key part number or manufacturer part number, e.g. 'Z100' or 'LM358P'

### `get_pricing` (~56 tokens)

Price breaks and stock levels for one part. Prices are in the account's customer currency.

Input parameters:

- `productNumber` (string, required): Digi-Key part number or manufacturer part number, e.g. 'Z100' or 'LM358P'

### `get_quantity_pricing` (~73 tokens)

Price a specific order quantity for one part, so you see the tier that applies to that quantity.

Input parameters:

- `productNumber` (string, required): Digi-Key part number or manufacturer part number, e.g. 'Z100' or 'LM358P'
- `quantity` (integer, required): How many units you intend to buy

### `get_availability` (~53 tokens)

Stock and lead-time summary for one part, without the full price table.

Input parameters:

- `productNumber` (string, required): Digi-Key part number or manufacturer part number, e.g. 'Z100' or 'LM358P'

### `get_associated_products` (~57 tokens)

Related parts Digi-Key lists for a product, e.g. accessories, kits and substitutes.

Input parameters:

- `productNumber` (string, required): Digi-Key part number or manufacturer part number, e.g. 'Z100' or 'LM358P'

### `get_media` (~47 tokens)

Images, videos and other media for one part.

Input parameters:

- `productNumber` (string, required): Digi-Key part number or manufacturer part number, e.g. 'Z100' or 'LM358P'

### `list_categories` (~19 tokens)

Top-level Digi-Key product categories with their child categories.

### `compare_parts` (~45 tokens)

Compare 2-5 parts side by side: MPN, description, category, status and starting price.

Input parameters:

- `productNumbers` (array, required): Two to five part numbers to compare

## Diagnostics

Captured diagnostic sections: Provenance, Vulnerabilities, Dependencies. The full working is on the page: https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp#diagnostics

## Score history

- 2026-11-21: 71
- 2026-11-20: 71
- 2026-11-19: 70
- 2026-11-18: 70
- 2026-11-17: 69
- 2026-11-16: 69
- 2026-11-15: 65
- 2026-11-14: 65
- 2026-11-13: 65
- 2026-11-12: 65
- 2026-11-11: 65
- 2026-11-10: 65
- 2026-11-09: 65
- 2026-11-08: 65

## Common questions

### What is the io.github.mrfentmen/digikey-mcp server?

io.github.mrfentmen/digikey-mcp is listed in the public MCP registry as io.github.mrfentmen/digikey-mcp. MCP server for Digi-Key: component search, pr MCP: real tools for real work. This page covers its npm package (digikey-mcp).

### Is the io.github.mrfentmen/digikey-mcp server safe to use?

io.github.mrfentmen/digikey-mcp scores 71 out of 100 on VerifyMCP. We recorded 1 known advisory against it as of 21 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the io.github.mrfentmen/digikey-mcp server expose?

io.github.mrfentmen/digikey-mcp exposes 10 tools: search_keywords, search_by_mpn, get_product_details, get_pricing, get_quantity_pricing, and 5 more. Their descriptions and schemas cost roughly 550 tokens of context every time the server is loaded.

### Is the io.github.mrfentmen/digikey-mcp server still maintained?

io.github.mrfentmen/digikey-mcp is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the io.github.mrfentmen/digikey-mcp server under?

io.github.mrfentmen/digikey-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

### What did VerifyMCP test on the io.github.mrfentmen/digikey-mcp server?

VerifyMCP ran 16 checks on io.github.mrfentmen/digikey-mcp, covering Malware scan, Known CVEs, Install scripts, Dependency health and 12 more. Endpoint Security and Transport & Reachability do not apply to an npm package, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- npm package: https://www.npmjs.com/package/digikey-mcp
- Socket report: https://socket.dev/npm/package/digikey-mcp
- Repository: https://github.com/mrfentmen/awesome-servers
- Changelog RSS feed: https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp.json
- HTML version of this page: https://verifymcp.io/servers/mrfentmen-digikey-mcp/digikey-mcp
