Sitemap URL Health Checker (via Apify MCP)

io.github.lineagersiui-boop由 GitHub 账号 lineagersiui-boop 发布v1.0.0更新于 Oct 30, 2026

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

发布方自己的服务:Apify MCP Server

已验证Streamable HTTP可网页运行网页搜索与抓取安全与监控

概览

AI 生成的概览

由 Apify 托管的 MCP 工具,检查网站 XML 站点地图中的每个 URL 是否存在 404、重定向、HTTPS 降级和 noindex 头。

可以做什么
  • 根据域名通过 robots.txt 或 /sitemap.xml 查找站点地图,也可直接传入站点地图、索引、.xml.gz 或纯文本列表 URL。
  • 逐个请求列出的 URL,报告状态码、重定向、重定向链、最终 URL 和标记。
  • 标记 404/4xx/5xx、重定向过多、https 跳转到 http 以及 X-Robots-Tag noindex 等问题。
  • 每个 URL 输出一条数据集记录,并在 SUMMARY 记录中汇总发现、已检查、计费、问题、被 robots 拦截和出错的 URL 数量。
适用场景
适合在网站迁移、更换域名或批量修改内容后,确认站点地图中的 URL 仍可访问且可被索引。也适合对你有权测试的网站做定期 SEO 健康检查。
运行要求
使用 Apify 托管的远程 MCP 端点,并通过 tools 参数只加载该 Actor。需要自己的 Apify 账号和 API 令牌,以 Authorization Bearer 头发送,或在支持时使用 OAuth 登录。本地 npx 方式使用 APIFY_TOKEN 环境变量。非演示运行需将 confirmPermission 设为 true。
安装前请注意
运行费用计入你的 Apify 账号,按每个检查的 URL 0.0005 美元加 Apify 平台用量计费;被 onlyProblems 过滤掉的 URL 仍会计费。该列表作者维护此 Actor 并从中获得费用,端点由 Apify 而非作者运营。只检查站点地图中列出的 URL,不抓取页面内链接。你必须有权检查目标网站。

安装

在 SourceWeft 中

  1. 打开 控制台中的 Sitemap URL Health Checker (via Apify MCP),将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储,绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable,通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体,或 SourceWeft 对话中。智能体会读取该服务器的安装指南,先向你展示发布者、端点和登录方式,经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/io.github.lineagersiui-boop%2Fsitemap-url-health-checker/install.md,并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前,先告诉我它的发布者、端点和登录方式,等我确认。不要把 API 密钥写进命令或我会提交的文件;问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "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.

来源:mcp/sitemap-url-health-checker/README.md,提交 a7bc96e

工具

0
该服务器需要登录,因此 SourceWeft 无法在没有账号的情况下读取其工具,也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

1
  1. v1.0.0最新Oct 30, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度,依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价,也不表示服务器安全或当前可用:可连通性是带日期的检查结果,评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list,或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分

其他 Apify 集成