Audit, fix and verify your site from your coding agent
Connect Claude Code, Cursor or VS Code to the hosted Weblyzo MCP server. Your agent audits a public URL, gets the whole edited file for each code fix, and checks the fix is live after you deploy.
Claude Code
claude mcp add --transport http weblyzo https://weblyzo-mcp.fly.dev/mcp --header "Authorization: Bearer <key>"Replace <key> with a key from Settings → Coding agents, which also has the config blocks for Cursor and VS Code.
The loop
Audit
/weblyzo:audit https://example.comaudit_site checks one page and ranks the fixes worth doing first. /weblyzo:site-health runs the same audit across up to 25 pages.
Fix
/weblyzo:fix https://example.comget_fix_patch takes the file a fix lives in and returns the whole edited file. Your agent writes it back and stops before committing.
Deploy
Review the diff and ship it through your usual pipeline. Nothing goes live until you deploy it.
Verify
/weblyzo:verify https://example.comverify_fix re-checks the live URL for each applied finding, and compare_audit reports the score before and after.
What it finds
About fifty checks against the live URL. There is no LLM in the audit path, so the same page gives the same findings on every run.
Fetched HTML
- Title and meta description
- Open Graph tags
- Canonical link
- H1 and image alt text
- JSON-LD structured data
- Viewport, lazy loading, image formats
Response headers
- HSTS
- Content-Security-Policy
- X-Frame-Options
- X-Content-Type-Options: nosniff
- Referrer-Policy
- Compression
Crawl files and links
- robots.txt
- Sitemap
- llms.txt
- Broken links
- AI crawlers blocked in robots.txt
Speed data
- Google Lighthouse lab data
- Chrome UX Report (CrUX) field data from real visitors
Six tools
- audit_site
- Page or site scope, up to 25 pages.
- audit_source
- Finds the same issues in your Next.js or HTML source before deploy, with the file and line.
- get_fix_detail
- What a finding means and how to fix it.
- get_fix_patch
- Returns the edited file for a code fix.
- verify_fix
- Confirms a fix is live on the deployed URL.
- compare_audit
- Score before and after.
- check_ai_visibility
- How visible your brand is in AI search engines: score, which engines name you, who they name instead, and what to change.
What it edits
Code fixes
Plain HTML pages, and Next.js App Router layouts where the fix lands in the metadata export. Files sent to get_fix_patch are processed in memory and never stored.
Guides for platform sites
WordPress, Shopify, Webflow, Squarespace and Wix sites have no source file to edit, so each fix comes as step-by-step instructions for the platform's settings.
Works in
Claude Code
One-line install, then the five /weblyzo: commands in any session.
Cursor
Add the server block to ~/.cursor/mcp.json.
VS Code
Add the server block to .vscode/mcp.json.
Plans
Coding agent access comes with Pro and above, and with the 14-day free Pro trial. Every tool call counts toward a monthly quota that resets each UTC month.
| Plan | Tool calls |
|---|---|
| Free | Not included |
| Starter | Not included |
| Pro | 500 a month |
| Agency | 2,500 a month |
| Enterprise | Unlimited |
Frequently asked questions
Run your first audit from the terminal
Start a 14-day free Pro trial, create a key under Settings → Coding agents, and paste the install line.