{"id":"acuvity-mcp-server-aws-lambda","name":"mcp-server-aws-lambda","af_score":39.2,"security_score":56.2,"reliability_score":27.5,"what_it_does":"An MCP server implementation intended to integrate with AWS Lambda, allowing an MCP-capable agent to invoke or interact with AWS Lambda-related capabilities through MCP tools.","best_when":"You want a standardized MCP interface for calling AWS Lambda from an agent and you can tightly control AWS credentials and IAM permissions.","avoid_when":"You cannot restrict IAM permissions or you lack controls to prevent an agent from invoking unintended Lambda functions.","last_evaluated":"2026-04-04T21:35:24.118149+00:00","has_mcp":true,"has_api":false,"auth_methods":["AWS IAM credentials (e.g., access key/secret or assumed role)"],"has_free_tier":false,"known_gotchas":["Agents may invoke Lambda with unintended payloads; enforce input validation and least-privilege IAM.","Lambda executions are inherently side-effectful; treat tool calls as non-idempotent unless the specific function is designed that way.","If the MCP server lacks clear tool contracts (inputs/outputs), agents may generate incorrect event payload shapes.","AWS throttling/retries may be needed; without documented retry/idempotency semantics, agent behavior can be brittle."],"error_quality":0.0}