lintlab SEO Site QA

io.github.lintlabPublished by GitHub account lintlabv1.0.0Updated Oct 25, 2026

Crawl a site for broken links, redirects and missing SEO tags. Pay per page on Apify.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant crawl a site and report broken links, redirects and missing SEO tags.

What you can do
Crawl a website and check it for broken links and redirects, reporting what it finds back to the assistant. Inspect pages for missing SEO tags so the assistant can flag gaps. Runs are executed on Apify and billed per page.
When to use it
Useful when you want an assistant to audit a site's link health and basic on-page SEO without building your own crawler, for example before a launch or during routine site maintenance.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is needed, authenticated either with an Apify API token sent as a Bearer token in the Authorization header or through Apify OAuth if the client supports it. Network access to Apify is required.
Before you install
Runs are billed to your Apify account on a pay-per-page basis, so crawling large sites can cost money. The Authorization header carries an Apify API token, which should be kept secret. Crawl results are processed by Apify as a third party.

Installation

In SourceWeft

  1. Open lintlab SEO Site QA in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.lintlab%2Fseo-site-qa/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "lintlab-seo-site-qa": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=lintlab/seo-site-qa"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestSep 26, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.