Inspection report
amazon_mcp
Open source MCP server from Gaurang010. Tool list: code-checked6.
The answer
1
What can it change in your account?
1 of 4 tools can change data.
name based Read and write here are inferred from tool names and descriptions, not from a test.
| Area | Access | Write tools | Read tools |
|---|---|---|---|
| Orders | · Orders no tool on record | 0 | 0 |
| Ads | · Ads no tool on record | 0 | 0 |
| Listings | · Listings no tool on record | 0 | 0 |
| Pricing | · Pricing no tool on record | 0 | 0 |
| Inventory | · Inventory no tool on record | 0 | 0 |
| Reports | · Reports no tool on record | 0 | 0 |
| Finance | · Finance no tool on record | 0 | 0 |
Record
The facts on file.
Tools
All 4 tools we found.
Grouped by what they do to your data. The access column shows why we put a tool there.
write Can change data 1
| Tool | Description | Area | Access basis |
|---|---|---|---|
| aws_s3_upload_file | Uploads text or binary file content directly to a designated S3 bucket path. | Other | name based |
read Reads data 3
| Tool | Description | Area | Access basis |
|---|---|---|---|
| aws_bedrock_invoke_model | Invokes a foundational LLM via AWS Bedrock and returns the generated text. | Other | name based |
| aws_ec2_describe_instances | Lists EC2 instances and returns their state, ip address, instance id, and tags. | Other | name based |
| aws_s3_list_buckets | Lists all available Amazon S3 buckets in your configured AWS region. | Other | name based |
Method
How we checked this server.
We read the tool definitions in the source code. We did not run the server against a seller account.6
Not tested with credentials. We did not connect this server to a seller or ads account. A tool marked read can still have side effects we could not see, and a vendor can add write tools at any time. Check the list again before you grant access.
Areas come from keywords in tool names, as explained on the matrix page.
Notes
Sources for this report
- 1Source repository or product pagegithub.com
- 2Documentationgithub.com
- 3License: GitHub API repo.license (search 2026-10-30)
- 4Authentication: static scan of repo (env names / code patterns)
- 5Pricing: https://github.com/Gaurang010/amazon_mcpgithub.com
- 6Our MCP inventory of Oct 30, 2026: tool list, access marks, stars and last commit. GitHub repository search (22 queries, unauthenticated) -> shallow clone -> static extraction (extract_tools.py) -> optional runtime tools/list (mcp_probe.py); vendor/official from public docs. access=read|write is a name/description heuristic unless access_basis says otherwise.