Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Fryer Parts Index

REMOTE · FRYERPARTS.PAGES.DEV

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

+3 this week 73 Trust /100

Last scanned (20 hours ago)

Scores higher than 59% of remote servers

Reachable. Last reached 21 Nov 2026.

Category E-commerce

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security74
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. See how to fix → View diagnostics → Partial
  • HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
Schema Quality & AI Usability75
  • AI-judged instruction clarity (good).Pass
  • Tool/resource definitions use about 360 tokens (~120/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management30
  • Stability observed for 9 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage90
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 67% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
What we tested

Checks we ran (13)

  • TLS certificate
  • Authorization
  • HTTPS
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 21 Nov 26 +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.

  • 18 Nov 26 +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.

  • 16 Nov 26 +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.

  • 14 Nov 26 +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.

  • 13 Nov 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 12 Nov 26 69

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 21 Nov 2026 · Probed https://fryerparts.pages.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=fryerparts.pages.dev CN=YE2,O=Let's Encrypt,C=US 31 Oct 2026 29 Jan 2027 ECDSA 256 ECDSA-SHA384 504e7f0bcbe632f6a9cb835e505b9719ed1
SANs: *.fryerparts.pages.dev, fryerparts.pages.dev
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of fryerparts.pages.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
pages.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://fryerparts.pages.dev/mcp Verified 200
http (plaintext) http://fryerparts.pages.dev/mcp HTTPS enforced 301 https://fryerparts.pages.dev/mcp
MCP tools · 3 exposed · ~284 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
get_part ~86

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.

NameTypeReqDescription
part_numberstringyesFull or partial OEM part number.
NameTypeReqDescription
aliasesarray––
aliases_zharray––
descriptionstring––
faqarray––
fitment_notestringyes–
kindstring––
part_numbersarrayyes–
slugstringyes–
specificationsarray––
titlestringyes–
urlstringyes–

No examples provided.

list_parts ~42

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.

Input schema present but exposes no named parameters.

NameTypeReqDescription
countintegeryes–
recordsarrayyes–

No examples provided.

search_parts ~156

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.

NameTypeReqDescription
limitinteger––
querystringyesPart number, spec string or keyword (English or Chinese).
NameTypeReqDescription
matchesarrayyes–
pagesarray––

No examples provided.

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.

remote · fryerparts.pages.dev

# add to Claude Code
claude mcp add --transport http jsilent-fryerparts 'https://fryerparts.pages.dev/mcp'
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.