Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Ieee Standards

NPM · @PIPEWORX/MCP-IEEE-STANDARDS · 2 COMPONENTS

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

80 Trust /100

Last scanned (20 hours ago)

Scores higher than 65% of npm servers

Category Education and Research

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Supply Chain Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • No install/post-install scripts declared.Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-ieee-standards). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 2 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability56
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
  • Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 3 Nov 26 +16
    • Malware scan: unverified → pass ▲ security
  • 2 Nov 26 −13
    • Malware scan: pass → unverified ▼ security
    • Stability: unverified → 0.13 ▲ functional
    • Package version: 0.2.0 → 0.2.1 functional
  • 30 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 29 Oct 26 77

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 4 Nov 2026 · Analysed npm/@pipeworx/mcp-ieee-standards@0.2.1

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem npm
Reason Verified
Discovered via Registry attestation endpoint
Source repo pipeworx-io/mcp-ieee-standards
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-ieee-standards/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3637410652
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:d76c5139890aa71c495446f70dfd66b4b6a5700256356ad6bd6ad35ec961b42e1845de651354a403ea9d38d5fd219c023c381536d18e746f84578221f

Background: How many MCP packages publish verified provenance →

Dependencies 0 packages
Packages resolved 0
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools · 3 exposed · ~1,314 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
ieee_article ~334

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" })

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

No output schema declared.

No examples provided.

ieee_search ~549

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" })

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

No output schema declared.

No examples provided.

ieee_standard_search ~431

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" })

NameTypeReqDescription
_apiKeystringyesYour 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…
limitnumber–Max standards to return (default 10, max 50).
querystringyesStandard 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_recordnumber–1-based offset for paging through a large result set (default 1).
yearnumber–Restrict to standards published in this year, e.g. 2020 (optional).

No output schema declared.

No examples provided.

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.

npm · @pipeworx/mcp-ieee-standards

# add to Claude Code
claude mcp add pipeworx-io-ieee-standards -- npx -y @pipeworx/mcp-ieee-standards
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 80 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 4 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 4 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.