Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Catalog is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
Search real parts with datasheet-provenance specs, check compatibility and compose priced BOMs.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http partsgraph-catalog-mcp https://partsgraph.ai/api/mcp
# 2 — ask your agent for something these tools do
# search_parts, get_part, list_categories and 8 more
Catalog costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http partsgraph-catalog-mcp https://partsgraph.ai/api/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | What you are looking for |
| category | string | no | — |
| build | string | no | — |
| role | string | no | — |
| limit | integer | no | — |
| project_context | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Part id, e.g. pololu-drv8833-carrier |
| project_context | string | no | 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. |
Every category in the catalogue with its part count.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_context | string | no | 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. |
The catalogue's reference builds (robot, weather station, plant waterer) with their roles and candidate parts — the starting point for build_bom.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| project_context | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| part_ids | array | yes | — |
| build_id | string | no | Defaults to the build these parts overlap most |
| project_context | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| a | string | yes | First part id |
| b | string | yes | Second part id |
| project_context | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | Part id |
| code | string | no | Attribute code from get_part; omit for all |
| project_context | string | no | 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. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| build_id | string | yes | 2wd-robot, weather-station or plant-waterer |
| choices | object | no | role → part id overrides |
| project_context | string | no | 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. |
Search the Partsgraph demo catalogue. Returns result ids for fetch. Alias of search_parts shaped to the search/fetch connector contract.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| query | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| id | string | yes | — |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| build_id | string | yes | 2wd-robot, weather-station or plant-waterer |
| choices | object | no | — |
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Catalog or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
This listing is an address its publisher runs, and you connect to it directly — this marketplace is not in the path. The scanner reads packages and public source, and an address is neither. So there is no grade — not a withheld one, an unmeasured one.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.4.0.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Catalog can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.