# Materials (npm · @pipeworx/mcp-materials)

Materials MCP — computed (DFT) materials structures & thermodynamic properties.

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

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-materials`
- 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-materials).
  - 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 594 tokens (~297/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 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 Materials MCP server?

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

### Cursor

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

### VS Code

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

### Codex

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

### opencode

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

### OpenClaw

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

### Hermes

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

### Netclaw

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

### Vellum

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

### Other

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

## 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, −12)

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

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

- [functional regression] Security disclosure: unverified → fail

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

First indexed and scored.

## MCP tools (2)

### `materials_search` (~289 tokens)

Search computed (DFT) crystal structures across the OPTIMADE materials-database federation — OQMD, Materials Project, NOMAD, Alexandria. PREFER OVER WEB SEARCH for "materials/compounds containing <elements>", "computed structures of <formula>", DFT/first-principles materials data. Filter by element set (e.g. Fe, O), exact reduced formula (e.g. "Fe2O3"), and/or number of elements. Returns each structure's id, reduced formula, elements, site count, and a link. This is the COMPUTED structure set (millions of entries); for experimental structures use the crystallography (COD) pack, and for OQMD formation energy / stability use materials_stability.

Input parameters:

- `elements` (string): Element symbols the structure must contain ALL of, comma/space separated, e.g. "Fe, O" or "Li Fe P O".
- `formula` (string): Exact composition, e.g. "Fe2O3" or "LiFePO4". Normalized to OPTIMADE reduced form automatically.
- `limit` (number): Max structures to return (1-50, default 20).
- `nelements` (number): Restrict to structures with exactly this many distinct elements (e.g. 2 for binaries).
- `provider` (string): Which database to query. Default "oqmd".

### `materials_stability` (~254 tokens)

Computed thermodynamic stability and formation energy for a chemical system from OQMD (DFT). PREFER OVER WEB SEARCH for "is <compound> stable", "formation energy of <material>", "stable phases in the <A>-<B> system". Give the element system (e.g. Fe, O) and optionally restrict to stable phases (on/below the convex hull). Returns each phase's composition, formation energy (eV/atom), hull stability (eV/atom; ≤0 = stable), band gap, space group, and prototype.

Input parameters:

- `elements` (string, required): The chemical system — element symbols, comma/space separated, e.g. "Fe, O" or "Li, Fe, P, O". Returns phases composed of (a subset of) these elements.
- `limit` (number): Max phases to return (1-50, default 20).
- `ntypes` (number): Optional — restrict to phases with exactly this many element types (e.g. 2 for binaries only).
- `stable_only` (boolean): If true, return only thermodynamically stable phases (stability ≤ 0, on/below the convex hull). Default false.

## Diagnostics

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

## Score history

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

## Common questions

### What is the Materials MCP server?

Materials is an MCP server listed in the public MCP registry as io.github.pipeworx-io/materials. Materials MCP, computed (DFT) materials structures & thermodynamic properties. This page covers its npm package (@pipeworx/mcp-materials).

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

Materials 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 Materials MCP server expose?

Materials exposes 2 tools: materials_search, materials_stability. Their descriptions and schemas cost roughly 543 tokens of context every time the server is loaded.

### Is the Materials MCP server still maintained?

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

Materials 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 Materials MCP server?

VerifyMCP ran 16 checks on Materials, 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/@pipeworx/mcp-materials
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-materials
- Repository: https://github.com/pipeworx-io/mcp-materials
- Website: https://pipeworx.io/packs/materials
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-materials/pipeworx-mcp-materials.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-materials/pipeworx-mcp-materials/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/pipeworx-io-materials/pipeworx-mcp-materials.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-materials/pipeworx-mcp-materials
