# NomyParts open data (remote · nomyparts-open-data.nomyparts.workers.dev)

Read-only catalog of drone and eVTOL components: products, makers, specs and sources.

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

## Components

- remote · `nomyparts-open-data.nomyparts.workers.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/com-nomyparts-open-data/nomyparts-open-data.md), [page](https://verifymcp.io/servers/com-nomyparts-open-data/nomyparts-open-data)

## Channel facts

- Endpoint: `https://nomyparts-open-data.nomyparts.workers.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.1`

## 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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server, and every tool looks verifiably read-only (it declares readOnlyHint: true, starts its name with a read verb and describes no write), so an anonymous caller can read but cannot change anything. We can't see whether a tool returns data specific to one caller, so keep any per-user data behind authorisation.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 461 tokens (~92/item across 5 items; 5 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 30/100
  - Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 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 NomyParts open data MCP server?

NomyParts open data is a hosted endpoint at https://nomyparts-open-data.nomyparts.workers.dev/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-nomyparts-open-data 'https://nomyparts-open-data.nomyparts.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-nomyparts-open-data": {
      "url": "https://nomyparts-open-data.nomyparts.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-nomyparts-open-data": {
      "type": "http",
      "url": "https://nomyparts-open-data.nomyparts.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-nomyparts-open-data]
url = "https://nomyparts-open-data.nomyparts.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-nomyparts-open-data": {
      "type": "remote",
      "url": "https://nomyparts-open-data.nomyparts.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-nomyparts-open-data --url 'https://nomyparts-open-data.nomyparts.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-nomyparts-open-data:
    url: "https://nomyparts-open-data.nomyparts.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-nomyparts-open-data": {
      "Transport": "http",
      "Url": "https://nomyparts-open-data.nomyparts.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-nomyparts-open-data -t streamable-http -u 'https://nomyparts-open-data.nomyparts.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-nomyparts-open-data": {
      "type": "http",
      "url": "https://nomyparts-open-data.nomyparts.workers.dev/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 76, +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-18 (score 75, +1)

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

### 2026-11-16 (score 74, +1)

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

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

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

### 2026-11-13 (score 72, +3)

- [security] Tool “compare_products” rewrote its description, which is the text the model reads
- [security] Tool “get_company” rewrote its description, which is the text the model reads
- [security] Tool “get_product” rewrote its description, which is the text the model reads
- [security] Tool “list_categories” rewrote its description, which is the text the model reads
- [security] Tool “search_components” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 69 → 92
- [functional improvement] Tool coverage: 78% → 100%
- [functional improvement] Stability: unverified → 0.03
- [cosmetic] “compare_products” reworded the description of “ids”
- [cosmetic] “search_components” reworded the description of “limit”
- [cosmetic] Tool “compare_products” changed its title: Compare products
- [cosmetic] Tool “get_company” changed its title: Get company
- [cosmetic] Tool “get_product” changed its title: Get product
- [cosmetic] Tool “list_categories” changed its title: List categories
- [cosmetic] Tool “search_components” changed its title: Search components

### 2026-11-12 (score 69)

First indexed and scored.

## MCP tools (5)

### `search_components` (~187 tokens)

Search components

Search the catalog of components by text, category, subcategory, manufacturer and specification filters. Returns the total number of matches and, for each of the first results, the product id, name, manufacturer, category, key specifications and the URL of its profile.

Input parameters:

- `category` (string): Category id or name (see list_categories).
- `limit` (integer): Maximum number of results to return (1 to 25, default 10).
- `manufacturer` (string): Manufacturer id or part of its name.
- `query` (string): Words to look for (name, manufacturer, type).
- `specs` (object): Specification filters by specification id: a number range {"min": 10, "max": 50} (in the SI unit when the specification has one) or a text that must be contained.
- `subcategory` (string): Subcategory id or name.

### `get_product` (~58 tokens)

Get product

The full record of one product: manufacturer, category, every specification with its unit and the source page of each value, the date each was checked, and its profile URL.

Input parameters:

- `id` (string, required): Product id, as returned by search_components.

### `get_company` (~49 tokens)

Get company

The record of one manufacturer: description, country, website, certifications and the list of its products with their ids and profile URLs.

Input parameters:

- `id` (string, required): Manufacturer id (manufacturerId of a product).

### `list_categories` (~37 tokens)

List categories

The categories and subcategories of the catalog (ids and names, to use as filters in search_components), with the number of products of each.

### `compare_products` (~75 tokens)

Compare products

Compare two to five products side by side, specification by specification: returns each product and, for every specification they state, the value of each one with its unit.

Input parameters:

- `ids` (array, required): Ids of the products to compare side by side, as returned by search_components (2 to 5; any further ids are ignored).

## Diagnostics

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

## Score history

- 2026-11-21: 76
- 2026-11-20: 76
- 2026-11-19: 75
- 2026-11-18: 75
- 2026-11-17: 74
- 2026-11-16: 74
- 2026-11-15: 73
- 2026-11-14: 73
- 2026-11-13: 72
- 2026-11-12: 69

## Common questions

### What is the NomyParts open data MCP server?

NomyParts open data is an MCP server listed in the public MCP registry as com.nomyparts/open-data. Read-only catalog of drone and eVTOL components: products, makers, specs and sources. This page covers its hosted endpoint (https://nomyparts-open-data.nomyparts.workers.dev/mcp).

### Is the NomyParts open data MCP server safe to use?

NomyParts open data scores 76 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 NomyParts open data MCP server expose?

NomyParts open data exposes 5 tools: search_components, get_product, get_company, list_categories, compare_products. Their descriptions and schemas cost roughly 406 tokens of context every time the server is loaded.

### Does the NomyParts open data MCP server require authentication?

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

### Is the NomyParts open data MCP server still maintained?

NomyParts open data 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 NomyParts open data MCP server?

VerifyMCP ran 12 checks on NomyParts open data, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about NomyParts open data: HTTPS. 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://nomyparts-open-data.nomyparts.workers.dev/mcp
- Website: https://www.nomyparts.com/developers/
- Changelog RSS feed: https://verifymcp.io/servers/com-nomyparts-open-data/nomyparts-open-data.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-nomyparts-open-data/nomyparts-open-data/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-nomyparts-open-data/nomyparts-open-data.json
- HTML version of this page: https://verifymcp.io/servers/com-nomyparts-open-data/nomyparts-open-data
