The full upstream README, mirrored here for reference. Install config, tool schemas, adoption signals, and an original overview live on the Sitelemetry listing page.
Sitelemetry is a hosted, remote MCP server for authorized website audits. Connect it to your AI assistant and ask for a security, technical SEO, AI visibility, analytics and tracking integrations, accessibility or performance audit in plain language. Each tool returns prioritized findings with severity, evidence, impact and a recommended fix.
This repository contains documentation only. Sitelemetry runs as a hosted service at
https://sitelemetry.com/mcp; the server source code is not published here.
| Endpoint | https://sitelemetry.com/mcp |
| Transport | Streamable HTTP (remote only) |
| Authorization | OAuth 2.1 with PKCE (browser sign-in, no API key in the client configuration) |
| Tools | 7 audit tools (your client lists the ones the connected account's plan includes) |
| Report languages | English, Turkish, Spanish, German, French, Portuguese, Italian, Japanese, Chinese |
| Registry name | com.sitelemetry/sitelemetry |
| Full setup guide | https://sitelemetry.com/mcp-guide |
Add the server to .vscode/mcp.json in your workspace, or to your user MCP configuration:
Start the server from the CodeLens above the entry, from the MCP SERVERS section of the Extensions view, or with the MCP: List Servers command. When VS Code asks you to authenticate, complete the Sitelemetry sign-in in your browser (sign in or create an account), then approve access.
Then open /mcp in Claude Code and choose Authenticate for Sitelemetry.
Add this entry to .cursor/mcp.json in your project, or to ~/.cursor/mcp.json for all projects:
Add a remote MCP server named sitelemetry with the URL https://sitelemetry.com/mcp. Select Streamable HTTP and OAuth if your client asks. The client needs to support remote HTTP MCP servers and browser-based OAuth.
ChatGPT and Claude.ai users can connect through the Sitelemetry listing in those apps. See the setup guide for details.
Long hosted audits return a job instead of a final result. The client checks that same job until the result is ready, without starting a second scan. If your client has a per-call timeout setting, allowing up to 15 minutes avoids cutting off long audits.
| Tool | What it does |
|---|---|
audit_security | Security posture of a website: public checks such as DNS, e-mail authentication records, TLS and HTTP security headers on any target; on a verified host, the protected and active checks your plan includes. |
audit_seo | Technical SEO crawl: crawlability, indexation, titles and meta tags, headings, canonical tags, structured data, broken internal links, redirect chains and AI-crawler policy. |
audit_ai_visibility | How ready a site's content is to be found and cited by AI search and LLM assistants: entity clarity, answerability, source signals, llms.txt and AI-crawler policy. |
audit_integrations | Analytics, tag manager, marketing pixel, site verification and consent setup detected from the site's HTML and headers. |
audit_accessibility | WCAG 2.2-oriented checks of the static HTML: image alternatives, form labels, heading structure, landmarks, contrast signals, language attribute and more. |
audit_performance | Performance and Core Web Vitals through Google PageSpeed Insights: LCP, INP, CLS, FCP, TTFB and the top improvement opportunities. |
audit_full | Every audit area the connected account includes, in one call, with a combined score across the measured areas. |
Every tool takes an explicit target URL and a report language. The dotted names (audit.security, audit.full, …) are accepted as aliases.
Once connected, ask your assistant in plain language, for example:
Sitelemetry is operated by Egenil Teleferik Mühendislik Teknik İşletme Danışmanlık Limited Şirketi.