The MCP
Incident Room
A demo assistant is returning confusing trade data. Your job is to design a safe, testable MCP server before the incident gets worse. Choose a path, see the consequence, and try a request yourself.
Will your input contract hold?
Run all three boundary cases. Your choices change the simulated route, validation outcome, and error response.
No request sent yet.
Teaching simulator only: this page does not execute TypeScript or speak MCP. The repository tests exercise the real local MCP server.
Mission debrief
Review your decisions and test results. A completed mission can reveal a design that still needs work; that is useful evidence.
Next in the full course: implement these choices in the sample TypeScript server, then run its actual MCP integration tests.