aws-mcpBLOCK

const SSH = 'ssh -i ~/.ssh/gh_woods -o IdentitiesOnly=yes';

payload: { password: "hunter2-should-not-leak" },

aws_resource_delete, aws_resource_status, aws_session_clear

return new Function(`${pieces}\nreturn runtimePlan;`)() as RuntimePlan;

return new Function(`${pieces}\nreturn { pickNewest, floor: OAM_MIN };`)() as {

const remedyFor = new Function(

const childEnv = new Function(

const discover = new Function(

: "a cp1252 byte in ~/.aws/config cannot parse where the preferred encoding is UTF-8",

"file://~/.aws/credentials",

"file://$HOME/.aws/credentials",

"file://%USERPROFILE%/.aws/credentials",

const err = new Error("connect ECONNREFUSED 169.254.169.254:80");

'\r\naws: [ERROR]: Read timeout on endpoint URL: "http://127.0.0.1:28763/2015-03-31/functions/slow-6000/invocations"\r\n',

'\r\nRead timeout on endpoint URL: "http://127.0.0.1:28841/2015-03-31/functions/slow-4000/invocations?Qualifier=PROD"\r\n',

'\r\naws: [ERROR]: Connect timeout on endpoint URL: "http://192.0.2.1:9/2015-03-31/functions/ok/invocations"\r\n',

'\r\naws: [ERROR]: Connection was closed before we received a valid response from endpoint URL: "http://127.0.0.1:28763/2015-03-31/functions/reset/invocations".\r\n',

const m = READ_TIMEOUT_RE.exec('\r\naws: [ERROR]: Read timeout on endpoint URL: "http://127.0.0.1:28842/"\r\n');

@modelcontextprotocol/sdk, @types/node, @types/turndown, @yawlabs/mcp-compliance, esbuild, node-html-parser, postject, turndown

- **The bundled MCP SDK moves from 1.30.0 to 1.32.1** (GHSA-6qxp-vccf-f47h, high: the SDK's OAuth client could send credentials to an authorization server chosen by the MCP server). The SDK is bundled

- **The 0600 on the two files that can hold credentials is verified now rather than assumed, and a filesystem that cannot honour it fails the call instead of leaking.** The `--cli-input-json` params f

- **Blob-typed `params` are always base64.** This is a behavior change for one configuration. With `cli_binary_format = raw-in-base64-out` in your AWS config -- common advice, AWS's own docs suggest i

- **`aws_docs_read` could not open the `index.html` pages `aws_docs_search` hands out.** docs.aws.amazon.com answers every `<path>/index.html` with a 301 to `<path>/`, and the post-redirect check adde

- **A Registry-driven install had no way to offer a profile, so it wrote none.** `server.json` declared no environment variables, so an installer reading the MCP Registry entry had nothing to prompt f

- **`aws_lambda_invoke` could run a function three times and still return nothing.** A function slower than 60 s hit the AWS CLI's default socket read timeout, and the CLI's standard retry mode then s