Outrings Web Intelligence

Outrings gives AI agents a factual view of the web.

CommunityOnlineNo sign-inGlobalFreeRead-only

What it can do

  • Audit Website: Run the full 200-check audit of a website and return the overall score, every category score, and the ranked list of what to fix first. Use this when the user asks a broad question abou
  • Check Category: Inspect a single area and return its verdict, the checks that failed, why each matters and how to fix it. Categories: seo, ai (whether AI crawlers and answer engines can read and cite
  • Get Score: The cheapest useful call: overall score, letter grade and every category score, with no findings or prose. Use it when comparing sites, when the user only wants a number, or as a first step

What data it sees

Do you need an account

No: the server works without sign-in

Outrings gives AI agents a factual view of the web. Inspect websites through deterministic measurements, structured evidence, and machine-readable intelligence across SEO, security, AI visibility, DNS, infrastructure, accessibility, and more.

How to connect

How to connect Outrings Web Intelligence to Claude

The server address to paste into Claude settings:

https://web_intelligence--outrings.run.tools

  1. Open Claude (claude.ai or the desktop app).
  2. Go to Settings → Connectors.
  3. Click Add custom connector.
  4. Paste the server address copied below into Remote MCP server URL and click Add.
  5. In a chat, click + → Connectors and switch the new connector on.

Custom connectors are available on Free, Pro, Max, Team and Enterprise plans (Free is limited to one). On Team and Enterprise an organization Owner adds the connector first under Organization settings → Connectors.

Authorization

After you click Add, a sign-in window for the service opens. Sign in with your own account and approve access. Claude never sees your password.

How to connect Outrings Web Intelligence to ChatGPT

The server address to paste into ChatGPT settings:

https://web_intelligence--outrings.run.tools

  1. Open ChatGPT in a browser (chatgpt.com). A Plus, Pro, Business, Enterprise or Edu plan is required.
  2. Turn on developer mode once: Settings → Apps → Advanced settings → Developer mode.
  3. Open Settings → Connectors and click Create.
  4. Fill in the form: Name (anything), Description (one line about what the service does), MCP server URL (copy it below).
  5. Under Authentication choose OAuth if the service requires sign-in, otherwise None. Click Create.
  6. In a new chat open + → Apps/Connectors and enable the connector.

OpenAI has renamed this section before (Connectors → Apps/Plugins). If the label differs, search settings for "developer mode". On Business/Enterprise workspaces an admin must allow custom connectors first.

Authorization

On first use ChatGPT opens the service's sign-in window. Sign in and approve access.

How to connect Outrings Web Intelligence to Cursor

The server address to paste into Cursor settings:

https://web_intelligence--outrings.run.tools

Fastest: click Open in Cursor below and confirm the prompt.

Manually:

  1. In Cursor open Settings → Cursor Settings → MCP and click Add new global MCP server.
  2. Paste the JSON copied below into ~/.cursor/mcp.json (per project: .cursor/mcp.json in the repo root).
  3. Save the file. The server appears in the MCP list; authorize it there if asked.

Authorization

If the service needs sign-in, an authorize button appears next to the server in the MCP list.

Server tool list (8)

Raw names from tools/list. Only developers need these.

audit_websiteRun the full 200-check audit of a website and return the overall score, every category score, and the ranked list of what to fix first. Use this when the user asks a broad question about a site — "how is my website", "what is wrong with it", "is this site any good" — or when you need grounding before advising on changes. Takes roughly 2-8 seconds. If the user only cares about one area, check_category is faster and returns less.
check_categoryInspect a single area and return its verdict, the checks that failed, why each matters and how to fix it. Categories: seo, ai (whether AI crawlers and answer engines can read and cite the site), security (headers, exposure, secrets in source), privacy, tls (certificate and protocol), dns (records, SPF, DMARC, CAA), a11y (accessibility), content, slop (AI-generated-filler signals), design, infra, tech, credibility, correlation (does the page deliver what its title promises), faq, discoverability, local, contact. Use this rather than audit_website when the question is narrow — "is my site secure", "why is my SEO bad", "can ChatGPT see my site".
get_scoreThe cheapest useful call: overall score, letter grade and every category score, with no findings or prose. Use it when comparing sites, when the user only wants a number, or as a first step before deciding which category to look into.
check_ai_visibilityMeasures technical crawler access and the page signals that affect whether an AI system can retrieve and parse a site. Reports, per crawler, whether GPTBot, OAI-SearchBot, ChatGPT-User, ClaudeBot, Claude-SearchBot, Claude-User, PerplexityBot, Google-Extended, Googlebot, Bingbot, Applebot-Extended and CCBot are allowed or blocked, naming the exact robots.txt rule responsible. Also checks whether content is served in HTML rather than requiring JavaScript, whether structured data is present and valid, and whether llms.txt exists. It does NOT determine whether an assistant will rank, select, mention or cite the page: access is a precondition for citation, not a cause of it, and the crawlers serve different purposes — for OpenAI, OAI-SearchBot governs eligibility for ChatGPT search while GPTBot relates to model training. Use this to rule out or confirm a technical blocker, and say plainly that ranking and selection are outside what any measurement here can establish.
what_changedRe-audit a site and report what moved since it was last checked: which findings are new, which were resolved, and how each category score shifted. Use it after the user says they fixed something, or to verify that a deployment did not regress anything. Returns comparable=false when the site has no earlier snapshot, which is not an error — it means history starts now. Unlike the other tools this one WRITES: it stores a durable snapshot of the result, because a comparison against history requires contributing to it. The baseline is the most recent retained snapshot and snapshots are kept at most once per site per six hours, so baselineAt may not be the deployment immediately before this one — read baselineAt rather than assuming it is the last change. Check comparable before attributing any score movement to the site: when the ruleset differed between the two measurements it is false, and the difference then includes a change in grading rather than a change in the website.
get_site_inventoryReturn a complete inventory of what the Outrings collector observed on a page — not a sample of it — for one kind of thing: internal links, external links, sitemap URLs, email addresses, scripts, images, forms, iframes, stylesheets or API endpoints referenced. The collector does not execute JavaScript, so this is everything present in the served HTML and the responses it fetched, which is not necessarily everything a real browser would end up loading at runtime. Use it for "what third-party scripts am I loading", "which email addresses are exposed on my site", "how many images are missing alt text", "what does my page link out to".
compare_websitesScore two to four sites and return them ranked, with the category gaps between them. Use it for "how do I compare to my competitors" or "which of these is better built". Each site is a real audit, so this takes several seconds per URL.
get_badge_embedProduce the HTML (and Markdown) for a badge the site owner can paste into their footer or README. It renders a live SVG showing a real measured score that refreshes every six hours and links through to the full audit, so a visitor can verify it. Use this when someone wants to display that their site was checked.