Sitemap URL Health Checker (via Apify MCP)

io.github.lineagersiui-boopPublished by GitHub account lineagersiui-boopv1.0.0Updated Oct 30, 2026

Check sitemap URLs for 404s, redirects and noindex. One Apify Actor via Apify's hosted MCP server.

The publisher's own server: Apify MCP Server

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Apify-hosted MCP tool that checks every URL in a site's XML sitemap for 404s, redirects, HTTPS downgrades and noindex headers.

What you can do
  • Find a site's sitemap from a domain via robots.txt or /sitemap.xml, or take direct sitemap, sitemap-index, .xml.gz or plain-text list URLs.
  • Request each listed URL and report status, redirects, redirect chains, final URL and flags.
  • Flag problems such as 404/4xx/5xx, too many redirects, https-to-http downgrades and X-Robots-Tag noindex.
  • Return one dataset item per URL plus a SUMMARY record with counts of found, checked, billed, problem, robots-blocked and errored URLs.
When to use it
Useful after a site migration, domain change or bulk content edit, when you want to confirm that sitemap URLs still resolve and are indexable. Also handy for periodic SEO hygiene checks on sites you are permitted to test.
Requirements
A remote MCP endpoint at Apify's hosted server, with the tools parameter selecting this Actor. Needs your own Apify account and API token, sent as an Authorization Bearer header, or OAuth sign-in where supported. A local npx fallback uses the APIFY_TOKEN environment variable. Non-demo runs require confirmPermission set to true.
Before you install
Runs are billed to your Apify account at $0.0005 per URL checked plus Apify platform usage; URLs filtered out by onlyProblems are still billed. The listing author maintains the Actor and earns its fees, and the endpoint is run by Apify, not the author. Only sitemap-listed URLs are checked, not links inside pages. You must have permission to check the target site.

Installation

In SourceWeft

  1. Open Sitemap URL Health Checker (via Apify MCP) 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.lineagersiui-boop%2Fsitemap-url-health-checker/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": {
    "sitemap-url-health-checker-via-apify": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=lineagersiui/sitemap-url-health-checker"
    }
  }
}

README

Sitemap URL Health Checker: MCP server (via Apify)

Check every URL listed in a website's XML sitemap for 404s, server errors, redirects, redirect chains, https-to-http downgrades and X-Robots-Tag: noindex headers, from any MCP client.

Disclosure: we built and maintain the Apify Actor lineagersiui/sitemap-url-health-checker and earn its pay-per-event fees. This listing is not affiliated with or endorsed by Apify or the Model Context Protocol project. The MCP endpoint is Apify's hosted MCP server (mcp.apify.com), run by Apify, not by us. This listing only preselects our Actor as the single tool. Drafted with AI tools under the author's direction.

Registry name: io.github.lineagersiui-boop/sitemap-url-health-checker

What it does

  • Finds the sitemap from a site address (via robots.txt or /sitemap.xml), or takes direct sitemap, sitemap-index, .xml.gz or plain-text list URLs.
  • Requests each listed URL and reports its status, redirects, final URL and flags.
  • Checks only URLs listed in the sitemap. It does not crawl links inside pages.

Requirements

  • Your own Apify account and API token. Get the token in Apify Console → Settings → API & Integrations. Runs are billed to your Apify account, not ours.
  • Permission to check the site. The Actor refuses non-demo runs unless confirmPermission is true.

Pricing

  • $0.0005 per URL checked (one event per URL that returns an HTTP status). 1,000 URLs cost $0.50, plus Apify platform usage.
  • Not billed: URLs skipped by robots.txt, timeouts and network errors.
  • Free demo: run with empty input to check 20 URLs of apify.com, not billed.

Connect

Endpoint (Streamable HTTP):

https://mcp.apify.com/?tools=lineagersiui/sitemap-url-health-checker

The tools parameter makes Apify's server load only this Actor. Without it, Apify's server loads its default tool set instead.

Bearer token (most clients):

json
{  "mcpServers": {    "sitemap-url-health-checker": {      "url": "https://mcp.apify.com/?tools=lineagersiui/sitemap-url-health-checker",      "headers": { "Authorization": "Bearer <YOUR_APIFY_TOKEN>" }    }  }}

Apify's server also supports OAuth sign-in, without a token in the config, for clients that support it. See Apify's MCP documentation.

Local stdio, for clients without remote support. This runs Apify's own open-source package, not ours:

json
{  "mcpServers": {    "sitemap-url-health-checker": {      "command": "npx",      "args": ["-y", "@apify/actors-mcp-server", "--tools", "lineagersiui/sitemap-url-health-checker"],      "env": { "APIFY_TOKEN": "<YOUR_APIFY_TOKEN>" }    }  }}

Input

FieldTypeNotes
siteUrlsarray of stringsSite addresses, e.g. example.com. Up to 10
sitemapUrlsarray of stringsDirect sitemap, sitemap-index, .xml.gz or plain-text list URLs. Up to 10
confirmPermissionbooleanDefault false. Must be true for non-demo runs
maxUrlsintegerDefault 500, range 1 to 5,000. Hard cap per run
onlyProblemsbooleanDefault false. Leaves out 2xx URLs with no redirect (they are still billed)
timeLimitSecsintegerDefault 1,500, range 60 to 3,600. No new checks start after this

Output

One dataset item per URL: url, status, flags, redirects, redirectStatuses, finalUrl, lastmod, sitemap. The key-value store record SUMMARY holds the counts: urlsFound, checked, billed, problems, blockedByRobots, errors.

FlagMeaning
not_found, client_error, server_error404/410, another 4xx, or 5xx
redirected, redirect_chain, too_many_redirectsOne redirect, more than one, or more than 5
https_downgradeAn https URL redirects to http
noindex_headerSends X-Robots-Tag: noindex
blocked_by_robotsDisallowed by robots.txt; skipped, not billed
timeout, network_error, blocked_private_addressCouldn't be checked; not billed
ok2xx, no redirect

Example prompts

  • "Check the sitemap of example.com for broken links and redirects. I own the site."
  • "Which URLs in https://example.com/sitemap_index.xml return 404 or redirect after our migration?"
  • "Which pages in our sitemap send a noindex header?"

Support

Open an issue in this repository. The Actor is maintained by its author on the Apify Store.

License

This README and server.json are MIT-licensed. The Actor and Apify's MCP server have their own terms.

Source: mcp/sitemap-url-health-checker/README.md at commit a7bc96e

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.0LatestOct 30, 2026

Score

85% 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
  • License10 pts

Other Apify integrations