Inspection report
amazon-agent-atlas-mcp
Vendor MCP server from Kuudo. Tool list: code-checked5.
The answer
0
What can it change in your account?
None of the 4 tools on record 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 | R Listings read only | 0 | 4 |
| 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.
read Reads data 4
| Tool | Description | Area | Access basis |
|---|---|---|---|
| execute | Catalog entry. Runs in your Kuudo deployment, not here. Chain await call_tool(...) calls in one Python block and return the final value. Only call_tool(tool_name: str, params… | Listings | name based |
| get_schema | Catalog entry. Runs in your Kuudo deployment, not here. Get parameter schemas for specific tools. Use after searching to get the detail needed to call a tool. | Listings | name based |
| search | Catalog entry. Runs in your Kuudo deployment, not here. Search for available tools by query. Returns matching tools ranked by relevance. | Listings | name based |
| tags | Catalog entry. Runs in your Kuudo deployment, not here. List available tool tags. Use to browse available tools by tag before searching. | Listings | 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.5
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)
- 5Our 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.