One service, many agents
This site uses the same business journey, but its authoritative interface is a remote MCP-style endpoint. The page is a human client; external agents can use the same server contract.
REMOTE MCP
Flight search client
Ready. Scenario: healthy
Remote contract
POST /mcp · tools/listDiscover server-side tools and schemas.
POST /mcp · tools/callCall tools with structured arguments.
Auth + outcome validationCatchpoint should test both.
Search results will appear here.
Details and safety gate
The browser page uses REST-compatible demo routes for the visible UI. The monitoring journey should call /mcp directly to prove the server contract.