Scan a website for SEO, accessibility, performance and security issues, and read the report.
com.sytecheck/sytecheck-mcp is an MCP server that scans a website and generates a report covering SEO, accessibility, performance, and security issues.
π οΈ Key Features
Website scanning
Reporting for SEO issues
Reporting for accessibility issues
Reporting for performance issues
Reporting for security issues
Returns a read report after the scan
π Use Cases
Analyze a website for SEO problems
Check accessibility on web pages
Evaluate performance issues discovered during scanning
Run website audits from Claude, Cursor, or any other MCP client, and get
the findings back as text you can act on.
SyteCheck scans a page across ten dimensions β HTML
validity, SEO, broken links, accessibility (WCAG 2.2 AA via axe-core), performance
(a real Lighthouse run), security headers, responsive layout, AI visibility,
content freshness, and an AI critique of the visual design β and returns a scored,
plain-language report.
A free account works. No card, no trial clock: the free tier includes three
scans a month across three categories, which is enough to wire this up and see a
real report before deciding whether to pay for more.
Quickstart
Create an account at sytecheck.app and verify your
email.
Mint a key at Account β API keys. Choose scans:read only if you want
the model to read existing scans but never spend quota. The secret is shown
once.
Add the server to your client, using one of the recipes below.
Submit a URL and wait for the report. Spends quota.
get_scan_report
Full findings for a scan id β the way to collect a scan run_scan left running
list_scans
Scan history, newest first, with filters
get_scan_trends
Score history per URL across repeat scans
list_categories
What SyteCheck can check, and what your plan includes
get_account_usage
Scans remaining this month, and when the quota resets
There is also a scan-and-remediate prompt that scans a URL and turns the
findings into a prioritized fix plan.
A note on cost
run_scan is the only tool that spends anything, and it spends real money: a scan
opens a browser, runs Lighthouse, and calls a vision model. It is marked
non-read-only so your client asks before running it, and its description tells the
model to check remaining quota first and not to re-scan an unchanged page. On a
free account you have three scans a month β an agent looping over run_scan
would exhaust that in one turn.
If you are handing a key to something unattended, mint a scans:read key. It
cannot create scans at all.
Configuration
Variable
Default
Purpose
SYTECHECK_API_KEY
(required)
Your sck_ API key
SYTECHECK_API_URL
https://api.sytecheck.app
API base URL
SYTECHECK_WAIT_TIMEOUT_MS
60000
How long run_scan waits before returning a scan id
SYTECHECK_POLL_INTERVAL_MS
3000
Gap between status checks while waiting
Note the API host is api.sytecheck.app, not sytecheck.app β the latter
serves the web app and answers API paths with its "page not found" screen.
Using the API directly
The MCP server is a thin client over a plain HTTP API you can call yourself.
docs/API.md β the full developer guide: authentication,
submitting scans, polling, webhooks and their signature verification, rate
limits, and versioning.
The server speaks JSON-RPC over stdin and stdout, so nothing may be written to
stdout except protocol messages β a stray console.log corrupts the stream and
the client disconnects with an unhelpful parse error. Diagnostics go to stderr.
Security
See SECURITY.md for how the key is handled, what a leaked key can
and cannot do, and how to report a vulnerability.
License
MIT β see LICENSE. The licence covers this code; the SyteCheck name and
mark are trademarks of Ascent Web Solutions, and use of the service is governed by
its Terms of Service. See TRADEMARK.md
for the full terms.
Install
Configuration
Environment variables
SYTECHECK_API_KEYrequiredsecret
SyteCheck API key, created at Account -> API keys on sytecheck.app. Begins with sck_.