mcpbeat Sign in

iParts Estonia Parts Catalogue MCP Server

answering

iParts Estonia Parts Catalogue is answering right now. Last checked 8 min ago. It exposes 7 tools.

Read-only iParts Estonia auto parts catalogue: numbers, vehicles, categories, fitment, offers, oils.

Uptime history 36 days of history · worst day 99%
36 days agonow
100.0%
Uptime 24h
91 of 91 checks
7
Tools
read from the server
229 ms
Response time
average over 24h
open, no key
Access
streamable-http

What changed 18

Every tool that appeared, vanished or quietly changed what it asks for. Recorded since 29 September 2026. No other catalogue keeps this.

25 Oct a tool changed version
14 Oct a tool changed version4 times that day
14 Oct 2 tool descriptions were rewritten3 times that day find_part_categories, search_parts
14 Oct a tool changed the parameters it asks for2 times that day search_parts
4 Oct a tool changed version2 times that day
3 Oct a tool changed version2 times that day
3 Oct a tool changed the parameters it asks for find_part_categories
1 Oct a tool changed version2 times that day
29 Sep a tool changed version
and 8 more, back to 29 September 2026

iParts Estonia Parts Catalogue missed one check this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 8 min ago.

run in your terminal
claude mcp add catalogue --transport http https://iparts.ee/mcp
Settings → Connectors → Add custom connector, then paste this address
https://iparts.ee/mcp
~/.codex/config.toml
[mcp_servers.catalogue]
url = "https://iparts.ee/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "catalogue": {
      "url": "https://iparts.ee/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "catalogue": {
      "type": "http",
      "url": "https://iparts.ee/mcp"
    }
  }
}

Available tools 7

Read directly from the server with tools/list, grouped by what they act on. If a tool disappears, we record the date.

part
find_part_categories
Resolve a natural-language automotive part request (et/ru/en) into one or more real public iParts catalogue categories using the store's existing multilingual synonym database and Meilisearch. The tool intentionally returns multiple plausible categories (e.g. standard / economy / high-performance brake discs, or brake disc / clutch disc for "disc") instead of silently selecting the first search result. Select one or more categories only when the user's intent makes the choice clear, otherwise ask the user. Words like front/rear/left/right are not category criteria here — keep them for the refinements of find_parts_for_vehicle. Vehicle-independent unless vehicle_ref is given. Use the returned opaque category_ref with find_parts_for_vehicle (car_products entries: find_car_products). Not for part numbers (use search_parts). With vehicle_ref and no scope two channels come back — the vehicle's categories (universal=false) and universal ones (universal=true): one kind can appear in both under the same name (the car's selection and the general list); use scope="vehicle" for the car only. Paging: has_more/next_cursor continue the SAME candidate list (pass cursor with the same query and language); search_limited=true means the store's search window was full and paging cannot reveal more — ask for a more specific part name. status is decided on the complete candidate list, not on the page.
get_part
Get the public product card of one part identified by brand and article number from iParts EE (iparts.ee): name, category, EAN codes, OEM numbers (max 20), trade numbers, technical specifications (name/value/unit), images, product page URL, current retail offers (price in EUR incl. VAT, quantity, ship date, estimated delivery, order-before cut-off), availability and deposit. Pass vehicle_ref (from find_vehicle) to include a fitment check with variant-ambiguity detection and vehicle-specific criteria (required before recommending this part for that vehicle; "applicable" is a catalogue link, not a guarantee that all restrictions of the user's car are met). Optional language (et/ru/en). Availability is based on the latest supplier inventory snapshot and may change before checkout. No supplier identities or purchase prices are exposed.
parts
find_parts_for_vehicle
List purchasable parts for a previously selected vehicle (vehicle_ref from find_vehicle) and one or more resolved iParts catalogue categories (category_ref from find_part_categories; up to 5 per call, products grouped per category). Returns public product data with current retail offers (EUR, VAT included), availability and delivery, ordered like the storefront, plus public refinements such as fitting position (axle/side), dimensions, brake system or brand when several fitment variants exist. Apply returned filter references in a subsequent call (selections[].filter_refs) when the user's intent identifies a specific variant (e.g. the user said "front" and a "Front Axle" option is offered); when variant_selection_required is true and the user gave no such information, ask the user instead of choosing. Universal categories (category.universal = true: tools, workshop equipment, chemicals …) have no vehicle links: they are listed like the storefront's universal pages, with or without vehicle_ref, and their products are not vehicle-checked. Filter references are bound to the vehicle and category they were returned for. Optional language (et/ru/en).
search_parts
Search the public iParts EE (iparts.ee) automotive parts catalogue by a NUMBER: manufacturer part number, OEM number, trade number, or brand + article number. The optional brand is the brand of the searched number (as on the storefront page /search/NUMBER/BRAND), not a filter for analogue brands. Use it when the user already has a number. For a part described in words use find_part_categories (and then find_vehicle → find_parts_for_vehicle) instead. Returns matching articles with match_type (direct, trade_number, oem, cross_reference), the public product URL, whether an offer exists and the lowest current retail price in EUR (VAT included), in storefront order. Only articles with a current offer are listed, exactly as on the storefront. Paging: up to 20 per page; total_found counts every page. If has_more is true, call search_parts again with cursor = next_cursor and the same query, brand, language and limit to get the next page. Optional language (et/ru/en) selects the language of names and URLs. VIN and EAN search are not supported. Availability is based on the latest supplier inventory snapshot and may change before checkout.
car
find_car_products
The storefront's car-products catalogue (engine / gearbox / power-steering / transmission / hydraulic oil, brake fluid, batteries …) — separate from the parts catalogue of find_parts_for_vehicle; use it for oils and fluids. Without category_ref: the categories (with the vehicle's requirements when vehicle_ref is given; vehicle_specific=false marks generic lists — tyres, motorcycle/boat/agricultural oils, moto/truck batteries — that are not selected by vehicle). With category_ref: the products — selected by the vehicle's requirements (e.g. oil specification "BMW LL-04") only when match_mode = spec_matched; for no_spec_data / spec_no_match the list is the WHOLE category and NOT a selection for the vehicle: say so, and point to manual_request (a form on the storefront page; the user submits it there). Prices include VAT (EUR). Optional language (et/ru/en).
fitment
check_fitment
Check whether a specific part (brand + article number) fits a selected vehicle (vehicle_ref from find_vehicle) and return fitment restrictions or variant ambiguity when the user must choose. status: applicable (the catalogue links the part to this vehicle), universal (part linked only to "UNIVERSAL"), not_applicable, unknown (no catalogue data). IMPORTANT: "applicable" = the catalogue links the part to the selected vehicle variant; it is NOT a guarantee that every restriction of the user's actual car is met. Always check vehicle_specific_criteria (PR codes, engine numbers, production dates, equipment) and the variant criteria: several diameters/sizes/systems can exist for one vehicle. variant_selection_required=false only means the storefront check found no conflicting variants — it does not certify the part. When variant_selection_required is true, or variant_check is not_available and criteria_variation is not empty, ask the user to confirm the variant instead of choosing silently. Never recommend a not_applicable part as fitting; treat universal as "no vehicle link", not as "fits every car"; on unknown say that compatibility cannot be confirmed. Call this tool (or get_part with vehicle_ref) before any final recommendation of a specific part for a vehicle. Optional language (et/ru/en) for criterion names and labels.
vehicle
find_vehicle
Resolve the user's vehicle to an exact catalogue vehicle variant of iParts EE using make, model, year and engine details, step by step: make → models → variants. A EE licence plate ("plate") is resolved through the storefront's own plate lookup (cache first, then external registries; the first lookup of a plate may take up to a minute). A vehicle the user already chose on the storefront (garage / active car) is resolved exactly by its public vehicle page URL ("vehicle_url"). Returns an opaque vehicle_ref for each matching variant — pass it to find_parts_for_vehicle, check_fitment or get_part. Returns several candidates with needs_selection=true when the vehicle cannot be resolved safely — never picks one automatically; narrow with year, engine code, kW or fuel, or ask the user. Each match includes model, variant name, production years, engine codes, fuel, kW/hp, displacement and the vehicle page URL. Optional language (et/ru/en). VIN lookup is not available.

Endpoints

URLTransportStateLatencyChecked
https://iparts.ee/mcp streamable-http answering 107 ms 8 min ago

Alternatives to iParts Estonia Parts Catalogue

same job, measured the same way
NTWX AAAS catalogue
by ml-nightworx-aaas

Read-only parent catalogue of NTWX live surfaces. No checkout.

3 tools answering
Trail Fortress Fitment
by trailfortress

Free, read-only truck and Jeep parts fitment: what fits your vehicle, fit checks, tire sizes.

6 tools answering
Dyscalculia.io
by dyscalculia

Open number-sense practice data and game catalogue for dyscalculia. Read-only.

6 tools answering
W
White Automotive & Media Services Catalog
by whiteautoandmedia

Read-only catalog search for GM infotainment, cluster and electronics module parts.

3 tools answering
GreenGo Partners
by jamesmirusa

Read-only catalog of GreenGo Partners: search AI agents, apps, games, templates and AI news.

3 tools answering
Charm
by bitmacrocode

OEM automotive repair data - part numbers, torque specs, procedures for 1982-2013 vehicles.

2 tools answering
LibrePass eSIM
by mariusbolik

Read-only LibrePass eSIM catalogue: find countries, data plans in EUR and SIM registration rules.

4 tools answering
padel.how Racket Reviews
by padel

Read-only padel.how racket catalogue: reviews, comparisons, brands, offers, and methodology.

5 tools answering

iParts Estonia Parts Catalogue — questions

Answers built from our own checks of this server.

What can iParts Estonia Parts Catalogue do?
It exposes 7 tools, read directly from the server on our last check. Among them: check_fitment, find_car_products, find_part_categories, find_parts_for_vehicle, find_vehicle, get_part and 1 more. The full list with descriptions is on this page — we take it from the server itself via tools/list, not from a README. How MCP servers expose tools in the first place →
What is iParts Estonia Parts Catalogue mostly used for?
Its tools cluster around part and parts. That is what this server is built to work with — the grouping comes from the actual tool names, not from a category we assigned.
Is iParts Estonia Parts Catalogue working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 229 ms. The bar chart above shows every period we have measured.
How do I connect iParts Estonia Parts Catalogue?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does iParts Estonia Parts Catalogue need an API key?
No. iParts Estonia Parts Catalogue completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 7 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is iParts Estonia Parts Catalogue?
It answers our handshake in 229 ms on average, which is faster than 61% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.