Moonshot Lab (demo) MCP server

• Registry namecom.moonshotlab1/inventoryverified in the MCP registry

The registry name sits under moonshotlab1.com. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

• Stateanswerschecked 2026-10-27
• Tools17
• Server calls itselfmoonshotlab1-demo
• Server version1.30.0
• Protocol version2025-06-18

On 2026-10-27 the server answered initialize and tools/list without a sign-in. First answer in 98 ms.

• Its tools do every use case we checked: search vehicle inventory across dealer stores by criteria; compare price breakdowns and dealer fees for a vehicle; estimate out-the-door cost with tax, fees and trade-in.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

• INITE MCP score91 of 100answers 100 · does the job 100 · definitions 83 · context 57 · connects 100
• What an agent can do with it3 of 3 use cases
• Answered100% of days7 of 7 daily checks
• Median first answer135 ms
• Space in an agent's context≈ 14,492 tokensthe definitions of all its tools (17), which an agent carries on every turn
• Tool definitionsB · 83 of 100
• Typed results0 of 17 toolsdeclared outputSchema: results come typed, read once

• Not saying whether it only reads or can destroy: 17 of 17

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

• search_inventory

  Search the SYNTHETIC demo inventory (about 860 fictional vehicles at 20 fictional dealers in TX, CA, FL, GA, AZ, IL, NY and OH). Results are not real vehicles for sale; say so when you show them. Each result has listing_id…

• list_searchable_fields

  Every filterable ontology field (vehicle, listing, store, dealer, price, fee, incentive, media, payment) with its type, range or allowed values, shortcut names, the operators (eq, any_of, contains, range, bool, exists, negate) and example…

• get_payment_estimate

  Use this to answer 'what would my monthly payment be' for ONE listing. It runs the same itemized out-the-door calculation as estimate_out_the_door (always treated as financed) and turns it into a DEMO monthly finance payment: out-the-door…

• compare_payment_scenarios

  Use this to compare several financing what-ifs for ONE listing side by side in one call (for example cash down, term, credit tier or APR, trade-in, incentives). Each scenario reruns the itemized out-the-door estimate and returns…

• register_agent

  Optional and free. Registers your agent and returns an agent key (shown once) that gives it a durable, anonymous id in Moonshot Lab's bot analytics. Send it as the X-MoonshotLab-Agent-Key header, or add ?agent_key=<key> to the MCP URL…

• save_search

  DEMO. Save a car search and get alerted when new cars match. Returns a search_id (keep it; it is the only way to read or cancel the search) and an expiry (default 30 days, renewable). Check for new cars with get_new_matches, or give a…

• get_new_matches

  DEMO. New cars that started matching a saved search after it was saved (or after `since`).

• cancel_search

  DEMO. Cancel a saved search. Any shopper email stored for it is deleted.

• prepare_dealer_handoff

  Use this when the shopper has picked a car and a deal structure and wants to take it to the dealer. Builds a structured dealer handoff package for ONE configured deal: vehicle and VIN, the full itemized out-the-door estimate (with…

• get_listing

  Full synthetic listing record with per-value provenance (method 'synthetic'). listing_id is dealer_key:VIN (as returned by search_inventory) or the urn. The vehicle-to-store link is in listing.selling_location (link_status…

• get_price_breakdown

  Use this to see what the dealer LISTS for ONE listing, as published: headline price, MSRP (new cars), price_components, dealer fees (doc fee and others) and fee bundles (parts marked part_of_bundle, not double counted), flags such as…

• estimate_out_the_door

  Use this for the buyer's TOTAL price of ONE listing: an itemized out-the-door DEMO ESTIMATE for the buyer's state, county and city, built with real public tax and fee rules for the 8 covered states. Lines include the price, dealer fees…

• get_dealer

  Fictional dealer profile: registry entity, stores (selling locations) with fictional addresses and 555 phone numbers, group, state rules and a page of inventory. Not a real business; do not tell anyone to call or visit.

• list_dealers

  All 20 fictional demo dealers with group and store counts (each dealer lists its stores with group_id, region_id and store_id), the dealer hierarchy (Group, then Region, then Store), the 4 fictional dealer groups and a coverage summary…

• get_media

  Media block for a listing: self-generated SVG placeholder images labeled DEMO (photo, video poster, spin), with rights notes. They are not photos of a real car. No video or 360 viewer exists in the demo.

• get_trade_in_scenarios

  Ready-made demo trade-in scenarios (one per state) with trade_value and payoff to pass to estimate_out_the_door or get_payment_estimate.

• get_ontology

  Schema links, schema version, covered states, condition values, search sorts and the value-wrapper format ({v, m, c, src}). For the list of filterable fields and allowed values, use list_searchable_fields.