{"type":"video","version":"1.0","html":"<iframe src=\"https://www.loom.com/embed/b1ff00c9e53348deb25a231689799b10\" frameborder=\"0\" width=\"1276\" height=\"957\" webkitallowfullscreen mozallowfullscreen allowfullscreen></iframe>","height":957,"width":1276,"provider_name":"Loom","provider_url":"https://www.loom.com","thumbnail_height":957,"thumbnail_width":1276,"thumbnail_url":"https://cdn.loom.com/sessions/thumbnails/b1ff00c9e53348deb25a231689799b10-789ffacc7e8ba8f4.gif","duration":314.923,"title":"Testing an MCP Server for Order Issues","description":"This Loom explains how to test a hosted MCP server. The tools that the server provides helps you investigate why a paid commerce order has not reached shipment creation. It describes using an MCP server that gathers evidence from payment, inventory, fulfillment, and shipment records, then applies deterministic rules, stores an audit trail, and recommends human review. The reviewer can test first via an MCP inspector by starting the inspector, connecting, viewing five tools, and investigating an order such as 1042, which is not shipped because the assigned warehouse is out of stock and an alternative warehouse exists. It also outlines a second path using the Gemini CLI with a reviewer token from a Bitward link to add the hosted MCP server and run the same investigation, including an evidence snapshot and AI work log details."}