lintlab Sitemap Validator

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

Find, validate and extract XML sitemaps (gzip, indexes) with lastmod. Pay per result on Apify.

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingDeveloper Tools

Overview

AI-generated overview

A remote Apify-hosted MCP server that lets an assistant find, validate and extract XML sitemaps, including gzip files and sitemap indexes, with lastmod data.

What you can do
Find XML sitemaps for a site and check whether they are valid, including gzip-compressed files and sitemap indexes. Extract sitemap entries together with their lastmod values. Runs are executed on Apify and billed per result.
When to use it
Useful when auditing a site's sitemap setup, checking that sitemap files and indexes are valid, or pulling URL and lastmod lists from sitemaps for SEO or crawling work.
Requirements
A remote MCP endpoint at mcp.apify.com over streamable HTTP. An Apify account is needed; authentication uses an Apify API token sent as a Bearer token in the Authorization header, or Apify OAuth if the client supports it. Network access is required.
Before you install
Runs are billed to your Apify account on a pay-per-result basis, so usage costs money. The Authorization header carries your Apify API token, a secret that should be kept private. Sitemap fetching sends the target site's address to Apify's service.

Installation

In SourceWeft

  1. Open lintlab Sitemap Validator 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%2Fsitemap-doctor/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-sitemap-validator": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=lintlab/sitemap-doctor"
    }
  }
}

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.