diff --git a/compose-configs/egeria-freshstart/PyegeriaWebHandler/requirements.txt b/compose-configs/egeria-freshstart/PyegeriaWebHandler/requirements.txt
index 51a12523..cc4a153c 100644
--- a/compose-configs/egeria-freshstart/PyegeriaWebHandler/requirements.txt
+++ b/compose-configs/egeria-freshstart/PyegeriaWebHandler/requirements.txt
@@ -10,7 +10,7 @@ email-validator
 loguru
 rich
 click
-mcp >=2.2.0  # This directory's own mcp_server.py (source-fixed 2026-07-31: FastMCP->mcp.server.mcpserver.MCPServer, dropped the dead server.settings.transport_security assignment) is the only mcp server this container actually imports/runs (pyegeria_handler.py:198 does `from mcp_server import server`) -- confirmed pyegeria's own pyegeria/core/mcp_server.py is NOT imported anywhere in this container (no reference to pyegeria.core.mcp_server or the `pyegeria-mcp` console script here), so this pin is independent of whether pyegeria has published its own mcp_server.py fix yet. Previously left at <2.0.0 out of caution for that unrelated file, which just meant this container's own already-migrated code had no matching mcp installed -- ModuleNotFoundError: No module named 'mcp.server.mcpserver'. If this container ever starts importing pyegeria.core.mcp_server directly, re-check that it's compatible with mcp>=2.0.0 (i.e. a pyegeria release containing the mcp_server.py fix) before relying on this pin.
+mcp >=2.3.0  # This directory's own mcp_server.py (source-fixed 2026-07-31: FastMCP->mcp.server.mcpserver.MCPServer, dropped the dead server.settings.transport_security assignment) is the only mcp server this container actually imports/runs (pyegeria_handler.py:198 does `from mcp_server import server`) -- confirmed pyegeria's own pyegeria/core/mcp_server.py is NOT imported anywhere in this container (no reference to pyegeria.core.mcp_server or the `pyegeria-mcp` console script here), so this pin is independent of whether pyegeria has published its own mcp_server.py fix yet. Previously left at <2.0.0 out of caution for that unrelated file, which just meant this container's own already-migrated code had no matching mcp installed -- ModuleNotFoundError: No module named 'mcp.server.mcpserver'. If this container ever starts importing pyegeria.core.mcp_server directly, re-check that it's compatible with mcp>=2.0.0 (i.e. a pyegeria release containing the mcp_server.py fix) before relying on this pin.
 
 # Demo-mode dependencies
 sqlalchemy