Home / MCP registry index / com.moonshotlab1/inventory
Moonshot Lab (demo)
com.moonshotlab1/inventory in the official MCP registry.
Endpoint https://moonshotlab1.com/mcp.
The registry describes it as: Agent car inventory index. Synthetic demo data, not real inventory, not an offer.
We read its 17 tools on 2026-10-28. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.
A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.
Tools it advertises
search_inventory list_searchable_fields get_payment_estimate compare_payment_scenarios register_agent save_search get_new_matches cancel_search prepare_dealer_handoff get_listing get_price_breakdown estimate_out_the_door get_dealer list_dealers get_media get_trade_in_scenarios get_ontology
Run this server? Show the check in your README
The badge reflects the latest weekly read: 
[](https://lazaretto.dev/mcp-registry/com-moonshotlab1-inventory)How this was checked
Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.
To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.