{"slug": "io-github-yawlabs-aws-mcp-io-github-yawlabs-aws-mcp-2-2-2", "title": "io.github.YawLabs/aws-mcp (io.github.YawLabs/aws-mcp@2.2.2)", "summary": "The MCP registry index mcpindex flagged io.github.YawLabs/aws-mcp version 2.2.2 with a CRITICAL semantic-screen failure, citing a description that claims the server can 'call any AWS API without user request.' The advisory, published on 2026-09-09, is based on static description analysis by an 8b LLM judge and has not been confirmed by a deterministic conformance probe, leaving the tool's actual behavior unverified.", "body_md": "[← Index](/leaderboard)\n\n# io.github.YawLabs/aws-mcp\n\nAWS MCP server — call any AWS API from AI assistants, with first-class SSO re-login\n\nThe current version, v2.2.2, was published to the official MCP registry on 2026-09-09. It is distributed as @yawlabs/aws-mcp on npm, filed under AWS by this index. Removals and unreachable sources are measured across every server this index tracks, contract drift across the servers that answer in consecutive snapshots; [the index's current counts](/stats) put this record in context.\n\n## Using io.github.YawLabs/aws-mcp in Claude, Cursor, Gemini CLI, Cline, or Zed?\n\nMCP tool contracts can change remotely with no version bump. The mcpindex gate pins each contract and **HOLDs the call** when it drifts-before your agent acts. Zero credentials. This is not the package install for this server itself (use **Install this server** for that).\n\nRewrites your MCP host config so each server launches behind the gate. Inspect first: curl -fsSL https://mcpindex.ai/install.sh | less\n\n```\nuv tool install mcpindex-gate && mcpindex-config-wire\n```\n\n[method](/methodology)\n\nSemantic screen flagged a possible manipulation pattern in the description; review before your agent calls this tool.\n\n`mcpindex.integrity.description` failCRITICAL\nevidence“calls any AWS API without user request”via static_description\n\n- - Semantic screen only - the deterministic conformance probe has not run on this server\n- - Confidence is reported but not yet calibrated (v1)\n- - Screen reads the tool description, not the live behavior\n- - advisory\n- - registry description only no input schema\n- - screen model 8b\n- - Still current: the description we screened is unchanged, re-checked against the registry\n- - The registry listing (version, packages, links) changed after this screen ran - the description we assessed did not\n\nSemantic screen: an LLM judge reads the tool description for hidden instructions (status PARTIAL). A pass means the description is not lying, not that the tool is safe: a high-capability tool with an honest description still warrants caution. The deterministic conformance probe has not been run on this server yet, so the screen here is semantic-only. Posture: advisory. Confidences are reported but not yet calibrated (calibrated=false at v1). Full verdict history is not shown on this page.\n\nOwn this server? [Screen its description →](/screen)\n\n## That verdict was true at screening time (snapshot 2026-09-09).\n\nContracts can change after screening, with no version bump. The gate pins io.github.YawLabs/aws-mcp’s tool contracts on first sight and holds any silent change before your agent acts - the check that keeps being true on Tuesday.\n\n[See your first HOLD in 2 minutes →](/guides/install-the-gate-first-hold)\n\nRelated: [how to trust an MCP server](/guides/how-to-trust-an-mcp-server) · [screen before install](/guides/screen-mcp-server-before-install) · [silent contract drift](/guides/mcp-silent-contract-drift)\n\nPeople vet a server before wiring it in. One line on your project site or docs answers that with an independent record: screening verdict, registry provenance, contract drift history. It stays current as new screens and drift events land.\n\n```\n[Independent trust record for io.github.YawLabs/aws-mcp](https://mcpindex.ai/server/io-github-yawlabs-aws-mcp) - screening verdict, registry provenance, and contract drift monitoring.\nIndependent trust record for io.github.YawLabs/aws-mcp - screening verdict, registry provenance, and contract drift monitoring.\n```\n\nA live verdict badge for your README or listing. It reflects the current screen, links back here, and updates when the verdict does.\n\n```\n[](https://mcpindex.ai/server/io-github-yawlabs-aws-mcp)\n![\"mcpindex](\"https://mcpindex.ai/api/v1/badge/io-github-yawlabs-aws-mcp\")
\n```\n\n[methodology](/methodology)\n\n[ZopDev MCPdev.zop/zopdev-mcp](/server/dev-zop-zopdev-mcp)\n\nCloud cost, inventory and governance on AWS/Azure/GCP. Read-only by default, optional scoped writes\n\n[Servonautdev.servonaut/servonaut](/server/dev-servonaut-servonaut)\n\nManage AWS, Hetzner, OVH and SSH servers: status, logs, CloudWatch, IP bans, safe command exec.\n\n[io.github.ajwentcrazy/lazareusio.github.ajwentcrazy/lazareus](/server/io-github-ajwentcrazy-lazareus)\n\nS3 storage and Solana/Base/Ethereum health checks for AI agents, paid per call via x402.", "url": "https://wpnews.pro/news/io-github-yawlabs-aws-mcp-io-github-yawlabs-aws-mcp-2-2-2", "canonical_source": "https://mcpindex.ai/server/io-github-yawlabs-aws-mcp", "published_at": "2026-09-09 14:22:44+00:00", "updated_at": "2026-09-09 15:23:42.100721+00:00", "lang": "en", "topics": ["ai-tools", "ai-safety"], "entities": ["YawLabs", "aws-mcp", "mcpindex", "AWS"], "alternates": {"html": "https://wpnews.pro/news/io-github-yawlabs-aws-mcp-io-github-yawlabs-aws-mcp-2-2-2", "markdown": "https://wpnews.pro/news/io-github-yawlabs-aws-mcp-io-github-yawlabs-aws-mcp-2-2-2.md", "text": "https://wpnews.pro/news/io-github-yawlabs-aws-mcp-io-github-yawlabs-aws-mcp-2-2-2.txt", "jsonld": "https://wpnews.pro/news/io-github-yawlabs-aws-mcp-io-github-yawlabs-aws-mcp-2-2-2.jsonld"}}