Sitelemetry
Privacy Sign in

Remote MCP / Authorized web assurance

Give your agent evidence it can act on.

Connect Codex or Claude to seven Sitelemetry audit tools. Every call is OAuth-protected, restricted to an authorized workspace project, plan-limited and read-only against the target website.

Connect a client Explore all tools
7audit tools
9report languages
0write or delete tools
1protected endpoint
01 / MCP

One endpoint. Seven focused audits.

Sitelemetry gives compatible AI clients a narrow set of web-audit tools. The client sends a tool name, a target you specify and optional audit settings; Sitelemetry returns compact evidence, prioritized findings and remediation guidance.

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
    Add the endpoint

    Register https://sitelemetry.com/mcp in your MCP client.

  2. 02
    Approve access

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

  3. 03
    Ask for evidence

    Use the exact target already added to your workspace with recorded authorization and required ownership verification.

02 / Setup

Connect in minutes.

Use the remote endpoint—there is no local package or source checkout for Sitelemetry SaaS.

CX
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
CC
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
CA
Anthropic

Claude.ai

OAuth 2.1

Open Connectors, choose Add custom connector, paste the endpoint below and complete Sitelemetry authorization. Labels can vary by Claude plan and client version.

https://sitelemetry.com/mcp

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 and email posture, TLS, HTTP headers and methods, exposed files and APIs, authentication surfaces, supply-chain signals and WordPress posture using the hosted non-intrusive baseline.

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 verified URL independently. Sitelemetry preflights the current redirect chain and returns Lighthouse/CrUX metrics only when PSI's reported inspected/final URL remains inside the same authorized 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

Authorized targets only.

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

Project and ownership gate

The exact target must match a non-sample project in your workspace with recorded audit authorization and, where required, completed DNS or HTTP ownership verification. These controls reduce misuse but do not replace your responsibility to hold every necessary legal permission.

Non-intrusive hosted baseline

Hosted security calls use a fixed non-intrusive baseline. They do not run exploit payload modules, port scanning or active external scanners. Private and loopback network targets are blocked.

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 is included with Professional and Enterprise.

You need an active, verified Sitelemetry account on a plan with remote MCP access. Before a tool call, add the exact target as a workspace project, record your authorization and complete ownership verification when required. Workspace limits still apply to every audit. Starter does not include remote MCP.

Compare plans Start with Professional
08 / Control

Disconnect whenever you choose.

Remove or disable Sitelemetry in your MCP client's server or connector settings to stop future calls from that client. For immediate server-side token invalidation, account deletion or connection assistance, contact Sitelemetry support.

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