# Ieee Standards (npm · @pipeworx/mcp-ieee-standards)

IEEE Xplore MCP — BYOK wrapper over the IEEE Xplore Metadata Search API…

- Trust score: 81/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-ieee-standards/ieee-standards-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-ieee-standards/ieee-standards-mcp)
- npm · `@pipeworx/mcp-ieee-standards`: 81/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-ieee-standards/pipeworx-mcp-ieee-standards.md), [page](https://verifymcp.io/servers/pipeworx-io-ieee-standards/pipeworx-mcp-ieee-standards)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-ieee-standards`
- 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-ieee-standards).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 3 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 56/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1371 tokens (~457/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 Ieee Standards MCP server?

Ieee Standards runs locally as an npm package, launched with npx -y @pipeworx/mcp-ieee-standards. 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-ieee-standards -- npx -y @pipeworx/mcp-ieee-standards
```

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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 81, +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-03 (score 80, +16)

- [security improvement] Malware scan: unverified → pass

### 2026-11-02 (score 64, −13)

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

### 2026-10-30 (score 77, 0)

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (3)

### `ieee_standard_search` (~431 tokens)

Search IEEE STANDARDS by number or topic and get each standard's title, abstract/scope, publication year, DOI and IEEE Xplore link. Covers the IEEE standards catalogue: IEEE 802.11 Wi-Fi / wireless LAN, IEEE 802.3 Ethernet, IEEE 1588 PTP precision time protocol, IEEE 1547 distributed energy resource interconnection, IEEE 1149.1 JTAG boundary scan, IEEE 754 floating point, IEEE 802.1AS timing, and the rest. Answers "what does IEEE standard X cover", "which IEEE standard defines Y", "find the IEEE 802.3 ethernet spec", "latest revision of IEEE 1588". Returns metadata plus the abstract; the normative clause text is sold by IEEE, so follow html_url to purchase or access it. Requires your own free IEEE Xplore API key via _apiKey (register an app at developer.ieee.org). Example: ieee_standard_search({ query: "802.11 wireless LAN", limit: 5, _apiKey: "your-ieee-key" }). Example: ieee_standard_search({ query: "1588 precision time protocol", year: 2019, _apiKey: "your-ieee-key" })

Input parameters:

- `_apiKey` (string, required): Your IEEE Xplore Metadata API key, sent as the `apikey` query param. Free — register an app at https://developer.ieee.org. Approval can take a few business days, and a new key stays inactive until IE…
- `limit` (number): Max standards to return (default 10, max 50).
- `query` (string, required): Standard number and/or topic keywords, e.g. "802.11 wireless LAN", "1588 precision time protocol", "802.3 ethernet", "1547 distributed energy resources", "754 floating point arithmetic".
- `start_record` (number): 1-based offset for paging through a large result set (default 1).
- `year` (number): Restrict to standards published in this year, e.g. 2020 (optional).

### `ieee_search` (~549 tokens)

Search the FULL IEEE Xplore corpus — IEEE and IET journal articles, conference proceedings, magazines, books, courses and standards — returning title, authors, abstract, publication venue, year, DOI and the IEEE Xplore link. The broad engineering / computer-science research tool: IEEE paper search, engineering research paper lookup, conference proceedings search, literature review on a technical topic, tracking one author's IEEE publications. Set content_type to focus on a single kind of record ("Conferences", "Journals", "Standards", "Magazines", "Books", "Courses", "Early Access"), or omit it to search every type at once. Returns metadata plus the abstract; the full text is sold by IEEE, so follow html_url to purchase or read it under an institutional subscription. Requires your own free IEEE Xplore API key via _apiKey (register an app at developer.ieee.org). Example: ieee_search({ query: "federated learning edge devices", limit: 10, _apiKey: "your-ieee-key" }). Example: ieee_search({ query: "millimeter wave beamforming", content_type: "Conferences", year: 2024, _apiKey: "your-ieee-key" })

Input parameters:

- `_apiKey` (string, required): Your IEEE Xplore Metadata API key, sent as the `apikey` query param. Free — register an app at https://developer.ieee.org.
- `author` (string): Restrict to an author name, e.g. "Yoshua Bengio" (optional).
- `content_type` (string): Restrict to one IEEE content type (optional). Omit to search every content type at once.
- `index_terms` (string): Restrict to an IEEE or author index term, e.g. "Deep learning" (optional).
- `limit` (number): Max records to return (default 10, max 50).
- `publication_title` (string): Restrict to a journal or proceedings title, e.g. "IEEE Transactions on Antennas and Propagation" (optional).
- `query` (string, required): Free-text search across IEEE metadata (title, abstract, index terms), e.g. "federated learning edge devices", "lithium-ion battery state of charge estimation".
- `sort_by` (string): Sort field (default relevance).
- `sort_order` (string): Sort direction (default desc when sorting by publication_year, asc otherwise).
- `start_record` (number): 1-based offset for paging through a large result set (default 1).
- `year` (number): Restrict to this publication year, e.g. 2024 (optional).

### `ieee_article` (~334 tokens)

Fetch one IEEE Xplore record by its article_number or DOI: full metadata including title, every author with affiliation, the complete abstract, publication venue, year, volume/issue, page range, publisher, IEEE and author index terms, plus standard_number and standard_status when the record is a standard, and the Xplore html_url / pdf_url. Use it to expand a hit from ieee_search or ieee_standard_search, or when an agent already holds an IEEE DOI or article number. Returns metadata plus the abstract; the full text is sold by IEEE — html_url is where to purchase or access it. Requires your own free IEEE Xplore API key via _apiKey (register an app at developer.ieee.org). Example: ieee_article({ article_number: "8766229", _apiKey: "your-ieee-key" }). Example: ieee_article({ doi: "10.1109/IEEESTD.2020.9363693", _apiKey: "your-ieee-key" })

Input parameters:

- `_apiKey` (string, required): Your IEEE Xplore Metadata API key, sent as the `apikey` query param. Free — register an app at https://developer.ieee.org.
- `article_number` (string): IEEE Xplore article number — the numeric id in an ieeexplore.ieee.org/document/<n> URL, e.g. "8766229". Supply this or `doi`.
- `doi` (string): DOI of the record, e.g. "10.1109/IEEESTD.2020.9363693". Supply this or `article_number`.

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 80
- 2026-11-03: 80
- 2026-11-02: 64
- 2026-11-01: 77
- 2026-10-31: 77
- 2026-10-30: 77
- 2026-10-29: 77

## Common questions

### What is the Ieee Standards MCP server?

Ieee Standards is an MCP server listed in the public MCP registry as io.github.pipeworx-io/ieee-standards. IEEE Xplore MCP, BYOK wrapper over the IEEE Xplore Metadata Search API… This page covers its npm package (@pipeworx/mcp-ieee-standards).

### Is the Ieee Standards MCP server safe to use?

Ieee Standards scores 81 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 Ieee Standards MCP server expose?

Ieee Standards exposes 3 tools: ieee_standard_search, ieee_search, ieee_article. Their descriptions and schemas cost roughly 1,314 tokens of context every time the server is loaded.

### Is the Ieee Standards MCP server still maintained?

Ieee Standards 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 Ieee Standards MCP server under?

Ieee Standards 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-ieee-standards
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-ieee-standards
- Repository: https://github.com/pipeworx-io/mcp-ieee-standards
- Website: https://pipeworx.io/packs/ieee-standards
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-ieee-standards/pipeworx-mcp-ieee-standards.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-ieee-standards/pipeworx-mcp-ieee-standards.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-ieee-standards/pipeworx-mcp-ieee-standards