MCP.Market

Sitemap Extractor (reliable) MCP server

online · 100% uptime
by jordan-belfort-ai·io.github.jordan-belfort-ai/sitemap-extractor·v1.0.0

Every URL in a site's sitemaps, with lastmod. Runs on Apify, $0.30 per 1,000 URLs.

A93/100grade A
What users say
No reviews yet
Be the first
Safety scan
A93/100

full report

Adoption
Growing

0 stars

Reviews

Write one

Nobody has reviewed Sitemap Extractor (reliable) yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Sitemap Extractor (reliable) tools

Tool list not cached yet. `describe` through the gateway fetches it live.

Public scan report

scanner v0.1.10 · 2026-10-13 · same rubric, same numbers if you re-run it

no findings
  • –Code scanremote-only server, no package to scann/a
  • Live reliabilityremote reachable in 205ms (auth required)20/20
  • –Tool poisoningtools not inspected (endpoint requires auth); not countedn/a
  • Auth qualityOAuth resource metadata advertised on 40115/15
  • Maintenancelast push 0 days ago15/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 93/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Sitemap Extractor (reliable) compares

Against every graded SEO MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
93/100
higher than 90% of 769 SEO servers
Uptime
100%
of our recent checks; the typical remote SEO server answers 100%
Response time
366 ms
faster than 44% of 536 SEO servers

Install Sitemap Extractor (reliable) in Claude Code, Cursor or VS Code

claude mcp add --transport http sitemap-extractor https://mcp.apify.com/?tools=jordan-belfort/sitemap-extractor-reliable
Add to Cursor

What the publisher says

From the Sitemap Extractor (reliable) repository's README, as published. We do not edit it. Read it on GitHub

Sitemap Extractor (reliable)

Give it a domain or a sitemap URL and get every URL the site publishes in its sitemaps, with lastmod, changefreq, priority, hreflang alternates and image counts. One bad sitemap never fails the run: it's logged as an error row, it costs nothing, and the rest of the site still comes through.

Why this one

Apify's own sitemap extractor requests every URL to check its status, on 4 GB of memory. In the 30 days to 11 Oct 2026, 130 of its 411 public runs failed, aborted or timed out. This Actor reads the sitemaps only, unless you ask for status checks, so a typical run finishes in seconds on 256 MB.

What it does

/sitemap.xml, /sitemap_index.xml, /sitemap.xml.gz and /wp-sitemap.xml.

  • Finds the sitemaps for you. Reads Sitemap: lines in robots.txt, then tries

plain-text sitemaps, and XML with unescaped & that strict parsers reject.

  • Follows sitemap indexes to any depth, de-duplicates sitemaps and URLs.
  • Reads every format: XML urlsets, sitemap indexes, gzipped files (.gz or gzip bodies),

https:// (many robots.txt files still list the old scheme).

  • Retries 429 and 5xx responses with backoff, and retries http:// sitemap links over

testing; a 3,000-URL news sitemap took under a second.

  • Filters by include/exclude globs and by lastmod date, so you only pay for what you keep.
  • Plain HTTP, no browser: fast and cheap. A 2,500-URL shop with 175 sitemap files took 39 s in

Input

{
  "startUrls": [{ "url": "https://www.allbirds.com" }],
  "includeGlobs": ["https://www.allbirds.com/products/*"],
  "maxUrls": 5000
}

Output

One dataset row per URL:

{
  "loc": "https://www.allbirds.com/products/womens-wool-runners-savanna-night-navy",
  "lastmod": "2026-10-11T22:35:07-07:00",
  "changefreq": "daily",
  "priority": null,
  "hreflang": [],
  "imageCount": 1,
  "sitemap": "https://www.allbirds.com/sitemap_products_1.xml?from=1878193471557&to=7369944137808",
  "error": null
}

A sitemap that can't be fetched or parsed shows up as a row with loc empty and error set (for example fetch failed: HTTPStatusError: Client error '403 Forbidden'). Run statistics are in the key-value store under STATS.

Price

Pay per result: $0.30 per 1,000 URLs (charged per url event; the best-known alternative charges $0.50 on the free plan). Error rows are free. With the default maxUrls of 1,000, a run never costs more than $0.30 unless you raise the cap.

Uses

SEO audits and content inventories, finding pages changed since a date, seeding a crawler or a RAG pipeline with a site's real URL list, monitoring a competitor's new product pages. Works well as an MCP tool for agents: one call, a clean list of URLs.

Ready-made examples (open one, change the domain, run):

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Sitemap Extractor (reliable): common questions

Is Sitemap Extractor (reliable) MCP server safe?
Yes, by our scan: it is graded A (93/100). Read the Sitemap Extractor (reliable) safety report
How do I install Sitemap Extractor (reliable)?
It runs remotely at mcp.apify.com. Add it to Claude Code, Cursor, VS Code or Claude Desktop with the snippets above, or call it through the mcp.market gateway without installing anything.
Does Sitemap Extractor (reliable) need an API key?
No key to paste: it signs you in with OAuth when your client connects.
Is Sitemap Extractor (reliable) maintained?
The last commit was 22 days ago (2026-10-13). The latest release is v1.0.0.
Is Sitemap Extractor (reliable) up?
100% of our last 28 checks got an answer. We check remote servers about four times a day.
What can I use instead of Sitemap Extractor (reliable)?
Servers from other publishers that do the same job: Google Search Console MCP server, SEO Tools: Google Search Console MCP server and Google Search Console MCP server.
How does Sitemap Extractor (reliable) compare with other SEO MCP servers?
safety score 93/100 (higher than 90% of 769 SEO servers); uptime 100% (of our recent checks; the typical remote SEO server answers 100%); response time 366 ms (faster than 44% of 536 SEO servers). Full comparison.

Alternatives to Sitemap Extractor (reliable)

Same job from other publishers: the closest match first, then the best rated.

  • Google Search Console MCP
    MCP server for the Google Search Console API: search analytics, sitemaps, URL inspection, sites.
    B
  • SEO Tools: Google Search Console
    Google Search Console: Search Analytics, URL Inspection, sitemaps (read-only, OAuth/service acct).
    B
  • Google Search Console
    Google Search Console MCP server — search analytics, URL inspection, and sitemaps
    B
  • Searchdock CLI
    Read-only Google Search Console analytics, URL inspection and sitemaps via SearchDock CLI.
    A
  • Gsc
    MCP server for Google Search Console & Indexing API — search analytics, sitemaps, URL inspection
    B

More from jordan-belfort-ai →