# Fryer Parts Index (remote · fryerparts.pages.dev)

Read-only index of Hobart/Vulcan fryer part numbers, OEM cross-references and fitment.

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

## Components

- remote · `fryerparts.pages.dev`: 73/100 (this document), [markdown](https://verifymcp.io/servers/jsilent-fryerparts/fryerparts.md), [page](https://verifymcp.io/servers/jsilent-fryerparts/fryerparts)

## Channel facts

- Endpoint: `https://fryerparts.pages.dev/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## 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**: 75/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 360 tokens (~120/item across 3 items; 3 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**: 90/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 67% 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 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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 Fryer Parts Index MCP server?

Fryer Parts Index is a hosted endpoint at https://fryerparts.pages.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 jsilent-fryerparts 'https://fryerparts.pages.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "jsilent-fryerparts": {
      "url": "https://fryerparts.pages.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "jsilent-fryerparts": {
      "type": "http",
      "url": "https://fryerparts.pages.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.jsilent-fryerparts]
url = "https://fryerparts.pages.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "jsilent-fryerparts": {
      "type": "remote",
      "url": "https://fryerparts.pages.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add jsilent-fryerparts --url 'https://fryerparts.pages.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  jsilent-fryerparts:
    url: "https://fryerparts.pages.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "jsilent-fryerparts": {
      "Transport": "http",
      "Url": "https://fryerparts.pages.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add jsilent-fryerparts -t streamable-http -u 'https://fryerparts.pages.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "jsilent-fryerparts": {
      "type": "http",
      "url": "https://fryerparts.pages.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-21 (score 73, +1)

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

### 2026-11-18 (score 72, +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 71, +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 70, +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 69, 0)

- [functional improvement] Stability: unverified → 0.03

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

First indexed and scored.

## MCP tools (3)

### `search_parts` (~156 tokens)

Search fryer parts

Search commercial deep-fryer parts by part number, specification string or keyword (e.g. 'RX thermostat 24 in capillary', '00-419670-00001', '5500 W element', '炸炉恒温器'). Returns matching records with the canonical page URL, plus matching guides and part-vs-part comparisons when the query is a decision question ('can I use A instead of B', '5500 W or 8500 W'). This is a reference index, not a store: there are no prices or stock levels. Use get_part afterwards when you need specifications for one record.

Input parameters:

- `limit` (integer)
- `query` (string, required): Part number, spec string or keyword (English or Chinese).

Output parameters:

- `matches` (array)
- `pages` (array)

### `get_part` (~86 tokens)

Get one fryer part record

Fetch one part record by OEM part number (full or partial, e.g. '00-411506-00013' or '411506-00013'). Returns every field: part numbers, aliases (English and Chinese), specifications, FAQ and the canonical page URL. Cite the returned url, not this tool.

Input parameters:

- `part_number` (string, required): Full or partial OEM part number.

Output parameters:

- `aliases` (array)
- `aliases_zh` (array)
- `description` (string)
- `faq` (array)
- `fitment_note` (string)
- `kind` (string)
- `part_numbers` (array)
- `slug` (string)
- `specifications` (array)
- `title` (string)
- `url` (string)

### `list_parts` (~42 tokens)

List all indexed fryer parts

List every part record in the index (16 records). Use it to discover what is covered before searching, or to answer 'what do you have on X' questions.

Output parameters:

- `count` (integer)
- `records` (array)

## Diagnostics

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

## Score history

- 2026-11-21: 73
- 2026-11-20: 72
- 2026-11-19: 72
- 2026-11-18: 72
- 2026-11-17: 71
- 2026-11-16: 71
- 2026-11-15: 70
- 2026-11-14: 70
- 2026-11-13: 69
- 2026-11-12: 69

## Common questions

### What is the Fryer Parts Index MCP server?

Fryer Parts Index is an MCP server listed in the public MCP registry as io.github.JSilent/fryerparts. Read-only index of Hobart/Vulcan fryer part numbers, OEM cross-references and fitment. This page covers its hosted endpoint (https://fryerparts.pages.dev/mcp).

### Is the Fryer Parts Index MCP server safe to use?

Fryer Parts Index scores 73 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 Fryer Parts Index MCP server expose?

Fryer Parts Index exposes 3 tools: search_parts, get_part, list_parts. Their descriptions and schemas cost roughly 284 tokens of context every time the server is loaded.

### Does the Fryer Parts Index MCP server require authentication?

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

### Is the Fryer Parts Index MCP server still maintained?

Fryer Parts Index 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 Fryer Parts Index MCP server?

VerifyMCP ran 13 checks on Fryer Parts Index, 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://fryerparts.pages.dev/mcp
- Repository: https://github.com/JSilent/fryer-parts-data
- Website: https://fryerparts.pages.dev/
- Changelog RSS feed: https://verifymcp.io/servers/jsilent-fryerparts/fryerparts.xml
- Changelog JSON feed: https://verifymcp.io/servers/jsilent-fryerparts/fryerparts/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/jsilent-fryerparts/fryerparts.json
- HTML version of this page: https://verifymcp.io/servers/jsilent-fryerparts/fryerparts
