Kuaidi100 launched China's first MCP-protocol-compatible logistics information service platform. The core API services of Kuaidi100's Baidiy
Nothing to run from here
Moonshot Lab (demo) is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
96/100
tool-list score
11
tools declared
remote
at its publisher
—
calls last 7d
What it does
Agent car inventory index. Synthetic demo data, not real inventory, not an offer.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --transport http moonshot-lab-demo-mcp https://moonshotlab1.com/mcp
# 2 — ask your agent for something these tools do
# search_inventory, list_searchable_fields, get_payment_estimate and 8 more
Moonshot Lab (demo) costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
MOAll 1 server
moonshotlab11 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. Nothing here runs on your machine and nothing runs on ours: this server answers at its publisher’s own address, and what you install is the connection straight to it.
Claude Codedeclared by this listing
This is a public server: it answers at its publisher’s own address and this marketplace is not in the path. Claude Code registers it in one command; --scope user makes it available in every project. The transport below is http, as the publisher's own manifest declares it.
claude mcp add --scope user --transport http moonshot-lab-demo-mcp https://moonshotlab1.com/mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it answers at its publisher’s own address: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it writes
One config entry pointing straight at the publisher’s own address — this marketplace is not in the path, and nothing from this listing executes on your machine.
What you approve
11 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
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 (dealer_key:VIN), vehicle basics, headline_price (before tax, title and fees), dealer_name, and selling_location: the store that holds the unit, with address and phone. link_sta
| Parameter | Type | Required | Notes |
|---|---|---|---|
| make | no | Make, case-insensitive, e.g. Honda, Ford, Tesla. 14 makes are present. | |
| model | no | Model with its punctuation, case-insensitive: CR-V, F-150, Model 3, Mustang Mach-E. | |
| year_min | no | Earliest model year. | |
| year_max | no | Latest model year. | |
| trim | no | Trim name, e.g. LX, EX-L, Lariat. | |
| condition | no | new, used or cpo (certified pre-owned). used also returns cpo units. | |
| state | no | Two-letter code of the selling store's state: TX, CA, FL, GA, AZ, IL, NY or OH. Not the full name. | |
| city | no | Exact city of the selling store (for example Houston, Katy, Plano). Suburbs are separate cities, so for 'in or near a city' prefer zip plus radius_miles. | |
| dealer_key | no | Dealer key from list_dealers, e.g. lonemesa. | |
| price_min | no | Minimum headline price in USD (before tax, title and dealer fees). | |
| price_max | no | Maximum headline price in USD (before tax, title and dealer fees). For a budget that includes taxes and fees, check estimate_out_the_door. | |
| max_mileage | no | Maximum odometer miles. | |
| body_style | no | suv, sedan, pickup, hatchback, minivan or wagon. Use pickup for trucks. | |
| fuel_type | no | gasoline, hybrid, plug_in_hybrid or electric. Use electric for EV or BEV. | |
| drivetrain | no | fwd, awd, rwd or 4wd. | |
| zip | no | Five-digit US ZIP of the shopper. With radius_miles, filters by straight-line distance to the selling store and adds distance_miles to each result. | |
| radius_miles | no | Radius in miles around zip. | |
| exterior_color | no | Exterior color family: white, black, silver, gray, blue, red, green or bronze. | |
| filters | no | Generic filters on ANY ontology field (vehicle, listing, store, dealer, price, fee, incentive, media, payment). All filters must match. See list_searchable_fields. | |
| payment_min | no | Minimum estimated monthly finance payment in USD (demo estimate). |
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 filters for search_inventory. The full compact list is about 30 KB, so narrow it with prefix or query.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| prefix | no | Only fields starting with this, e.g. canonical, price_summary, incentives, store, dealer_profile, media_block, derived, payment. | |
| query | no | Only fields whose name or description contains this text, e.g. fee, color, payment. | |
| detail | string | no | compact (default): type, range or up to 12 values. full: up to 40 allowed values, examples and counts; use it with prefix or query. |
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 total minus down payment and trade equity, amortized at the APR (or a demo APR by credit_tier) over term_months. Returns finance.estimated_monthly_payment rounde
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_id | string | yes | dealer_key:VIN from search_inventory. |
| down_payment | no | Cash down in USD, subtracted from the out-the-door total. Default 0. | |
| trade_value | no | Trade-in allowance in USD. Passed to the out-the-door step, so it gets the state's trade-in tax credit where allowed. | |
| payoff | no | Loan payoff owed on the trade-in, USD (negative equity is added to the amount financed). | |
| trade_equity | no | Net trade equity in USD when allowance and payoff are unknown (negative if upside down). Subtracted after tax, so no trade-in tax credit is applied. | |
| apr | no | APR percent, 0 to 36. If omitted, a demo APR is picked by credit_tier. | |
| credit_tier | no | excellent, good (default), fair or poor. Picks the demo APR when apr is omitted (used and cpo rates are higher than new). | |
| term_months | no | Loan term in months, 12 to 96. Default 60. | |
| buyer_state | no | Buyer's two-letter state for tax and fees. Default: the selling store's state, or the state of buyer_zip. | |
| buyer_county | no | Buyer's county without 'County', for local tax lines. | |
| buyer_city | no | Buyer's city, for local tax lines. | |
| buyer_zip | no | Buyer's five-digit ZIP. Here it sets buyer state and city when buyer_state is omitted. | |
| eligible_incentive_labels | no | label_raw values of conditional incentives from get_price_breakdown that the buyer qualifies for. |
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, selling_location_id, candidates, flags such as group_site_lists_sister_store or multi_store_unstated); the dealer block is the advertising dealer. For price and fees in a compa
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_id | string | yes | dealer_key:VIN from search_inventory, or the listing urn. |
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 whether the advertised price already includes fees, options, incentives split into all_buyer (already in the price) and conditional (not in the price), and the state'
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_id | string | yes | dealer_key:VIN from search_inventory. |
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, eligible incentives, state and local sales tax, title and registration fees, and a trade-in block (allowance, payoff, equity, tax credit). Every line has a source
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_id | string | yes | dealer_key:VIN from search_inventory. |
| buyer_state | no | Shopper's two-letter state; sets the tax and fee state. Defaults to the selling store's state. A ZIP alone does not change it here. States outside the 8 covered return a low-confidence estimate withou | |
| buyer_county | no | Shopper's county name without the word County, e.g. Harris, Cook, Orange. Improves local tax lines. | |
| buyer_city | no | Shopper's city, e.g. Chicago. Some city taxes depend on it; it can also imply the county. | |
| buyer_zip | no | Shopper's five-digit ZIP, recorded with the location. Pass buyer_state and county or city as well; the ZIP alone does not set them in this tool. | |
| registration_state | no | State where the car will be registered, if different from buyer_state. | |
| trade_value | no | Trade-in allowance in USD offered or expected for the shopper's car. | |
| payoff | no | Loan payoff in USD still owed on the trade-in. | |
| lender_name | no | Lender holding the trade-in loan (optional, not stored). | |
| eligible_incentive_labels | no | label_raw values of conditional incentives from get_price_breakdown that the shopper qualifies for (case-insensitive). | |
| financed | no | True if the purchase will be financed, false for cash. Some fees and incentives depend on it; if omitted they are flagged as uncertain. | |
| plate_transfer | boolean | no | True to transfer existing plates where the state allows it. |
| vehicle_weight_lbs | no | Vehicle weight, used by weight-based registration fees. |
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| dealer_key | string | yes | Dealer key from list_dealers or a search result, e.g. bluebonnetridge. |
| inventory_limit | integer | no | Inventory rows to include. |
| inventory_offset | integer | no | Paging offset for inventory. |
All 20 fictional demo dealers with group and store counts, plus the 4 fictional dealer groups.
No parameter schema on file.
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.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| listing_id | string | yes | dealer_key:VIN from search_inventory. |
| types | no | Filter by item type: photo, video (poster image only) or spin_exterior. | |
| limit | integer | no | Maximum items, 0 to 100. |
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.
No parameter schema on file.
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.
No parameter schema on file.
Free
$0 forever
- Every tool — any call limit is its publisher’s, not ours
- No card, and mcprush charges nothing for it
- Runs at its publisher’s own address — this marketplace is not in the path
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Moonshot Lab (demo) or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATool-list grade · score 96 / 100
Release 1.0.0-demo · scanned 20 Oct 2026
Graded from the tools this server lists, not from its source code.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score96
Findings0 threat · 0 capability
Capabilityminimal
Coveragemanifest
Verificationnot in this report
Surface digestb097eaae19604f6b93c37baa81d03932b18ebe74552d4f6b1f1c193f6ec4002e
Score vectorthreat 100 → client 96
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| coverage-honesty | manifest | inspection depth (manifest) — how much of the target the scan could see | −4 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
The scan read each tool’s name, description, input schema and annotations exactly as the server listed them the last time it answered us; no code was reviewed. We ask the server again about once a month, and a list that changed is graded again.
Tool surfaceread
Implementation sourcenot available
Package metadatanot available
Live transportnot available
The implementation source was not read — this reflects the declared tool metadata only.
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_inventory | no tags | |
| list_searchable_fields | no tags | |
| get_payment_estimate | no tags | |
| get_listing | no tags | |
| get_price_breakdown | no tags | |
| estimate_out_the_door | no tags | |
| get_dealer | no tags | |
| list_dealers | no tags | |
| get_media | no tags | |
| get_trade_in_scenarios | no tags | |
| get_ontology | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestb097eaae19604f6b
Scanned2026-10-20
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
This is an address its publisher runs: which release it serves is theirs to choose, so there is nothing here to pin. The history below is for reading; the current release on file is 1.0.0-demo.
1.0.0-demo
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish Moonshot Lab (demo) can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.