Implementation
Core retail read quickstart
Use this sequence to evaluate or implement version 0.1 without mistaking the human guide for the normative contract.
1. Explore the gateway
Start with Howard Bentley's dealer-scoped Gateway at https://mcp.dealeragentgateway.com/dealers/howard-bentley/mcp. The platform status page at mcp.dealeragentgateway.com/status lists the active dealer instance without mixing platform health with dealer inventory. Inspect the dealer authority policy before relying on availability or price.
2. Pin the artifacts
- MCP revision:
2026-07-28 - Protocol:
0.1.0-draft.1 - Schema dialect: JSON Schema 2020-12
- Bundle:
dealeragent.core-retail-read/0.1
3. Implement in dependency order
- Manifest and dealer identity.
- Inventory search and exact vehicle detail.
- Authoritative availability verification.
- Pricing disclosure with required and conditional components.
Expose tools using the exact names in the capability catalog. Validate inputs and outputs against the referenced schemas.
4. Map source authority
| Claim | Required source decision |
|---|---|
| Vehicle facts | Which catalog source is canonical for each field? |
| Search availability | How old may a discovery snapshot be? |
| Verified availability | Which source may authoritatively confirm status, and for how long? |
| Price and charges | Which dealer source publishes the current disclosure? |
| Incentives | Who defines conditions, validity, and stacking? |
5. Validate before publishing
python3 scripts/validate_artifacts.py
python3 scripts/run_conformance.py
python3 scripts/build_public_site.py
python3 scripts/validate_deployment.pyThen test human answers for sold vehicles, stale data, duplicate identifiers, conditional discounts, non-stackable incentives, missing government charges, and cross-rooftop access.
6. Publish discoverably
Serve the MCP endpoint over HTTPS, expose the protocol manifest, publish registry metadata, declare access policy, and link the endpoint to the canonical protocol version. Do not claim certification.