# Octopart (npm · @pipeworx/mcp-octopart)

Octopart MCP — electronic component search via the Nexar Supply API (GraphQL)

- Trust score: 82/100 (high trust)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-octopart/octopart-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-octopart/octopart-mcp)
- npm · `@pipeworx/mcp-octopart`: 82/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-octopart/pipeworx-mcp-octopart.md), [page](https://verifymcp.io/servers/pipeworx-io-octopart/pipeworx-mcp-octopart)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-octopart`
- Version: `0.2.1`
- 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-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-octopart).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 1 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 703 tokens (~234/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Octopart MCP server?

Octopart runs locally as an npm package, launched with npx -y @pipeworx/mcp-octopart. 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 pipeworx-io-octopart -- npx -y @pipeworx/mcp-octopart
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-octopart": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-octopart"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-octopart": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-octopart"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-octopart -- npx -y @pipeworx/mcp-octopart
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add pipeworx-io-octopart --command npx --arg -y --arg @pipeworx/mcp-octopart
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-octopart:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-octopart"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-octopart": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-octopart"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-octopart -t stdio -c npx -a -y @pipeworx/mcp-octopart
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-octopart": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-octopart"
      ]
    }
  }
}
```

## 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-05 (score 82, +1)

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

### 2026-11-04 (score 81, +15)

- [security improvement] Malware scan: unverified → pass

### 2026-11-03 (score 66, −14)

- [security regression] Malware scan: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-11-01 (score 80, +1)

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

### 2026-10-30 (score 79, +1)

- [functional regression] Security disclosure: unverified → fail

### 2026-10-29 (score 78)

First indexed and scored.

## MCP tools (3)

### `octopart_search` (~232 tokens)

Search Octopart for electronic components by manufacturer part number (MPN) or keyword. Returns matching parts with manufacturer, category, median price, total availability, and distributor offers (stock, price breaks, MOQ, lead time). Example: octopart_search({ q: "STM32F407", limit: 5, _apiKey: "client_id:client_secret" })

Input parameters:

- `_apiKey` (string, required): Nexar OAuth2 credentials as "client_id:client_secret". Get a free key ("Welcome 1K" plan) at https://portal.nexar.com
- `country` (string): ISO country code for pricing/availability context, e.g. "US" (optional)
- `currency` (string): ISO currency code for converted prices, e.g. "USD" (optional)
- `limit` (number): Max number of parts to return (default 5, max 20)
- `q` (string, required): Manufacturer part number or keyword, e.g. "STM32F407VGT6", "0.1uF 0603 capacitor"

### `octopart_multi_match` (~226 tokens)

Batch-match a list of manufacturer part numbers in one call — ideal for BOM (bill of materials) enrichment. Each query resolves to the best-matching part(s) with distributor offers. Example: octopart_multi_match({ mpns: ["SY89832UMG", "SY89874UMG"], limit: 1, _apiKey: "client_id:client_secret" })

Input parameters:

- `_apiKey` (string, required): Nexar OAuth2 credentials as "client_id:client_secret". Get one at https://portal.nexar.com
- `country` (string): ISO country code for pricing/availability context, e.g. "US" (optional)
- `currency` (string): ISO currency code for converted prices, e.g. "USD" (optional)
- `limit` (number): Max parts to return per MPN (default 1)
- `mpns` (array, required): List of manufacturer part numbers to match (exact-match), e.g. ["SY89832UMG", "GRM188R71C104KA01D"]

### `octopart_part` (~190 tokens)

Get full detail for a single electronic part by exact MPN: every distributor seller with offers (price breaks, inventory level, MOQ, factory lead time), technical specs, availability, datasheet URL, and Octopart page. Example: octopart_part({ mpn: "LM317T", _apiKey: "client_id:client_secret" })

Input parameters:

- `_apiKey` (string, required): Nexar OAuth2 credentials as "client_id:client_secret". Get one at https://portal.nexar.com
- `country` (string): ISO country code for pricing/availability context, e.g. "US" (optional)
- `currency` (string): ISO currency code for converted prices, e.g. "USD" (optional)
- `mpn` (string, required): Exact manufacturer part number, e.g. "LM317T", "ATMEGA328P-PU"

## Diagnostics

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

## Score history

- 2026-11-05: 82
- 2026-11-04: 81
- 2026-11-03: 66
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78

## Common questions

### What is the Octopart MCP server?

Octopart is an MCP server listed in the public MCP registry as io.github.pipeworx-io/octopart. Octopart MCP, electronic component search via the Nexar Supply API (GraphQL). This page covers its npm package (@pipeworx/mcp-octopart).

### Is the Octopart MCP server safe to use?

Octopart scores 82 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Octopart MCP server expose?

Octopart exposes 3 tools: octopart_search, octopart_multi_match, octopart_part. Their descriptions and schemas cost roughly 648 tokens of context every time the server is loaded.

### Is the Octopart MCP server still maintained?

Octopart is still listed as active in the MCP registry. We last reached this channel on 5 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 Octopart MCP server under?

Octopart declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-octopart
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-octopart
- Repository: https://github.com/pipeworx-io/mcp-octopart
- Website: https://pipeworx.io/packs/octopart
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-octopart/pipeworx-mcp-octopart.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-octopart/pipeworx-mcp-octopart.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-octopart/pipeworx-mcp-octopart