Build an enterprise MCP tool ecosystem

Why it matters

A shared tool catalog only stays trustworthy if every client checks what it discovers and what it gets back. This exercise builds that boundary end to end.

What to practise

Complete two FastMCP tool handlers and a client that initializes a Streamable HTTP session, lists tools and invokes one. Before invoking, the client filters the catalog by active lifecycle and required major version. A schema-violating result becomes a governed fallback, while server logs keep only tool name, correlation ID and status. Deploy the server to Azure Container Apps behind Microsoft Entra authentication, and confirm that anonymous calls are rejected and the token audience is right.

How it fits

Version-aware selection from discovered tools is 2.3.2 and 2.3.9, and the remote session and token are 2.3.3 and 2.3.4. Output-schema validation is 2.3.10, and the fallback is the last step of 2.3.8’s recovery budget.