Inspection report
limonene-mcp
Vendor MCP server from Limonene. Tool list: docs5.
The answer
0
What can it change in your account?
None of the 6 tools on record can change data. This is a partial list, so a write tool may still exist.
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 not documented | 0 | 0 |
| Ads | ? Ads not documented | 0 | 0 |
| Listings | ? Listings not documented | 0 | 0 |
| Pricing | R Pricing read only | 0 | 1 |
| Inventory | R Inventory read only | 0 | 1 |
| Reports | R Reports read only | 0 | 3 |
| Finance | R Finance read only | 0 | 1 |
Record
The facts on file.
Tools
All 6 tools we found.
Grouped by what they do to your data. The access column shows why we put a tool there.
read Reads data 6
| Tool | Description | Area | Access basis |
|---|---|---|---|
| get_store_overview | bounded marketplace-local sales window. | Reports | name based |
| get_open_insights | dated existing alerts, capped at 25. | Reports | name based |
| get_pricing_and_buybox | cached observations for up to 20 SKUs; no price edits. | Pricing | name based |
| get_inventory_health | FBA-only inventory, optional SKU. | Inventory | name based |
| get_sales_trend | SKU history for 1 to 60 days. | Reports | name based |
| get_profit_breakdown | revenue/fees and available cost-coverage information; do not label fees-only figures net profit. | Finance | name based |
Method
How we checked this server.
The tool list comes from public documentation. We did not connect 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.