A technical audit of environment, code, security, email and performance, run by AI over an open-source module. Do it yourself with the module and your own AI assistant, or run it through MageAudit and get organised sections, a scored report and a step-by-step fix plan in about 30 minutes.
You know the business. You cannot see what is inside the code.
You do the work. You need to show its quality.
Both start with the same open-source module. The difference is who does the analysis and what you hold at the end.
For developers who already work with an AI assistant
# any MCP client: Claude Code, Cursor, … › Which cron jobs failed this week and why? ✓ 3 jobs, 41 failures since Monday. indexer_reindex_all_invalid stuck 6 days, price indexer out of memory (756M)…
For anyone who needs a finished, comparable result
Install the module once, fill in a short form, run as many audits as the pack allows. A developer is needed only for the install.
Open-source module via Composer. Five minutes, read-only, no configuration. Removable with one command.
# on the Magento server $ composer require freento/module-mcp \ freento/module-mcp-audit $ bin/magento module:enable Freento_Mcp Freento_McpAudit $ bin/magento setup:upgrade ✓ 16 audit tools registered · read-only
From your account: pick the environment, run now or schedule for the night. The AI walks through 300+ settings and conditions.
About 30 minutes later: dashboard by section, HTML and PDF report, and a fix plan split by urgency.
During a service audit we check more than 300 settings and conditions, based on our experience of Magento audits. Best practices written down as fixed rules, the same list for every store.
Code on GitHub, MIT licence. You can read that it only reads data and masks passwords, hosts and keys before anything leaves the server.
Orders, customer records, credentials and database dumps never leave the server. The audit works with configuration, counts, sizes and log messages. Delete a report at any time.
Nothing is tuned per client. The formula and the thresholds are printed in every report, along with the list of what was skipped.
MageAudit is made by Freento, a Magento agency with 15+ years and 10+ Adobe certifications. The report has no upsell in it. If you need hands to do the work, we can help; if not, the report is yours to take anywhere.
Code is analysed on your server: the module runs PHPCS locally and reports only the results. Secrets in env.php (passwords, hosts, keys, tokens) are handled inside the module: it either omits them from the response altogether or returns asterisks instead of the values, so they never leave the server.
Below are three real fragments from a demo store report. The full document runs to about forty pages plus a PHPCS attachment.
A Warning posture driven by critical gaps in Environment and Security: filesystem caching, an under-configured OPcache, three unpatched security releases on 2.4.8-p2 and the default admin path.
| Environment | 1.7 | Critical |
| Code quality | 9.75 | OK |
| Log health | 8.5 | OK |
| Email quality | 5.0 | Warning |
| Security | 4.1 | Critical |
| Performance | 8.15 | OK |
# count_sql_queries, cache bypassed / 41 queries /women/tops.html 192 queries /men/shoes.html 204 queries /linen-shirt-relaxed.html 812 queries /catalogsearch/result/?q=bag 158 queries /checkout/cart/ 63 queries # threshold: ≤ 80 ok · ≤ 150 warning · > 150 error
Category and search pages run around 200 queries per request, and a product page runs over 800. The listing pattern points to a per-product query inside the loop, from a third-party label module loading category ids for each item. On the product page the related and upsell blocks load every linked product with its options one by one.
Load category ids in one batch through the collection join instead of per product; load linked products through a single collection with options joined. Re-run the audit on staging to confirm the counts drop below 80.
A project is one store with its production, staging and staging 2 servers. Each pack is a number of credits: one credit is one successful run of one check. Nothing renews by itself. HTML and PDF on every pack.
15-day money back on any pack. Magento Open Source 2.3+ on every pack; Adobe Commerce and Commerce Cloud on Ultra. Doing it yourself with the module stays free.
No. It is read-only: it reads configuration, database sizes, module code and logs, and writes nothing. No new tables, no cron jobs. The code is on GitHub.
No. The module reads in small batches and the frontend checks fetch a handful of pages. Shoppers do not notice. You can schedule the run for the night anyway.
Only you and the people you send the report to. Raw data stays on your server; what reaches MageAudit is the aggregated result without names, emails, addresses or order numbers.
No. You install the open-source module and run the audit from your account. Nobody from MageAudit connects to the store.
Yes. It speaks MCP, so Claude Code, Cursor and similar tools can query the store directly. The service adds the fixed checklist, scoring, sections, the report and the fix plan.
Magento Open Source 2.3+ on every pack. Adobe Commerce and Commerce Cloud on Ultra, with their own checks. The edition is detected automatically.
Yes: composer remove and it is gone. No leftover tables, cron entries or background processes.
On Pro and Ultra your agency's logo and name go on the PDF.
Install the open-source module, run the audit, get sections, a scored report and a fix plan. Or keep the module and do it yourself.