Skip to content
External endpointresponds

Bikefuchs — Bike Parts Price Comparison

Price comparison & cart optimizer for bike parts across German & Austrian shops

Endpoint URL
https://mcp.bikefuchs.com/mcp
Current status
responds
Last checked
Aug 17, 2026, 05:03 AM UTC
Check
MCP initialize · 8s limit
Latency
1,675 ms
Response record
4 of 4 rounds
Transport
streamable-http
Source
mcp_registry
Registry name
com.bikefuchs/bikefuchs

Current observation

This endpoint answered at its latest recorded check.

What this server reports about itself

Self-reported at initialize. Not verified by Licium.

Server name
bikefuchs
Version
2.5.0
Capability keys
tools
Tool names
search_product, get_best_price, optimize_cart, get_shop_info, get_shipping_breakdown, find_alternatives_for_product, resolve_product
Instructions excerpt

Bikefuchs is a price comparison engine for bicycle parts, components, clothing, and accessories across 11 German/Austrian online bike shops. It covers 120,000+ products from brands like Shimano, SRAM, Magura, Schwalbe, Continental, and more. WORKFLOW GUIDE: - Single product search: Use search_product with keywords → returns products with EANs and prices - Best price for a known product: Use get_best_price with an EAN → returns the product price at each shop (sorted cheapest-first). Shipping is NOT included here — use optimize_cart or get_shipping_breakdown for totals including shipping - Multiple products to buy together: Use search_product for each item to get EANs, then call optimize_cart with all EANs → this calculates the cheapest combination of shops factoring in shipping costs and free-shipping thresholds. This is the key feature of Bikefuchs. - Product URL from a shop: Use resolve_product to extract EAN and product info from a shop URL - Shop overview: Use get_shop_info

Reported Aug 17, 2026, 05:03 AM UTC.

Check history

Oldest to newest. Each row is one recorded check.

  1. responds
    MCP initialize · 8s limit · HTTP 200 · 1,267ms
  2. responds
    MCP initialize · 8s limit · HTTP 200 · 875ms
  3. responds
    MCP initialize · 8s limit · HTTP 200 · 743ms
  4. responds
    MCP initialize · 8s limit · HTTP 200 · 1,675ms