mcpbeat

FINN Auto - Car Subscription MCP Server

com.finn.www/auto
answering

FINN Auto - Car Subscription is answering right now. Last checked moments ago. It exposes 5 tools.

Search and browse cars for all-inclusive subscription on FINN. Prices, specs, and checkout links.

The linked repository no longer exists on GitHub — it was deleted or made private.

Uptime history 39 hours of history
39 hours agonow
100.0%
Uptime 24h
92 of 92 checks
5
Tools
read from the server
258 ms
Response time
average over 24h
open, no key
Access
streamable-http

Connect this server

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

run in your terminal
claude mcp add auto --transport http https://www.finn.com/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "auto": {
      "url": "https://www.finn.com/api/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.auto]
url = "https://www.finn.com/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "auto": {
      "url": "https://www.finn.com/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "auto": {
      "url": "https://www.finn.com/api/mcp"
    }
  }
}

Available tools 5

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

available
get_available_filters
Discover what's currently available in FINN's fleet. Returns all brands (with nested models), car types, fuel types, colors, subscription terms, gearshifts, and price/power/range bounds. Use this to answer questions like 'What brands does FINN offer?' or to validate filter values before searching.
internal
get_internal_link_url
Get canonical FINN URLs for a brand and its models — for building internal linking blocks on SEO pages. For each model returns three URLs that target DIFFERENT funnels: `mdp_url` (marketing/brand page), `plp_subscribe_url` (subscription product listing, /de-DE/subscribe/{brand}_{model}), and `plp_leasing_url` (leasing product listing, /de-DE/leasing/{brand}_{model}). Use `plp_leasing_url` when linking from a Leasing advisory, `plp_subscribe_url` when linking from subscription content. If `model` is omitted, returns all currently available models for the brand.
subscription
get_subscription_pricing
Calculate exact monthly subscription price for a specific vehicle, term, and mileage combination. Returns base price, km add-on, total, and a canonical checkout URL. Checkout URL structure (always use the URL returned in `checkout_url` verbatim — do NOT construct your own): https://www.finn.com/de-DE/checkout/cart/{vehicleId}/{term}/{kmPackage} https://www.finn.com/de-DE/checkout/cart/{vehicleId}/{term}/{kmPackage}?downPaymentAmount={amount} The three positional path segments after `/cart` are vehicle id, term in months, and monthly km package — in that order. About `down_payment_amount` (Fahrzeugbereitstellung): - Fahrzeugbereitstellung is a one-time vehicle provisioning fee. - When `down_payment_amount` is provided, it is paid upfront as Einmalzahlung (one-time payment) and the URL includes `?downPaymentAmount={amount}`. - When omitted, the same fee is spread across the term and absorbed into the monthly price; the URL has no query string.
vehicle
get_vehicle_details
Get full specifications, equipment, all images, and pricing per term for a specific vehicle. Use a vehicle_id from search_vehicles results. IMPORTANT: Always show `detail_url` as a clickable link — it points to the FINN configurator where the user picks term and km. To produce a direct checkout link for a specific term + km combination (and optionally a one-time Fahrzeugbereitstellung), call `get_subscription_pricing` and use the `checkout_url` it returns. Never construct checkout URLs yourself. The `vehicle_id` field is an internal API identifier — never display it to users.
vehicles
search_vehicles
Search available cars on FINN with filters. Returns matching vehicles with prices, images, and links. All filter values use German names (e.g. "Elektro" not "Electric", "Schwarz" not "Black"). IMPORTANT: Always show detail_url as a clickable link for each vehicle. The vehicle_id field is an internal API identifier for get_vehicle_details — never display it to users.

Endpoints

URLTransportStateLatencyChecked
https://www.finn.com/api/mcp streamable-http answering 208 ms 0 min ago

FINN Auto - Car Subscription — questions

Answers built from our own checks of this server.

What can FINN Auto - Car Subscription do?
It exposes 5 tools, read directly from the server on our last check. Among them: get_available_filters, get_internal_link_url, get_subscription_pricing, get_vehicle_details, search_vehicles. 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 →
Is FINN Auto - Car Subscription working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 258 ms. The bar chart above shows every period we have measured.
Is FINN Auto - Car Subscription still maintained?
The linked repository no longer exists on GitHub — it was deleted or made private. We show this because it changes what you can expect: an unmaintained server may keep answering for months and then stop without warning.
How do I connect FINN Auto - Car Subscription?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address.
Does FINN Auto - Car Subscription need an API key?
No. FINN Auto - Car Subscription completed a full MCP handshake with us as an anonymous client and listed its tools without asking for anything. All 5 of them are readable on this page. This is what we observed, not what the docs claim.
How fast is FINN Auto - Car Subscription?
It answers our handshake in 258 ms on average, which is faster than 52% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.