Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

AWS CLI MCP Server

PYPI · MDEV-AWS-MCP-SERVER

Python MCP server for AWS CLI inspection and operations

−15 this week 81 Trust /100

Last scanned (15 hours ago)

Scores higher than 82% of PyPI servers

Category Cloud Infrastructure

Trust breakdown (7 categories)

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 Security49
  • Malware scan not yet available for this package.Unverified
  • Known CVEs were checked across the 54 of 55 dependencies we could resolve, so this covers what we could see, not the whole tree.Partial
  • Runs hatchling.build at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • Dependency health was assessed across the 54 of 55 dependencies we could resolve, so this covers what we could see, not the whole tree. View diagnostics → Partial
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to musaddiq-dev/aws-cli-mcp-server). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 165 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability78
  • AI-judged instruction clarity (excellent).Pass
  • Context-footprint check failed: tool/resource definitions use about 539 tokens (~134/item across 4 items; 4 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 100% of tool parameters carry a description.Pass
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • All 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Changelog

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.

  • 3 Nov 26 −15
    • Malware scan: pass → unverified ▼ security
  • 31 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 30 Oct 26 +1
    • Stability: 0.97 → pass security
  • 29 Oct 26 −16
    • Malware scan: pass → unverified ▼ security
    • Stability: pass → 0.97 functional
  • 23 Oct 26 +1
    • Stability: 0.97 → pass security
  • 22 Oct 26 +14
    • Malware scan: unverified → pass ▲ security
    • Stability: pass → 0.97 functional
  • 19 Oct 26 −15
    • Malware scan: pass → unverified ▼ security
  • 18 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
Diagnostics

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 4 Nov 2026 · Analysed pypi/mdev-aws-mcp-server@0.1.2

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo musaddiq-dev/aws-cli-mcp-server
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/musaddiq-dev/aws-cli-mcp-server/.github/workflows/publish-pypi.yml@refs/tags/v0.1.2
Rekor log index 1613264603
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:7eee7f38639f6a4467f6ec052a4a9fbc22d289945c61e7e94a0822e3b65fd1c3

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 →

Dependencies 54 packages
Packages resolved 54
Stale 4
No linked repository 1
Tree resolution Partial

The dependency tree was only partially resolved, so these counts may be incomplete.

Background: SBOMs and build attestations, explained →

MCP tools · 4 exposed · ~539 tokens

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 →

Tool Tokens
call_aws ~264

Execute AWS CLI commands with validation and error handling. This is the primary tool for executing AWS CLI commands. Use this when you know the specific AWS service and operation you want to perform. Key points: - Commands MUST start with "aws" and follow AWS CLI syntax - Default region: us-east-1 (override with --region parameter) - Working directory: /tmp/aws-mcp-work - Use absolute paths for files Command restrictions: - DO NOT use shell pipes (|), redirects (>, >>, <), or command substitution ($()) - DO NOT use shell variables or environment variables - DO NOT use relative paths for file operations Examples: - "aws ec2 describe-instances" - List EC2 instances - "aws s3 ls" - List S3 buckets - "aws lambda list-functions" - List Lambda functions - "aws iam list-users" - List IAM users - "aws cloudwatch describe-alarms" - List CloudWatch alarms Returns: Dictionary with success status, output data, and error information

NameTypeReqDescription
cli_commandstringyesThe complete AWS CLI command to execute. MUST start with 'aws'
max_results––Optional limit for number of results (useful for pagination)

Structured output declared, but exposes no named fields.

No examples provided.

get_aws_regions ~31

Get a list of available AWS regions. Returns: Dictionary with success status and list of AWS regions

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

get_caller_identity ~55

Get the AWS identity of the current caller. Returns information about the IAM user or role whose credentials are used to call the operation. Returns: Dictionary with success status and caller identity (Account, ARN, UserId)

Input schema present but exposes no named parameters.

Structured output declared, but exposes no named fields.

No examples provided.

suggest_aws_commands ~189

Suggest AWS CLI commands based on a natural language query. Use this tool when you're unsure about the exact AWS CLI command syntax or want to explore available commands for a specific task. Best practices for query formulation: 1. Include the AWS service name (EC2, S3, Lambda, etc.) 2. Describe the action you want to perform 3. Include any relevant context or constraints Query examples: - "List all running EC2 instances in us-east-1" - "Get the size of my S3 bucket named 'my-backup-bucket'" - "List all IAM users with AdministratorAccess policy" - "Show me all Lambda functions in my account" - "Create a new security group for SSH access" Returns: Dictionary with success status, query, and list of suggested commands

NameTypeReqDescription
querystringyesNatural language description of what you want to accomplish

Structured output declared, but exposes no named fields.

No examples provided.

Install

How do I install the AWS CLI MCP Server server?

AWS CLI MCP Server runs locally as a PyPI package, launched with uvx mdev-aws-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · mdev-aws-mcp-server

# add to Claude Code
claude mcp add musaddiq-dev-aws-cli-mcp-server -- uvx mdev-aws-mcp-server
Common questions

What is the AWS CLI MCP Server server?

AWS CLI MCP Server is listed in the public MCP registry as io.github.musaddiq-dev/aws-cli-mcp-server. Python MCP server for AWS CLI inspection and operations. This page covers its PyPI package (mdev-aws-mcp-server).

Is the AWS CLI MCP Server server safe to use?

AWS CLI MCP Server scores 81 out of 100 on VerifyMCP. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the AWS CLI MCP Server server expose?

AWS CLI MCP Server exposes 4 tools: call_aws, suggest_aws_commands, get_aws_regions, get_caller_identity. Their descriptions and schemas cost roughly 539 tokens of context every time the server is loaded.

Is the AWS CLI MCP Server server still maintained?

AWS CLI MCP Server is still listed as active in the MCP registry. We last reached this channel on 4 November 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 AWS CLI MCP Server server under?

AWS CLI MCP Server declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.