Back to Browse

Sytecheck MCP Server

by BertPC
Developer ToolsModerate7.2MCP RegistryLocal
Free

Server data from the Official MCP Registry

Scan a website for SEO, accessibility, performance and security issues, and read the report.

About

Scan a website for SEO, accessibility, performance and security issues, and read the report.

Security Report

7.2
Moderate7.2Low Risk

SyteCheck MCP server is well-designed with strong security practices for API credential handling, proper authentication enforcement, and careful error handling to prevent credential leakage. The codebase demonstrates good security discipline with no malicious patterns or dangerous operations detected. Minor observations include broad exception handling and a credential advisory note that could be more explicit, but these are low-severity and do not meaningfully impact security. Supply chain analysis found 1 known vulnerability in dependencies (0 critical, 1 high severity). Package verification found 1 issue.

7 files analyzed · 5 issues found

Security scores are indicators to help you make informed decisions, not guarantees. Always review permissions before connecting any MCP server.

Permissions Required

This plugin requests these system permissions. Most are normal for its category.

HTTP Network Access

Connects to external APIs or services over the internet.

env_vars

Check that this permission is expected for this type of plugin.

What You'll Need

Set these up before or after installing:

SyteCheck API key, created at Account -> API keys on sytecheck.app. Begins with sck_.Required

Environment variable: SYTECHECK_API_KEY

API base URL. Only set this to point at a non-production SyteCheck instance.Optional

Environment variable: SYTECHECK_API_URL

How to Install

Add this to your MCP configuration file:

{
  "mcpServers": {
    "com-sytecheck-sytecheck-mcp": {
      "env": {
        "SYTECHECK_API_KEY": "your-sytecheck-api-key-here",
        "SYTECHECK_API_URL": "your-sytecheck-api-url-here"
      },
      "args": [
        "-y",
        "@ascentws/sytecheck-mcp"
      ],
      "command": "npx"
    }
  }
}

Documentation

View on GitHub

From the project's GitHub README.

SyteCheck MCP Server

Run website audits from Claude, ChatGPT, 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

  1. Create an account at sytecheck.app and verify your email.
  2. 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.
  3. Add the server to your client, using one of the recipes below.

Claude Code

claude mcp add sytecheck --env SYTECHECK_API_KEY=sck_your_key_here \
  -- npx -y @ascentws/sytecheck-mcp

Claude Desktop

Edit claude_desktop_config.json (Settings → Developer → Edit Config):

{
  "mcpServers": {
    "sytecheck": {
      "command": "npx",
      "args": ["-y", "@ascentws/sytecheck-mcp"],
      "env": { "SYTECHECK_API_KEY": "sck_your_key_here" }
    }
  }
}

Cursor

Add to .cursor/mcp.json in your project, or the global equivalent:

{
  "mcpServers": {
    "sytecheck": {
      "command": "npx",
      "args": ["-y", "@ascentws/sytecheck-mcp"],
      "env": { "SYTECHECK_API_KEY": "sck_your_key_here" }
    }
  }
}

Gemini CLI / Antigravity CLI

Add to ~/.gemini/settings.json (or the Antigravity equivalent):

{
  "mcpServers": {
    "sytecheck": {
      "command": "npx",
      "args": ["-y", "@ascentws/sytecheck-mcp"],
      "env": { "SYTECHECK_API_KEY": "sck_your_key_here" }
    }
  }
}

OpenAI Agents SDK

from agents import Agent
from agents.mcp import MCPServerStdio

sytecheck = MCPServerStdio(
    params={
        "command": "npx",
        "args": ["-y", "@ascentws/sytecheck-mcp"],
        "env": {"SYTECHECK_API_KEY": "sck_your_key_here"},
    }
)

agent = Agent(
    name="Site auditor",
    instructions="Audit sites with SyteCheck and explain what to fix.",
    mcp_servers=[sytecheck],
)

Then ask: "Scan https://example.com and tell me what to fix first."

Tools

ToolWhat it does
run_scanSubmit a URL and wait for the report. Spends quota.
get_scan_reportFull findings for a scan id — the way to collect a scan run_scan left running
list_scansScan history, newest first, with filters
get_scan_trendsScore history per URL across repeat scans
list_categoriesWhat SyteCheck can check, and what your plan includes
get_account_usageScans 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

VariableDefaultPurpose
SYTECHECK_API_KEY(required)Your sck_ API key
SYTECHECK_API_URLhttps://api.sytecheck.appAPI base URL
SYTECHECK_WAIT_TIMEOUT_MS60000How long run_scan waits before returning a scan id
SYTECHECK_POLL_INTERVAL_MS3000Gap 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.
  • public-openapi.json — the OpenAPI 3.1 spec, for generating a client.
  • examples/ — runnable clients in curl, Python, Node, Java, and C#, plus a webhook receiver that verifies the delivery signature.
  • Interactive docs: Swagger UI · ReDoc

Development

npm install
npm run build
npm test
npm run lint

To run against a local SyteCheck instance:

SYTECHECK_API_KEY=sck_… SYTECHECK_API_URL=http://localhost:8000 node dist/index.js

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.

Reviews

No reviews yet

Be the first to review this server!