# Trymaglev Parts MCP server

Source: https://glimind.com/server/mcp-registry%2Fcom.trymaglev%2Fparts
Registry id: `mcp-registry/com.trymaglev/parts`
Status: live (checked 2026-11-22T17:20:05.961Z)

## Measurements (30 days)

- Uptime: 100%
- Checks: 947
- Outages (90 days): 0

## Install

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

Claude Code:

```sh
claude mcp add --transport http trymaglev-parts-mcp-server https://trymaglev.com/mcp
```

## Tools (13)

- `build_rfq`: 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
- `check_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 
- `compare_parts`: Side-by-side comparison of 2-10 parts: shared spec keys, price at a quantity, origin, NDAA.
- `find_equivalents`: Drop-in or near equivalents for a part from other makers, optionally restricted by origin lens, plus parts it is commonly paired with.
- `find_manufacturers`: 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
- `get_part`: Full record for one part: specs, dated prices with sources, maker, origin, HTS, NDAA/Blue UAS/FCC, equivalents and compatible parts.
- `get_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 (star
- `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
- `list_categories`: Categories and subcategories with part counts and the spec columns each subcategory compares on.
- `match_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 e
- `plan_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 targe
- `requirement_keys`: The requirement keys a subcategory accepts for match_requirements: numeric keys with unit and catalog range, and text keys with their options.
- `search_parts`: 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", "

Measured by Glimind (https://glimind.com): MCP handshake + tool list only, no tool is ever called. CC BY 4.0.
