# Maglev Parts (remote · parts.trymaglev.com)

Robot parts with origin and US landed cost; quotes for CNC, sheet metal, molding and wire harnesses

- Trust score: 66/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-21

## Components

- remote · `parts.trymaglev.com`: 66/100 (this document), [markdown](https://verifymcp.io/servers/com-trymaglev-parts/parts.md), [page](https://verifymcp.io/servers/com-trymaglev-parts/parts)
- remote · `trymaglev.com`: 62/100, [markdown](https://verifymcp.io/servers/com-trymaglev-parts/trymaglev.md), [page](https://verifymcp.io/servers/com-trymaglev-parts/trymaglev)

## Channel facts

- Endpoint: `https://parts.trymaglev.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

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. 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-21.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 59/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1918 tokens (~147/item across 13 items; 13 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 3/100
  - Stability check failed: schema churn in the 10 days we've observed: 5 tool removals, 0 breaking changes, 0 auth/transport breaks, 1 additions.
- **Tool Coverage**: 86/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 52% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 13 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the Maglev Parts MCP server?

Maglev Parts is a hosted endpoint at https://parts.trymaglev.com/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.

### Claude

```bash
claude mcp add --transport http com-trymaglev-parts 'https://parts.trymaglev.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-trymaglev-parts": {
      "url": "https://parts.trymaglev.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-trymaglev-parts": {
      "type": "http",
      "url": "https://parts.trymaglev.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-trymaglev-parts]
url = "https://parts.trymaglev.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-trymaglev-parts": {
      "type": "remote",
      "url": "https://parts.trymaglev.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-trymaglev-parts --url 'https://parts.trymaglev.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-trymaglev-parts:
    url: "https://parts.trymaglev.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-trymaglev-parts": {
      "Transport": "http",
      "Url": "https://parts.trymaglev.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-trymaglev-parts -t streamable-http -u 'https://parts.trymaglev.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-trymaglev-parts": {
      "type": "http",
      "url": "https://parts.trymaglev.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-20 (score 66, +2)

- [security regression] Stability: 0.27 → fail
- [security regression] A breaking change shipped without a version bump: still 1.0.0
- [security regression] Tool “check_manufacturability” was removed
- [security regression] Tool “get_quotes” was removed
- [security regression] Tool “place_order” was removed
- [security regression] Tool “preview_order” was removed
- [security regression] Tool “upload_cad_for_quote” was removed
- [security improvement] Authorization: fail → partial
- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “build_rfq” rewrote its description, which is the text the model reads
- [functional regression] Tool coverage: 58% → 52%
- [functional regression] MCP protocol: pass → fail
- [functional improvement] Schema quality: 183 → 147
- [functional improvement] Tool “search_parts” now declares an output schema
- [functional improvement] Tool “build_rfq” now declares an output schema
- [functional improvement] Tool “check_test_result” now declares an output schema
- [functional improvement] Tool “compare_parts” now declares an output schema
- [functional improvement] Tool “find_equivalents” now declares an output schema
- [functional improvement] Tool “find_manufacturers” now declares an output schema
- [functional improvement] Tool “get_part” now declares an output schema
- [functional improvement] Tool “get_test_protocol” now declares an output schema
- [functional improvement] Tool “landed_cost” now declares an output schema
- [functional improvement] Tool “list_categories” now declares an output schema
- [functional improvement] Tool “match_requirements” now declares an output schema
- [functional improvement] Tool “plan_joint” now declares an output schema
- [functional improvement] Tool “requirement_keys” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] MCP protocol version: 2025-11-25 → 2025-06-18
- [cosmetic] “search_parts” added an optional parameter “offset”
- [cosmetic] “build_rfq” dropped the optional parameter “company”
- [cosmetic] “build_rfq” dropped the optional parameter “contact_email”
- [cosmetic] “build_rfq” dropped the optional parameter “contact_name”

### 2026-11-19 (score 64, +1)

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

### 2026-11-16 (score 63, +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.

### 2026-11-14 (score 62, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “check_manufacturability” rewrote its description, which is the text the model reads
- [security] Tool “preview_order” rewrote its description, which is the text the model reads
- [security] Tool “place_order” rewrote its description, which is the text the model reads
- [security] Tool “get_quotes” rewrote its description, which is the text the model reads
- [cosmetic] “check_manufacturability” reworded the description of “options”
- [cosmetic] “get_quotes” reworded the description of “options”
- [cosmetic] Tool “place_order” changed its title: Place a production order (paused) → Place a production order (not open yet)
- [cosmetic] Tool “preview_order” changed its title: Preview an order: total and terms → Preview an order: terms

### 2026-11-13 (score 61, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional regression] Schema quality: 149 → 168
- [functional improvement] Tool coverage: 51% → 58%
- [functional] New tool “find_manufacturers”

### 2026-11-12 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-11-11 (score 61)

First indexed and scored.

## MCP tools (13)

### `find_manufacturers` (~435 tokens)

Find manufacturers who can make a part

Use this when the user asks who can make a custom part, or needs a manufacturer, factory or machine shop: CNC machining, sheet metal, injection molding, casting, PCB fabrication and assembly, wire harnesses, 3D printing and more, in a country or region (China, US, Mexico, Canada, Taiwan, Vietnam and others). Searches Maglev's network of 912 manufacturers and returns matching shops with processes, materials, country and state or province, certifications, MOQ, production lead-time and quote-turnaround bands, and whether they take small first runs. Each shop has its name and a ref; Maglev requests the quotes (see how_to_quote). At most 50 shops per request: page with next_cursor. No key needed. Pass a plain-language query, structured filters, or both.

Input parameters:

- `certifications` (array): A shop must hold all of these.
- `countries` (array): ISO 3166 alpha-2 codes or names, e.g. ["MX"] or ["Mexico", "Canada"].
- `cursor` (string): next_cursor from the previous answer, with the same other arguments.
- `lens` (string): Origin lens, as in search_parts: any, cn (China incl. HK), not-cn, us, usmca (US/CA/MX), allied.
- `limit` (integer)
- `materials` (array): Ranks shops that state these materials first. Does not filter.
- `processes` (array): A shop matches when it does any of these.
- `quantity` (integer): Units needed. Drops shops whose stated minimum order is higher; shops with an unknown minimum stay.
- `query` (string): What to make and where, in plain words, e.g. "sheet-metal bracket in Mexico" or "injection-molded enclosure, ISO 13485, not China". Processes, part words, materials, certifications and countries (inc…
- `startup_friendly_only` (boolean): Only shops recorded as taking first, small runs.

Output parameters:

- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `how_to_quote` (string)
- `network` (object)
- `next_cursor` (string|null)
- `notes` (array)
- `returned` (integer)
- `searched` (object)
- `shops` (array)
- `total` (integer)

### `search_parts` (~186 tokens)

Search the parts catalog

Search the Maglev parts catalog (compute modules, motors and drivers, robot actuators, drone parts). Match on part number, brand, or spec words such as "48V", "Orin NX", "harmonic". Filter by where it is made and NDAA status.

Input parameters:

- `category` (string): compute-modules | motors | actuators | drone
- `lens` (string): Origin filter: any, cn (China incl. HK), not-cn, us, usmca (US/CA/MX), allied
- `limit` (integer)
- `ndaa_only` (boolean): Only NDAA-compliant or Blue UAS listed parts
- `offset` (integer): Results to skip. To page, pass the next_offset of the previous answer with the same other arguments.
- `query` (string): Search words; empty returns everything in scope

Output parameters:

- `count` (integer)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `next_offset` (integer|null)
- `offset` (integer)
- `results` (array)
- `total` (integer)

### `match_requirements` (~170 tokens)

Match parts to requirements

Route a design requirement to parts: give a subcategory (e.g. joint-actuators, strain-wave-reducers, frameless-bldc) and the numbers the design needs, and get every part ranked against them. Each result says, per requirement, whether it meets, is close (within 15%), misses, or is unknown, and the response names the requirement blocking the most options and how far to relax it. Call requirement_keys first to see which keys a subcategory accepts.

Input parameters:

- `lens` (string)
- `limit` (integer)
- `ndaa_only` (boolean)
- `priorities` (array): Requirement keys that count double in the fit score
- `qty` (integer)
- `requirements` (array, required)
- `subcategory` (string, required)

Output parameters:

- `blockers` (array)
- `counts` (object)
- `custom` (object|null)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `how_ranked` (string)
- `ignored_keys` (array)
- `lens` (string)
- `ndaa_only` (boolean)
- `qty` (integer)
- `query` (string)
- `requirements` (array)
- `results` (array)
- `subcategory` (string)

### `requirement_keys` (~43 tokens)

Requirement keys for a subcategory

The requirement keys a subcategory accepts for match_requirements: numeric keys with unit and catalog range, and text keys with their options.

Input parameters:

- `subcategory` (string, required)

Output parameters:

- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `keys` (array)
- `subcategory` (string)

### `get_part` (~60 tokens)

Get one part

Full record for one part: specs, dated prices with sources, maker, origin, HTS, NDAA/Blue UAS/FCC, equivalents and compatible parts.

Input parameters:

- `id` (string, required): Maglev part id, e.g. from search_parts

Output parameters:

- `brand` (string)
- `category` (string)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `id` (string)
- `mpn` (string)
- `name` (string)
- `origin` (object)
- `price` (array)
- `specs` (object)
- `url` (string)

### `list_categories` (~25 tokens)

List categories

Categories and subcategories with part counts and the spec columns each subcategory compares on.

Output parameters:

- `categories` (array)
- `error` (string): Set when the tool could not answer; the other fields are then absent.

### `compare_parts` (~47 tokens)

Compare parts

Side-by-side comparison of 2-10 parts: shared spec keys, price at a quantity, origin, NDAA.

Input parameters:

- `ids` (array, required)
- `qty` (integer)

Output parameters:

- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `parts` (array)
- `specs` (object)

### `landed_cost` (~145 tokens)

Estimate US landed cost

Estimate US landed cost for a part in the Maglev catalog. Needs its catalog id: find it with search_parts first; parts outside the catalog cannot be priced here. Returns goods value + duty stack for the origin (MFN, Section 301, other programs, each with a source) + merchandise processing fee + freight. An estimate, not customs advice.

Input parameters:

- `freight_usd` (number)
- `id` (string, required)
- `origin` (string): ISO-2 country it ships from; defaults to the part's origin
- `qty` (integer)
- `unit_usd` (number): Unit price to use when the part has no listed price

Output parameters:

- `as_of` (string|null)
- `disclaimer` (string)
- `duty_lines` (array)
- `duty_pct_total` (number|null)
- `duty_status` (string)
- `duty_unknown_reason` (string)
- `duty_usd` (number|null)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `freight_usd` (number)
- `goods_value_usd` (number)
- `hts` (string|null)
- `hts_is_typical` (boolean)
- `methods` (string)
- `mpf_usd` (number)
- `origin` (string|null)
- `origin_basis` (string|null)
- `origin_name` (string|null)
- `origin_note` (string|null)
- `part` (string)
- `per_unit_usd` (number)
- `qty` (integer)
- `stale` (boolean)
- `stale_reasons` (array)
- `total_assumes` (array)
- `total_excludes` (array)
- `total_usd` (number)
- `unit_usd` (number)

### `find_equivalents` (~50 tokens)

Find equivalent parts

Drop-in or near equivalents for a part from other makers, optionally restricted by origin lens, plus parts it is commonly paired with.

Input parameters:

- `id` (string, required)
- `lens` (string)

Output parameters:

- `equivalents` (array)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `pairs_with` (array)
- `part` (object)

### `get_test_protocol` (~104 tokens)

Actuator test protocol

How to bench-test a robot joint actuator: nine tests in run order (what each tells you, method, equipment, values to report, sources) and three bench kits (starter, serious, lab) with catalog part ids, quantities and listed prices. Use when someone has built or bought an actuator and asks how to verify it, or what test equipment to buy.

Input parameters:

- `kit` (string): Optional kit id to return only that kit, e.g. "starter"

Output parameters:

- `blurb` (string)
- `covers` (array)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `id` (string)
- `items` (array)
- `kits` (array)
- `lines_on_quote` (integer)
- `open_source` (array)
- `protocol_url` (string)
- `rig` (array)
- `standards` (array)
- `tests` (array)
- `title` (string)
- `total_listed_usd` (number)
- `url` (string)
- `version` (string)
- `why` (string)

### `check_test_result` (~103 tokens)

Check a bench test result

Check a bench test result for a joint actuator against the result format (/api/test/result.schema.json, template at /api/test/result-template.json) and compare the measured values with the part's datasheet in the catalog: peak torque, continuous torque, backlash, Kv, Kt. Returns errors, warnings and each measured-vs-datasheet delta. Nothing is stored.

Input parameters:

- `result` (object, required): One result in maglev.test-result/0.1 format

Output parameters:

- `against_datasheet` (array)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `errors` (array)
- `ok` (boolean)
- `part` (object|null)
- `warnings` (array)

### `build_rfq` (~106 tokens)

Draft a parts request

Build a request for Maglev to buy listed parts, price unlisted ones, or make custom versions. Returns the request document and a drafted email. It takes no name, email address or company: the email ends with a line your person fills in before sending. Nothing is sent or ordered: show it to your person first.

Input parameters:

- `items` (array, required)
- `needed_by` (string)
- `notes` (string)
- `ship_to_country` (string)

Output parameters:

- `email` (object)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `mailto` (string)
- `next_step` (string)
- `request` (object)
- `status` (string)

### `plan_joint` (~177 tokens)

Plan a robot joint

Plan a complete robot joint from targets: peak torque, output speed, bus voltage, mass budget and quantity. Returns complete joint actuators that meet the targets, and joints built from parts (frameless motor + reducer + driver + encoder) with the torque and speed math shown, listed price and mass totals, which parts still need a quote, lead times where known and where each part is made. Checks the catalog cannot make are reported as not checked.

Input parameters:

- `limit` (integer)
- `max_mass_g` (number): Mass budget for the joint, g
- `peak_torque_nm` (number, required): Peak output torque the joint needs, N·m
- `qty` (integer)
- `speed_rpm` (number): Output speed the joint needs, rpm
- `voltage_v` (number, required): Bus voltage, V

Output parameters:

- `built_from_parts` (array)
- `error` (string): Set when the tool could not answer; the other fields are then absent.
- `method` (string)
- `next` (string)
- `off_the_shelf` (array)
- `targets` (object)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-trymaglev-parts/parts#diagnostics

## Score history

- 2026-11-21: 66
- 2026-11-20: 66
- 2026-11-19: 64
- 2026-11-18: 63
- 2026-11-17: 63
- 2026-11-16: 63
- 2026-11-15: 62
- 2026-11-14: 62
- 2026-11-13: 61
- 2026-11-12: 61
- 2026-11-11: 61

## Common questions

### What is the Maglev Parts MCP server?

Maglev Parts is an MCP server listed in the public MCP registry as com.trymaglev/parts. Robot parts with origin and US landed cost; quotes for CNC, sheet metal, molding and wire harnesses. This page covers its hosted endpoint (https://parts.trymaglev.com/mcp).

### Is the Maglev Parts MCP server safe to use?

Maglev Parts scores 66 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 Maglev Parts MCP server expose?

Maglev Parts exposes 13 tools: find_manufacturers, search_parts, match_requirements, requirement_keys, get_part, and 8 more. Their descriptions and schemas cost roughly 1,651 tokens of context every time the server is loaded.

### Does the Maglev Parts MCP server require authentication?

No. We connected to Maglev Parts without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Maglev Parts MCP server still maintained?

Maglev Parts is still listed as active in the MCP registry. We last reached this channel on 21 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Maglev Parts MCP server?

VerifyMCP ran 13 checks on Maglev Parts, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://parts.trymaglev.com/mcp
- Website: https://trymaglev.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-trymaglev-parts/parts.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-trymaglev-parts/parts/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-trymaglev-parts/parts.json
- HTML version of this page: https://verifymcp.io/servers/com-trymaglev-parts/parts
