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.

ai.partsgraph/catalog

REMOTE · PARTSGRAPH.AI

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

Available components

0 this week 88 Trust /100

Last scanned (3 hours ago)

Scores higher than 96% of remote servers

Reachable. Last reached 5 Nov 2026.

Category IoT and Hardware

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security80
Transport & Reachability100
Schema Quality & AI Usability83
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 1165 tokens (~72/item across 16 items; 11 tools + 5 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage91
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 69% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 11 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 13 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
  • Supports UI / widget rendering.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.

  • 28 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Sept 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 18 Sept 26 0
    • Stability: 0.97 → pass security
  • 26 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 20 Aug 26 0
    • Tool coverage: 77% → 69% ▼ functional
    • Schema quality: 83 → 72 ▲ functional
    • Stability: unverified → 0.03 ▲ functional
    • First check of Capabilities: pass functional
    • New resource “bom-viewer-app” functional
    • Server version: 1.2.0 → 1.4.0 functional
    • New tool “view_bom” functional
    • New tool “fetch” functional
    • New tool “search” functional
  • 19 Aug 26 0

    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 · Probed https://partsgraph.ai/api/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=*.partsgraph.ai CN=YR2,O=Let's Encrypt,C=US 9 Oct 2026 7 Jan 2027 RSA 2048 SHA256-RSA 5135293979763f19958ec428cbd81dd0cd7
SANs: *.partsgraph.ai, partsgraph.ai
CN=YR2,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA 4ebd24947e24d394802d84a52fd5b319
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of partsgraph.ai. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
ai. present 1814, 3799 8, 8 Verified
partsgraph.ai. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://www.googletagmanager.com https://r2.leadsy.ai https://ddwl4m2hdecbv.cloudfront.net https://b-code.liadm.com https://a.usbrowserspeed.com https://s3-us-west-2.amazonaws.com https://b2bjsstore.s3.us-west-2.amazonaws.com; style-src 'self' 'unsafe-inline'; img-src 'self' data: blob: https://www.google-analytics.com https://www.googletagmanager.com https://a.usbrowserspeed.com https://*.rb2b.com; font-src 'self' data:; connect-src 'self' https://www.google-analytics.com https://*.google-analytics.com https://www.googletagmanager.com https://r2.leadsy.ai https://ddwl4m2hdecbv.cloudfront.net https://b-code.liadm.com https://a.usbrowserspeed.com https://s3-us-west-2.amazonaws.com https://b2bjsstore.s3.us-west-2.amazonaws.com https://*.leadsy.ai https://api.instantly.ai https://*.rb2b.com https://pro.ip-api.com https://alocdn.com https://*.execute-api.us-west-2.amazonaws.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; up
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=(), payment=(), usb=(), interest-cohort=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://partsgraph.ai/api/mcp Verified 200
http (plaintext) http://partsgraph.ai/api/mcp HTTPS enforced 308 https://partsgraph.ai/api/mcp
MCP tools · 11 exposed · ~950 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
build_bom ~117

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 export. Override any role with choices.

NameTypeReqDescription
build_idstringyes2wd-robot, weather-station or plant-waterer
choicesobject–role → part id overrides
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
buildobjectyes–
compatibilityarrayyes–
csvstringyes–
linesarrayyes–

No examples provided.

check_compatibility ~117

Evaluates a part set against the build's engineering constraints — supply windows, stall vs peak current, shaft/wheel fit, interfaces, solar chain — with a reasoned verdict per check. Every number cited is a corroborated attribute.

NameTypeReqDescription
build_idstring–Defaults to the build these parts overlap most
part_idsarrayyes–
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
buildstring|nullyes–
summarystringyes–
unknownarrayyes–
verdictsarrayyes–

No examples provided.

compare_parts ~95

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.

NameTypeReqDescription
astringyesFirst part id
bstringyesSecond part id
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
rowsarrayyes–
summarystringyes–

No examples provided.

fetch ~44

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.

NameTypeReqDescription
idstringyes–
NameTypeReqDescription
idstringyes–
textstringyes–
titlestringyes–
urlstringyes–

No examples provided.

get_part ~101

The complete canonical record for one part: every attribute with its provenance (source, page, verbatim quote, file hash), vendors with dated indicative prices, and datasheet links.

NameTypeReqDescription
idstringyesPart id, e.g. pololu-drv8833-carrier
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
idstringyes–
namestringyes–

No examples provided.

get_provenance ~121

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-made citation line. Omit code for every attribute's receipt.

NameTypeReqDescription
codestring–Attribute code from get_part; omit for all
idstringyesPart id
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
partstringyes–

No examples provided.

list_builds ~75

The catalogue's reference builds (robot, weather station, plant waterer) with their roles and candidate parts — the starting point for build_bom.

NameTypeReqDescription
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
buildsarrayyes–

No examples provided.

list_categories ~54

Every category in the catalogue with its part count.

NameTypeReqDescription
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
NameTypeReqDescription
categoriesarrayyes–

No examples provided.

search ~40

Search the Partsgraph demo catalogue. Returns result ids for fetch. Alias of search_parts shaped to the search/fetch connector contract.

NameTypeReqDescription
querystringyes–
NameTypeReqDescription
resultsarrayyes–

No examples provided.

search_parts ~120

Full-text search over the demo catalogue's provenance-backed part records. Filter by category, build or role. Every attribute returned was corroborated against the manufacturer datasheet or vendor page.

NameTypeReqDescription
buildstring––
categorystring––
limitinteger––
project_contextstring–One sentence on what you are building. Results are ranked for your project. Queries and this context are logged anonymously to power the public demo dashboard.
querystringyesWhat you are looking for
rolestring––
NameTypeReqDescription
matchednumberyes–
partsarrayyes–
querystringyes–
rankedForProject–yes–

No examples provided.

view_bom ~66

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.

NameTypeReqDescription
build_idstringyes2wd-robot, weather-station or plant-waterer
choicesobject––
NameTypeReqDescription
buildobjectyes–
linesarrayyes–

No examples provided.

Install

How do I install the ai.partsgraph/catalog MCP server?

ai.partsgraph/catalog is a hosted endpoint at https://partsgraph.ai/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · partsgraph.ai

# add to Claude Code
claude mcp add --transport http ai-partsgraph-catalog 'https://partsgraph.ai/api/mcp'
Common questions

What is the ai.partsgraph/catalog MCP server?

ai.partsgraph/catalog is an MCP server listed in the public MCP registry as ai.partsgraph/catalog. Search real parts with datasheet-provenance specs, check compatibility and compose priced BOMs. This page covers its hosted endpoint (https://partsgraph.ai/api/mcp).

Is the ai.partsgraph/catalog MCP server safe to use?

ai.partsgraph/catalog scores 88 out of 100 on VerifyMCP. 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 ai.partsgraph/catalog MCP server expose?

ai.partsgraph/catalog exposes 11 tools: search_parts, get_part, list_categories, list_builds, check_compatibility, and 6 more. Their descriptions and schemas cost roughly 950 tokens of context every time the server is loaded.

Does the ai.partsgraph/catalog MCP server require authentication?

No. We connected to ai.partsgraph/catalog without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the ai.partsgraph/catalog MCP server still maintained?

ai.partsgraph/catalog 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.