SiteVerdict
OfficialServer Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| APIFY_TOKEN | No | Your Apify token (stdio mode) | |
| SITEVERDICT_DRY_RUN | No | 1 returns sample data with no Apify calls | 0 |
| SITEVERDICT_TOOLSETS | No | Toolsets to enable (e.g., 'all' or comma-separated list) | web |
| SITEVERDICT_DNS_CHECK | No | Resolve hostnames and reject private addresses (SSRF guard) | 1 |
| SITEVERDICT_HTTP_HOST | No | HTTP mode host | 127.0.0.1 |
| SITEVERDICT_HTTP_PATH | No | HTTP mode path | /mcp |
| SITEVERDICT_HTTP_PORT | No | HTTP mode port | 3333 |
| SITEVERDICT_ALLOWED_HOSTS | No | Comma lists for public HTTP deployments | localhost |
| SITEVERDICT_MAX_WAIT_SECS | No | How long a call waits before returning running plus a runId | 900 |
| SITEVERDICT_APIFY_USERNAME | No | Apify account that owns the Actors | from brand.json |
| SITEVERDICT_ACTOR_AI_SEARCH | No | Override individual Actor ID for AI search readiness | |
| SITEVERDICT_ALLOWED_ORIGINS | No | Comma lists for public HTTP deployments | localhost |
| SITEVERDICT_DEFAULT_WAIT_SECS | No | How long a call waits before returning running plus a runId | 240 |
| SITEVERDICT_ACTOR_DOMAIN_EMAIL | No | Override individual Actor ID for domain email health | |
| SITEVERDICT_ACTOR_ACCESSIBILITY | No | Override individual Actor ID for accessibility | |
| SITEVERDICT_ACTOR_SPEED_REVENUE | No | Override individual Actor ID for speed and revenue | |
| SITEVERDICT_MAX_CONCURRENT_RUNS | No | Concurrent Actor runs per client | 6 |
| SITEVERDICT_RATE_LIMIT_PER_MINUTE | No | Tool calls per minute per client | 20 |
| SITEVERDICT_ACTOR_TRACKING_CONSENT | No | Override individual Actor ID for tracking consent | |
| SITEVERDICT_DEFAULT_MAX_CHARGE_USD | No | Spend cap per Actor run | 2 |
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| prompts | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| audit_tracking_consentA | Loads the site in a real browser three ways (no click, Reject, Accept all) and reports which tags fire before consent or after Reject, tracking cookies set without consent, Google Consent Mode v2 signals, broken GA4/GTM tags, duplicate page_views and missing conversions. Returns a score, prioritised plain-English fixes and a link to the full HTML report. Use for GDPR/UK GDPR/PECR/ePrivacy cookie compliance and "why is my analytics data wrong" questions. Runs on the caller's own Apify account (APIFY_TOKEN) and is billed by Apify pay-per-event; nothing is charged by this server. |
| scan_speed_and_revenueA | Measures Core Web Vitals (LCP, INP, CLS, TTFB) and page weight on key pages, finds the biggest speed bottlenecks (images, render-blocking scripts, third-party tags) and, if you give traffic and order value, estimates monthly revenue lost to slow pages. Returns a score, metrics, prioritised fixes and a full-report link. Runs on the caller's own Apify account (APIFY_TOKEN) and is billed by Apify pay-per-event; nothing is charged by this server. |
| audit_accessibility_wcagA | Crawls pages in a real browser and runs axe-core WCAG 2.2 checks (A/AA/AAA), mapping issues to WCAG success criteria and EN 301 549 / European Accessibility Act duties. Returns a score, issue counts by impact, the affected pages and concrete code-level fixes, plus a full-report link. Automated testing finds a subset of WCAG issues; it does not replace a manual audit. Runs on the caller's own Apify account (APIFY_TOKEN) and is billed by Apify pay-per-event; nothing is charged by this server. |
| check_domain_email_healthA | Checks a domain's email authentication and deliverability setup (MX, SPF, DKIM, DMARC policy, BIMI, MTA-STS/TLS-RPT), DNS hygiene (DNSSEC, CAA, nameservers) and HTTPS/TLS certificate expiry. Flags spoofing risk and Gmail/Yahoo bulk-sender requirement gaps with exact DNS records to add. Runs on the caller's own Apify account (APIFY_TOKEN) and is billed by Apify pay-per-event; nothing is charged by this server. |
| check_ai_search_readinessA | Checks whether AI assistants and AI search engines can find, read and cite the site: robots.txt rules for GPTBot/ClaudeBot/PerplexityBot/Google-Extended, llms.txt, structured data (schema.org), server-rendered content, meta/canonical tags and sitemap. Returns a readiness score and prioritised fixes. Runs on the caller's own Apify account (APIFY_TOKEN) and is billed by Apify pay-per-event; nothing is charged by this server. |
| full_website_auditA | Runs the tracking & consent, speed & revenue, accessibility (WCAG 2.2), domain/email health and AI-search readiness checks IN PARALLEL on one website, then merges them into an overall score, an executive summary and a single fix list ranked by severity, legal/revenue impact and effort. Best first call for "audit my website" or "what should I fix first". Partial results are returned if one check fails. Starts one Apify run per check on the caller's Apify account (pay-per-event). |
| get_audit_resultsA | Fetches the status and results of an audit run that was still "running" when its tool returned (or any earlier run), by Apify runId. Does not start a new scan and costs nothing extra. |
| detect_tech_stackA | Detects the technology stack of one or many websites from public signals: homepage HTML, script/stylesheet URLs, HTTP headers, cookie names, public DNS (MX, SPF, DMARC, NS, CNAME), TLS issuer and robots.txt. Returns per site the technologies found (category, confidence 0-100, version, evidence) plus convenience fields cms, ecommerce, analytics, advertising, hosting, cdn, emailProviders and dnsProvider. Covers 1,000+ technologies (CMS, ecommerce and Shopify apps, analytics, tag managers, ad pixels, consent tools, CRM, chat, payments, CDN, hosting, email providers). Filters build lists such as "Shopify stores not using Klaviyo" (onlySitesUsing / excludeSitesUsing). mode "http" (default) is fast and cheap; "browser" also catches tags injected by tag managers. Respects robots.txt and never bypasses bot protection: blocked sites return status "blocked" and are not charged. It analyses only the sites you pass; it cannot list every site using a technology. Runs an Apify Actor on the caller's own Apify account (billed by Apify pay-per-event, capped per run). |
| monitor_website_changesA | Checks web pages for uptime and for changes since the last check. Per URL: up/down/blocked status, HTTP status, response time, TTFB, redirect chain, DNS result and TLS days-to-expiry; for pages checked before, a change verdict (baseline | no-change | changed) with a plain-English summary and a unified diffExcerpt. Detects text changes in the whole page or a CSS/XPath region, price changes, list items added/removed, keywords appearing/disappearing, SEO-critical changes (title, meta description, canonical, H1, noindex appearing), robots.txt/sitemap changes and, in browser mode, screenshot pixel differences. The FIRST call for a URL returns changeStatus "baseline": reuse the same stateStoreName on later calls to compare. Saves a private snapshot in the caller's Apify storage (nothing on the target site changes). Dates, times, UUIDs and copyright years are ignored by default; add ignorePatterns/excludeSelectors for false changes. Respects robots.txt; blocked pages are not charged. Browser mode costs 3x an HTTP check. Runs an Apify Actor on the caller's own Apify account (billed by Apify pay-per-event, capped per run). |
| fetch_clean_markdownA | Fetches public web pages and returns their main content as clean Markdown (no menus, ads, cookie banners or footers), plus title, author, published/modified dates, language, canonical URL, a heading outline and a ready-made citation. Tables stay Markdown tables; code blocks keep their language. Use it to read, quote or summarise a page or load documentation; cite citation.url. chunk:true returns heading-aware chunks for long pages; mode "sitemap"/"crawl" (with maxPages, includeGlobs like "/docs/**") reads several pages of one site; rendering "auto" only if a page comes back nearly empty. Respects publishers: obeys robots.txt, never bypasses paywalls, logins, CAPTCHAs or bot protection, honours noai/TDM opt-outs — such pages return status "blocked"/"paywalled" with a reason and NO content; do not retry them by other means. Runs an Apify Actor on the caller's own Apify account (billed by Apify pay-per-event, capped per run). |
| get_run_resultsA | Fetches the status and results of a run that was still "running" when a SiteVerdict data tool returned (by runId and tool name). Does not start a new run and costs nothing extra. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
| website_fix_plan | Runs the full audit and turns it into a prioritised, plain-English action plan. |
| cookie_consent_check | Checks tracking before consent / after reject and explains the fixes. |
| prelaunch_check | Speed, accessibility, email/DNS and AI-search checks before a launch or redesign goes live. |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
| score-card | Score card + findings list UI for audit results (MCP Apps / ChatGPT). |
| tools | Every data tool this connection exposes: toolsets, backing Actor, annotations, required user credentials and cost hint. |
| checks | Which tool runs which Apify Actor, and what each check covers. |
| scoring-guide | Scoring, grading and fix-plan ranking method, plus billing notes. |
TDQS
Scored across 11 tools
The audit tools target clearly distinct concerns (consent, speed, accessibility, email/DNS, AI search, tech stack, monitoring, content extraction), and full_website_audit is explicitly positioned as an aggregate. The main ambiguity is between get_audit_results and get_run_results, which both fetch async Apify run status/results and may be confused.
Most tool names use snake_case verb_noun patterns (audit_..., check_..., detect_..., monitor_..., fetch_...). The main deviation is full_website_audit, which is a noun phrase rather than a verb-led action name, and there are some verb synonyms (audit/check/scan) that are still readable.
Eleven tools are well-scoped for a multi-audit website analysis server. Each tool maps to a meaningful capability, with only minor redundancy in the two result-fetching tools.
The surface covers a broad website-audit lifecycle: consent/tracking, performance, accessibility, domain/email health, AI-search readiness, tech detection, change monitoring, and content extraction, with async result retrieval. Minor gaps remain around a dedicated general SEO/content audit or broken-link checker, though related checks are partially covered elsewhere.