Amazon ECS MCP Server
PYPI · MCP-PROXY-FOR-AWS · SCANNED SEP 20
AI-powered Amazon ECS workload management
Available components
Recent critical change
CVE-2026-32871 affects this package (4 Aug 2026). See the changelog before you install this server.
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security25
- Malware scan not yet available for this package.Unverified
- CVE check failed: an unpatched critical CVE affects this package; the score is capped at 0. See how to fix → View diagnostics → Fail
- Runs hatchling.build at install time, a recognised native-build step with no shell scripting around it. View diagnostics → Pass
- 8 of 80 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency19
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 4 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
- Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess.Unverified
Stability & Change Management0
- Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare.Unverified
Tool Coverage0
- Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess.Unverified
Tool Safety0
- Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan.Unverified
Capabilities0
- Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake.Unverified
Unverified: 5 categories
Categories scored 0 because our sandbox run of this package has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →
How do I install the Amazon ECS MCP Server server?
Amazon ECS MCP Server runs locally as a PyPI package, launched with uvx mcp-proxy-for-aws. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
pypi · mcp-proxy-for-aws
claude mcp add aws-api-us-east-1-ecs-mcp-server -- uvx mcp-proxy-for-aws
{
"mcpServers": {
"aws-api-us-east-1-ecs-mcp-server": {
"command": "uvx",
"args": [
"mcp-proxy-for-aws"
]
}
}
} {
"servers": {
"aws-api-us-east-1-ecs-mcp-server": {
"command": "uvx",
"args": [
"mcp-proxy-for-aws"
]
}
}
} codex mcp add aws-api-us-east-1-ecs-mcp-server -- uvx mcp-proxy-for-aws
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"aws-api-us-east-1-ecs-mcp-server": {
"type": "local",
"command": [
"uvx",
"mcp-proxy-for-aws"
],
"enabled": true
}
}
} openclaw mcp add aws-api-us-east-1-ecs-mcp-server --command uvx --arg mcp-proxy-for-aws
mcp_servers:
aws-api-us-east-1-ecs-mcp-server:
command: "uvx"
args: ["mcp-proxy-for-aws"] {
"McpServers": {
"aws-api-us-east-1-ecs-mcp-server": {
"Transport": "stdio",
"Command": "uvx",
"Arguments": [
"mcp-proxy-for-aws"
]
}
}
} assistant mcp add aws-api-us-east-1-ecs-mcp-server -t stdio -c uvx -a mcp-proxy-for-aws
{
"mcpServers": {
"aws-api-us-east-1-ecs-mcp-server": {
"command": "uvx",
"args": [
"mcp-proxy-for-aws"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 14 Sept 26 0
- Malware scan: pass → unverified ▼ security
- 12 Sept 26 0
- Malware scan: unverified → pass ▲ security
- 11 Sept 26 0
- Malware scan: pass → unverified ▼ security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 12 Aug 26 0
- Security disclosure: unverified → fail ▼ functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Malware scan: unverified → pass ▲ security
- 8 Aug 26 0
- Malware scan: pass → unverified ▼ security
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 20 Sept 2026 · Analysed pypi/mcp-proxy-for-aws@1.1.6
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | pypi |
Background: How many MCP packages publish verified provenance →
Install scripts 1 script
| Hook | Tier | Command |
|---|---|---|
| build_backend | allowlisted | hatchling.build |
Background: Why install scripts are a supply-chain risk →
Vulnerabilities 8 findings
| ID | CVE | Severity | Vector | Fix available |
|---|---|---|---|---|
| GHSA-5h2m-4q8j-pqpj | CVE-2025-69196 | high | yes | |
| GHSA-m8x7-r2rg-vh5g | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| GHSA-rww4-4w9c-7733 | CVE-2026-27124 | high | yes | |
| GHSA-vv7q-7jx5-f767 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
| PYSEC-2026-2474 | CVE-2025-69196 | none | yes | |
| PYSEC-2026-2475 | CVE-2025-64340 | medium | CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H | yes |
| PYSEC-2026-2476 | CVE-2026-27124 | none | yes | |
| PYSEC-2026-338 | CVE-2026-32871 | critical | CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H | yes |
Background: What a vulnerability scan can and cannot prove →
Dependencies 80 packages
| Packages resolved | 80 |
|---|---|
| Stale | 4 |
| No linked repository | 4 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.
What is the Amazon ECS MCP Server server?
Amazon ECS MCP Server is listed in the public MCP registry as aws.api.us-east-1.ecs-mcp/server. AI-powered Amazon ECS workload management. This page covers its PyPI package (mcp-proxy-for-aws).
Is the Amazon ECS MCP Server server still maintained?
Amazon ECS MCP Server is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the Amazon ECS MCP Server server under?
Amazon ECS MCP Server declares the Apache-2.0 licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.