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.

Crystallography

NPM · @PIPEWORX/MCP-CRYSTALLOGRAPHY · 2 COMPONENTS

Crystallography Open Database (COD) MCP.

+3 this week 83 Trust /100

Last scanned (5 hours ago)

Scores higher than 76% of npm servers

Category Health and Science

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-crystallography). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 4 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability68
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 625 tokens (~208/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 Management23
  • Stability observed for 7 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.

  • 5 Nov 26 +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.

  • 3 Nov 26 +1

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

  • 1 Nov 26 +26
    • Known CVEs: unverified → pass ▲ security
    • Malware scan: unverified → pass ▲ security
    • Dependency health: unverified → pass ▲ functional
  • 31 Oct 26 −25
    • Known CVEs: pass → unverified ▼ security
    • Malware scan: pass → unverified ▼ security
    • Dependency health: pass → unverified ▼ functional
    • Package version: 0.3.0 → 0.3.1 functional
  • 29 Oct 26 80

    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 5 Nov 2026 · Analysed npm/@pipeworx/mcp-crystallography@0.3.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-crystallography
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/pipeworx-io/mcp-crystallography/.github/workflows/publish.yml@refs/heads/main
Rekor log index 3612314340
Predicate type SLSA build provenance https://slsa.dev/provenance/v1
Subject digest sha512:760d8ce030426f9b3b0d32aadc4256fa9b1ffb155615023808fb24cd7dce7cb2ec225ec21d7362d00341805db3308ca3ef31bb1bbf0f7b4326328f5f2

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 · ~572 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
get_cif ~116

Fetch the full CIF (Crystallographic Information File) for a COD structure by its numeric COD ID — the actual machine-readable structure: symmetry operations and the atom sites (element, fractional x/y/z coordinates, occupancy). Use after search_structures/get_structure when you need the real atomic structure, not just the metadata/link. Returns the CIF text plus a parsed summary (formula, space group, cell, atom count). Keyless.

NameTypeReqDescription
cod_idstringyesCOD numeric structure id, e.g. "1009000".

No output schema declared.

No examples provided.

get_structure ~116

Look up a single crystal structure in the Crystallography Open Database (COD) by its numeric COD ID (e.g. "1009000"). Returns the compound/mineral name, chemical formula, space group, full unit-cell parameters (a, b, c, alpha, beta, gamma, volume), bibliographic details (title, authors, journal, year, DOI), and a link to the CIF structure file. Keyless.

NameTypeReqDescription
cod_idstringyesCOD numeric structure id, e.g. "1009000".

No output schema declared.

No examples provided.

search_structures ~340

Search the Crystallography Open Database (COD), an open repository of crystal structures (inorganic, organic, metal-organic, and mineral). Search by compound name (free text), chemical formula, or mineral name; returns matching crystal structures with unit-cell parameters, space group, year, and a link to the CIF structure file. Keyless. Provide at least one of query, formula, or mineral. Formulas are normalized to COD's stored Hill notation for you, so "NaCl", "SiO2" and "CaCO3" all work; the response reports `formula_searched` with the exact string that was matched.

NameTypeReqDescription
formulastring–Chemical formula in any common spelling — "NaCl", "SiO2", "CaCO3", "C6H6", or COD's own "O2 Si". It is converted to COD's stored Hill form (C first, then H, then the rest alphabetically; counts of 1…
limitnumber–Max structures to return (default 20, max 100).
mineralstring–Mineral name, e.g. "Quartz", "Calcite", "Halite". Matched against each structure's mineral field (case-insensitive substring), so "Quartz" also returns "Quartz low" / "Quartz high".
querystring–Free-text search (compound/common name, title words, author, etc.). e.g. "quartz", "aspirin".

No output schema declared.

No examples provided.

Install

How do I install the Crystallography MCP server?

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

# add to Claude Code
claude mcp add pipeworx-io-crystallography -- npx -y @pipeworx/mcp-crystallography
Common questions

What is the Crystallography MCP server?

Crystallography is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crystallography. Crystallography Open Database (COD) MCP. This page covers its npm package (@pipeworx/mcp-crystallography).

Is the Crystallography MCP server safe to use?

Crystallography scores 83 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 Crystallography MCP server expose?

Crystallography exposes 3 tools: search_structures, get_structure, get_cif. Their descriptions and schemas cost roughly 572 tokens of context every time the server is loaded.

Is the Crystallography MCP server still maintained?

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

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