Sitecurl

com.sitecurlPublished by sitecurl.comv0.2.0Updated Oct 27, 2026

Run website audits and track site health scores, findings, and regressions from any MCP client.

Overview

AI-generated overview

Sitecurl MCP lets an assistant run website audits and track site health scores, findings and regressions from any MCP client.

What you can do
  • Run website audits and retrieve site health scores.
  • Review audit findings and track regressions over time.
  • Work with the Sitecurl service from any MCP client over a local stdio process.
  • No individual tools are documented in the supplied listing, so exact operations are not described.
When to use it
Useful when you want an assistant to check a site's health, pull audit findings, or watch for regressions without leaving the chat client. Best suited to teams already on a Sitecurl Pro or Studio plan.
Requirements
Runs as a local process installed from the npm package @sitecurl/mcp over stdio; desktop clients only. Requires a Sitecurl API key in the SITECURL_API_KEY environment variable, which needs a Pro or Studio plan. An optional SITECURL_API_URL variable overrides the API base URL, which defaults to sitecurl.com. Network access to the Sitecurl API is needed.
Before you install
The server needs a Sitecurl API key (SITECURL_API_KEY), a live credential that should be kept out of shared configs and logs. It requires a paid Pro or Studio plan. Audits and any tracking actions send site data to the Sitecurl service, and the optional SITECURL_API_URL can redirect requests to a different endpoint, so only point it at a trusted host.

Installation

In SourceWeft

  1. Open Sitecurl in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Tools

0
SourceWeft has not started this package in its sandbox yet, so its tools are not known.

Version history

1
  1. v0.2.0LatestSep 16, 2026

Score

25% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts

    Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.

  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.