Sitelemetry
Privacy Sign in

Remote MCP / Authorized web assurance

Give your agent evidence it can act on.

Choose the setup for your MCP client below. Sitelemetry audit calls are OAuth-protected, limited by your plan and read-only against the target website.

Connect a client Explore all tools
7audit tools
9report languages
0write or delete tools
6client setup options
01 / MCP

Connect with the setup for your client.

Sitelemetry gives compatible AI clients seven focused web-audit tools. The client sends a tool name, an explicit target and supported audit settings; Sitelemetry returns the full available audit evidence, prioritized findings and remediation guidance. Audit calls record usage and audit data in Sitelemetry without changing the target website.

Connecting MCP does not give an agent access to your hosting account, CMS, source code or Google account. The hosted tools inspect publicly reachable web signals and do not change the target.

  1. 01
    Choose your client

    Use the general endpoint for Codex, Claude Code, Cursor and other compatible MCP clients, or connect through the Sitelemetry listing in ChatGPT or Claude.ai.

  2. 02
    Approve access

    Sign in to Sitelemetry and approve the audit scope in your browser.

  3. 03
    Ask for evidence

    For Codex and Claude Code, public audits can use public targets; protected scans need workspace verification. For Claude.ai, every audit needs the exact verified HTTPS target.

02 / Setup

Connect in minutes.

Choose the source-private plugin for Cloud plus Local Agent, or keep the remote-only OAuth setup below.

Single-package Local Agent

One source-private plugin registers Sitelemetry Cloud, a loopback-only Local Agent, and the audit/fix/re-test workflow.

OpenAI

Codex Marketplace

Cloud + Local
codex plugin marketplace add ozandikici/sitelemetry-plugins && codex plugin add sitelemetry@sitelemetry
Anthropic

Claude Marketplace

Cloud + Local
claude plugin marketplace add ozandikici/sitelemetry-plugins && claude plugin install sitelemetry@sitelemetry

The Local Agent connects only to localhost, 127.0.0.1 or ::1 and consumes no Sitelemetry Cloud scan quota. It does not send site data to Sitelemetry Cloud; audit requests and results return to your MCP client and may be processed by its model provider under your client/provider settings.

Long hosted audits continue in the background. Your assistant automatically checks the same job until the full result is ready, without starting another scan. The timeout settings below are optional.

OpenAI

Codex

OAuth 2.1

Add the server, then start the browser authorization flow once.

codex mcp add sitelemetry --url https://sitelemetry.com/mcp
codex mcp login sitelemetry

Optional: allow 900 seconds (15 minutes) per tool call. Merge this into the existing Sitelemetry section in ~/.codex/config.toml, then restart Codex.

[mcp_servers.sitelemetry]
url = "https://sitelemetry.com/mcp"
tool_timeout_sec = 900
Codex MCP documentation
Anthropic

Claude Code

OAuth 2.1

Add the HTTP server, open /mcp in Claude Code and choose Authenticate for Sitelemetry.

claude mcp add --transport http sitelemetry https://sitelemetry.com/mcp

Use a current Claude Code version. The optional timeout allows 900000 milliseconds (15 minutes) per tool call. If Sitelemetry is already configured, add timeout: 900000 to its existing server entry, then restart Claude Code.

Claude Code MCP documentation
Cursor

Cursor

OAuth 2.1

Add this entry to .cursor/mcp.json in your project, or ~/.cursor/mcp.json for all projects. Merge it with any existing mcpServers entries.

{
  "mcpServers": {
    "sitelemetry": {
      "url": "https://sitelemetry.com/mcp"
    }
  }
}

In Cursor's MCP settings, connect Sitelemetry. Sign in or create your Sitelemetry account in the browser, then approve access. OAuth handles sign-in; no API key is needed.

Cursor setup documentation

Optional: if your client supports tool timeout settings, allow 15 minutes for long calls. Available settings and limits depend on the client version.

Streamable HTTP

Other MCP clients

OAuth 2.1

Add a remote MCP server named Sitelemetry with the URL below. Select Streamable HTTP and OAuth if your client asks.

https://sitelemetry.com/mcp

Use a client that supports remote HTTP MCP and browser-based OAuth. Connect, sign in or create a Sitelemetry account, and approve access; the client then loads the available tools.

Anthropic

Claude.ai

OAuth 2.1

Open the Sitelemetry listing in Claude.ai and connect your account. Complete Sitelemetry authorization in your browser.

Connect in Claude.ai
Custom connector setup

If you need a custom connector, add the Claude endpoint below in Claude.ai's connector settings and complete authorization.

https://claude-mcp.sitelemetry.com/mcp
OpenAI

ChatGPT

OAuth 2.1

Open the Sitelemetry listing in ChatGPT, connect your account, and complete Sitelemetry authorization in your browser.

Connect in ChatGPT

OAuth clients receive a short-lived, audience-bound access token—not your Sitelemetry password, account API key or stored Google integration credentials.

03 / Tools

The complete tool surface.

Every tool requires a target. Optional inputs are deliberately narrow and results are returned as concise text plus structured audit data.

01
audit_security

Security audit

Checks DNS, email DNS, RDAP registration, TLS, HTTP security headers, HTTPS/MITM posture, technology fingerprinting and transport delivery by default. Target verification follows your client's rules; additional modules remain subject to your plan and hosted-scan policy.

02
audit_seo

Technical SEO

Crawls public pages for indexation, metadata, headings, canonicals, structured data, internal-link failures, redirects and AI-crawler policy.

03
audit_ai_visibility

AI visibility

Assesses entity clarity, answerability, source signals, prompt coverage, llms.txt and crawler policy for AI search and answer engines.

04
audit_integrations

Analytics and tracking

Detects analytics, tag managers, marketing pixels, site-verification signals, consent systems and potential PII exposure in public data-layer output.

05
audit_accessibility

Accessibility

Runs a static WCAG 2.2-oriented review of alternative text, labels, headings, landmarks, contrast signals, language declarations, duplicate IDs and iframe titles.

06
audit_performance

Performance

Uses Google PageSpeed Insights, which fetches the requested public URL independently. Sitelemetry preflights the current redirect chain and accepts Lighthouse/CrUX metrics only when PSI's reported inspected/final URL remains inside the same safe host and port boundary.

07
audit_full

Full audit

Runs all six pillars in parallel, returns one blended score and summarizes every pillar. Use individual tools afterward when you need the full finding list for one discipline.

04 / Prompts

Ask for an outcome, not a tool name.

A compatible client can choose the right Sitelemetry tool from your request.

01

Run a full Sitelemetry audit of example.com in English. Prioritize critical and high findings, then give me a sequenced remediation plan.

02

Audit the technical SEO of example.com across 12 pages. Group fixes into crawlability, metadata, structured data and internal links.

03

Check example.com for WCAG-oriented accessibility issues. Show the evidence for each high-impact problem and propose acceptance criteria.

04

Evaluate whether example.com is easy for answer engines to understand and cite. Turn the top five AI-visibility gaps into implementation tasks.

05

Review the analytics and consent stack on example.com. Flag missing verification, duplicate tags and any public data-layer fields that may contain personal data.

05 / Safety

Target verification by client.

Sitelemetry is a defensive assurance service, not an open scanning proxy.

Workspace verification

Codex, Claude Code and ChatGPT protected scans need workspace ownership verification. Claude.ai needs current proof for the exact HTTPS target on every audit. A new verified site gets a monitoring project if a slot is available; it can still be audited when slots are full, within your plan's allowance. Verify ownership through Sitelemetry DNS or HTTP, or Google Search Console with siteOwner permission.

Public audits and protected scans

Codex and Claude Code support public targets for eight public security checks, SEO, AI Visibility, Integrations, Accessibility and Performance. Protected security modules and Full Audit need workspace verification. Claude.ai requires target verification for all these audits.

No target mutation

The seven tools make observation requests and return evidence. They do not sign in to, create, edit or delete content in the audited website or its connected accounts.

Bounded and accounted operation

Every successful call records Sitelemetry usage and audit/security state and consumes the applicable plan quota. Subscription entitlements, rate limits, concurrency controls and timeouts apply to remote calls; Sitelemetry-originated web requests also use server-side SSRF and redirect controls. PageSpeed's independent fetch and returned-result boundary are disclosed above.

06 / Data

Know what crosses the connection.

Sitelemetry receives MCP protocol traffic and the tool arguments your client sends: the requested tool, target, report language and any supported audit setting. It processes public technical responses and returns audit evidence to that client. It does not independently access the rest of your AI conversation.

Your chosen AI client provider receives the tool request and returned results as part of your conversation and handles them under its own terms and privacy policy. Sitelemetry may retain account, usage, security and audit records as described in the Privacy Policy; it does not sell personal information.

Privacy PolicyData categories, purposes, providers, retention and rights Terms of ServiceAuthorized-use rules and service limitations
07 / Access

Remote MCP transport is available to every account.

Any active, verified Sitelemetry account can connect through Remote MCP. Claude.ai lists all seven audit tools. Execution depends on the connected account's plan and remaining quota. Free supports audit_security within its low monthly security allowance; other audits require an eligible plan. Codex and Claude Code public audits do not require workspace target verification when available; protected security modules and audit_full do. Claude.ai requires the exact verified HTTPS target for every audit. Account, usage and workspace limits apply to every call.

Compare plans Start with Professional

Verified sites, monitoring and usage

Verified domains define which targets are authorized. Monitoring projects store sites for ongoing tracking; project capacity is separate from domain verification. A full project slot does not by itself prevent audits of other verified sites. Audit permissions and remaining usage allowances still apply.

Understanding Sitelemetry access

08 / Control

Disconnect whenever you choose.

In Sitelemetry, open My account and Connected MCP applications to revoke an application's access. This revokes all authorizations for that application at the selected MCP address; other applications are unaffected. You can also remove Sitelemetry from your client settings. Reconnecting requires authorization again.

Product and connection supportsupport@sitelemetry.com
Service operatorEGENİL TELEFERİK MÜHENDİSLİK TEKNİK İŞLETME DANIŞMANLIK LİMİTED ŞİRKETİ