DealerMAX MCP Server
DealerMAX MCP Server is the public, read-only Model Context Protocol surface for the DealerMAX network. It lets compatible AI clients query public vehicle inventory, NLT offers, dealer directory data, vehicle specifications, and automotive knowledge without scraping and without a dealer API key.
Canonical coordinates
| Namespace | app.dealermax/public-search |
|---|---|
| Latest registry version | 1.2.1 |
| Transport endpoint | https://mcp.dealermax.app/mcp/ |
| Transport | Streamable HTTP. |
| Authentication | None. The surface is public and read-only. |
| License | CC-BY-4.0 with attribution to DealerMAX. |
| Registry | https://registry.modelcontextprotocol.io/v0.1/servers/app.dealermax%2Fpublic-search/versions/latest |
| Server card | https://mcp.dealermax.app/.well-known/mcp/server-card.json |
| Source | https://github.com/DealerMax-app/dealermax-mcp |
Tool catalog
The live server exposes seven read-only tools. The names below are the stable public tool names published in the latest registry entry and server card.
| Tool | Purpose |
|---|---|
get_vehicle_specs | Public technical specifications for Italian-market vehicles: engine, emissions, fuel consumption, dimensions, performance, seats, segment, drivetrain, tyres, and BEV charging fields when available. |
search_vehicles | Cross-dealer semantic search on used vehicles, with optional filters for region, province, city, brand, budget, and fuel type. |
search_nlt_offers | Cross-dealer search on NLT (Noleggio Lungo Termine / long-term rental) offers, including monthly-fee, duration, geography, category, fuel, transmission, commercial-vehicle, and seat filters. |
get_vehicle_details | Full detail for one vehicle by UUID or slug: specs, price, photos, dealer, canonical URL, and optional generated podcast fields. |
get_nlt_offer_details | Full detail for one NLT offer by slug: quotations, advance-payment scenarios, gallery, included accessories, tags, and network dealer offers. |
find_dealer | Directory of active DealerMAX network dealers, filterable by region, province code, province name, city, and represented brand. |
get_market_intel | Italian automotive knowledge base across editorial guides, glossary terms, FAQ, and news, with semantic search. |
Use it from an MCP client
Any MCP client that supports remote Streamable HTTP servers can use the endpoint directly:
https://mcp.dealermax.app/mcp/Clients that still require a local stdio bridge should follow that client's official MCP setup flow and keep the DealerMAX remote endpoint as the canonical server URL.
Verify the public record
These checks do not require an account, token, or API key.
curl -s "https://registry.modelcontextprotocol.io/v0.1/servers/app.dealermax%2Fpublic-search/versions/latest"curl -s "https://mcp.dealermax.app/.well-known/mcp/server-card.json"Expected registry facts: namespace app.dealermax/public-search, version
1.2.1, remote URL https://mcp.dealermax.app/mcp/, and
tool list get_vehicle_specs, search_vehicles, search_nlt_offers, get_vehicle_details, get_nlt_offer_details, find_dealer, get_market_intel.
Boundary versus REST
| MCP Server | Public, cross-network, read-only, no API key. Built for AI clients and agentic discovery. No writes, no private dealer data, no custom dealer-scoped contract. |
|---|---|
| Dealer Public API | Dealer-scoped REST API, authenticated by a dealer-generated API key. Built for server-side websites, BFFs, SSG jobs, and integrations that need one dealer's own public inventory and content. |
| PartnerMAX Enterprise | Selected-partner API and SDK path for approved multi-dealer operational workflows. |
Policy
- The MCP surface is read-only and idempotent.
- It exposes public network data only: no write workflows, no private dealer dashboard fields, no dealer API keys, and no customer PII.
- Fair-use rate limiting applies per IP to protect the public service.
- Bulk exports and dealer-specific backend integrations should use the Dealer Public API, not the anonymous MCP surface.