fix: pin mcp<2.0.0 to prevent FastMCP import breakage in MCP server examples

[jyotsnamas]

Summary

• Pin mcp>=1.10.0,<2.0.0 in all 7 MCP-related requirements.txt files
• MCP 2.0+ renamed FastMCP → MCPServer and moved the module path from mcp.server.fastmcp to mcp.server.mcpserver
• Without the upper bound, uv resolves to mcp 2.1.1 which causes ModuleNotFoundError at runtime, leading to initialization timeout and empty tool responses

Verification

Deployed 02-mcp-server-features to AgentCore Runtime in us-west-2:

• Without fix: Runtime init timeout, tools return empty {}
• With fix: All MCP tools, prompts, and resources work correctly

Files changed

7 requirements.txt files under 01-features/02-host-your-agent/01-runtime/

Test plan

• Deploy 02-mcp-server-features with pinned dep — tools/list, tools/call, prompts/list all return data
• Deploy 09-mcp-e2e/01-server-e2e with pinned dep — finance tracker tools work
• Verify strands-agents modules unaffected (they transitively constrain mcp<2.0.0)

🤖 Generated with Claude Code

[github-actions]

Latest scan for commit: 5f3d570 | Updated: 2026-08-31 16:07:11 UTC

Security Scan Results

Scan Metadata

• Project: ASH
• Scan executed: 2026-08-31T16:04:33+00:00
• ASH version: 3.0.0

Summary

Scanner Results

The table below shows findings by scanner, with status based on severity thresholds and dependencies:

Column Explanations:

Severity Levels (S/C/H/M/L/I):

• Suppressed (S): Security findings that have been explicitly suppressed/ignored and don't affect the scanner's pass/fail status
• Critical (C): The most severe security vulnerabilities requiring immediate remediation (e.g., SQL injection, remote code execution)
• High (H): Serious security vulnerabilities that should be addressed promptly (e.g., authentication bypasses, privilege escalation)
• Medium (M): Moderate security risks that should be addressed in normal development cycles (e.g., weak encryption, input validation issues)
• Low (L): Minor security concerns with limited impact (e.g., information disclosure, weak recommendations)
• Info (I): Informational findings for awareness with minimal security risk (e.g., code quality suggestions, best practice recommendations)

Other Columns:

• Time: Duration taken by each scanner to complete its analysis
• Action: Total number of actionable findings at or above the configured severity threshold that require attention

Scanner Results:

• PASSED: Scanner found no security issues at or above the configured severity threshold - code is clean for this scanner
• FAILED: Scanner found security vulnerabilities at or above the threshold that require attention and remediation
• MISSING: Scanner could not run because required dependencies/tools are not installed or available
• SKIPPED: Scanner was intentionally disabled or excluded from this scan
• ERROR: Scanner encountered an execution error and could not complete successfully

Severity Thresholds (Thresh Column):

• CRITICAL: Only Critical severity findings cause scanner to fail
• HIGH: High and Critical severity findings cause scanner to fail
• MEDIUM (MED): Medium, High, and Critical severity findings cause scanner to fail
• LOW: Low, Medium, High, and Critical severity findings cause scanner to fail
• ALL: Any finding of any severity level causes scanner to fail

Threshold Source: Values in parentheses indicate where the threshold is configured:

• (g) = global: Set in the global_settings section of ASH configuration
• (c) = config: Set in the individual scanner configuration section
• (s) = scanner: Default threshold built into the scanner itself

Statistics calculation:

• All statistics are calculated from the final aggregated SARIF report
• Suppressed findings are counted separately and do not contribute to actionable findings
• Scanner status is determined by comparing actionable findings to the threshold

Scanner	S	C	H	M	L	I	Time	Action	Result	Thresh
bandit	0	0	0	0	145	0	2.7s	0	PASSED	MED (g)
cdk-nag	0	0	0	0	0	0	8.5s	0	PASSED	MED (g)
cfn-nag	0	0	0	0	0	0	13ms	0	PASSED	MED (g)
checkov	0	0	0	0	0	0	8.0s	0	PASSED	MED (g)
detect-secre…	0	0	0	0	0	0	1.7s	0	PASSED	MED (g)
grype	0	0	0	0	0	0	1m 1s	0	PASSED	MED (g)
npm-audit	0	0	0	0	0	0	336ms	0	PASSED	MED (g)
opengrep	0	0	0	0	0	0	<1ms	0	SKIPPED	MED (g)
semgrep	0	0	0	0	0	0	<1ms	0	MISSING	MED (g)
syft	0	0	0	0	0	0	3.6s	0	PASSED	MED (g)