# ai.partsgraph/catalog

Search real parts with datasheet-provenance specs, check compatibility and compose priced BOMs.

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 1.4.0
- **Author:** ai.partsgraph
- **License:** Unknown
- **Endpoints:** streamable-http https://partsgraph.ai/api/mcp
- **Source:** https://partsgraph.ai/catalog
- **Endpoint health:** reachable (last checked 2026-10-01T22:55:08.196Z, 5 samples) — uptime is not a security property and is not part of the trust score
- **Compatible clients:** claude-code, cursor, copilot, chatgpt, gemini (basis: transport)

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 0 days

## Security scan

- **Status:** clean
- **Scanned:** 2026-10-01T22:55:08.196Z
- **Version scanned:** live
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

11 declared. Observed from a live `tools/list` probe.
- `search_parts` — Full-text search over the demo catalogue's provenance-backed part records. Filter by category, build or role. Every attribute returned was corroborated against 
- `get_part` — The complete canonical record for one part: every attribute with its provenance (source, page, verbatim quote, file hash), vendors with dated indicative prices,
- `list_categories` — Every category in the catalogue with its part count.
- `list_builds` — The catalogue's reference builds (robot, weather station, plant waterer) with their roles and candidate parts — the starting point for build_bom.
- `check_compatibility` — Evaluates a part set against the build's engineering constraints — supply windows, stall vs peak current, shaft/wheel fit, interfaces, solar chain — with a reas
- `compare_parts` — Aligned attribute-by-attribute comparison of two catalogue parts. Absence means the sources did not state a value — never that the part lacks the property.
- `get_provenance` — The receipt behind a stated value: the verbatim source quote, the page, the extraction method, and the sha-256 of the exact file it was read from — plus a ready
- `build_bom` — Composes a complete BOM for a reference build — quantities, dated indicative prices, per-line rationale, a compatibility verdict for the chosen set, and a CSV e
- `search` — Search the Partsgraph demo catalogue. Returns result ids for fetch. Alias of search_parts shaped to the search/fetch connector contract.
- `fetch` — Fetch the full provenance-backed record for a search result id as a citable document. Alias of get_part shaped to the search/fetch connector contract.
- `view_bom` — Composes the BOM for a reference build and renders it as an interactive view in clients that support MCP Apps. Same data as build_bom.

## Install

**Verdict: review** — Installable, but 2 things to check first: No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
**Cautions** (coverage gaps and advisories — never blocking)
- No CVE coverage: this entry has no npm/PyPI coordinates to query OSV against, so "no known vulnerabilities" is not a claim that can be made about it.
- No publisher has proved control of this listing; it is indexed, not vouched for.
**Config** (claude-code):
```json
"{\n  \"mcpServers\": {\n    \"catalog\": {\n      \"type\": \"http\",\n      \"url\": \"https://partsgraph.ai/api/mcp\"\n    }\n  }\n}"
```

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: runs on someone else's infrastructure; read-only tool surface.
- Floor 9, ceiling 27 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/ai.partsgraph%2Fcatalog
- Install plan: https://forgeregistry.com/api/v1/packages/ai.partsgraph%2Fcatalog/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/ai.partsgraph%2Fcatalog
- HTML page: https://forgeregistry.com/registry/ai.partsgraph%2Fcatalog
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.