Apify Site audit

io.github.AHMEDFOUAADPublished by GitHub account AHMEDFOUAADv1.0.0Updated Nov 11, 2026

Sitemap URL extraction, bulk URL status / broken-link checks and dataset dedup via Apify.

The publisher's own server: audit.domains - Domain Valuation

VerifiedStreamable HTTPWeb executableWeb Search & ScrapingData & Analytics

Overview

AI-generated overview

Apify-hosted MCP preset that gives an assistant three public-web site-audit tools: sitemap URL extraction, bulk link/status checks and dataset dedup.

What you can do
  • Extract URLs from a site's sitemap into structured JSON
  • Check many URLs in bulk for status codes and broken links
  • Deduplicate and merge result datasets
  • Inspect and manage the resulting Actor runs and datasets through the standard Apify run and dataset helpers
When to use it
Useful when you want an assistant to audit a site's sitemap and links, or clean up scraped URL lists, without loading the whole Apify Store tool set. Suited to recurring public-web checks where pay-per-result billing is acceptable.
Requirements
Remote endpoint at mcp.apify.com with the bundle's tools parameter. Requires an Apify account and authentication: OAuth sign-in, or an Apify API token sent as a Bearer token in the Authorization header. Runs bill to your own Apify account.
Before you install
Runs are paid per result and bill to your Apify account (a free slice of results per run applies; the free plan includes limited monthly credit). Keep the Apify token secret and never commit it. The Actors are published and sold by the repo author, who is not affiliated with Apify. Only public pages are read.

Installation

In SourceWeft

  1. Open Apify Site audit 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.AHMEDFOUAAD%2Fapify-site-audit/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": {
    "apify-site-audit": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=ahmed.fouaad82/sitemap-extractor,ahmed.fouaad82/url-status-checker,ahmed.fouaad82/dataset-dedup-merge"
    }
  }
}

README

Apify MCP data presets for AI agents

Copy-paste MCP configs that give Claude Desktop, Cursor, VS Code (Copilot) or Claude Code a small, focused set of public-web-data tools instead of the whole Apify Store. Each bundle points the official hosted Apify MCP server at three specific Actors using its documented ?tools= URL parameter, so the agent sees exactly three dedicated tools plus the run/dataset helpers.

Disclosure: I (GitHub @AHMEDFOUAAD, Apify user ahmed.fouaad82) built and sell these Actors on Apify Store. They are paid per result (pay-per-event). The first results of every run are free (25 for most of these Actors; see each Store page's Pricing tab), then the listed price applies. You need your own Apify account (OAuth sign-in or your own API token); runs bill to your account, and Apify's free plan includes $5/month of usage. This repo only contains client configs: it is not affiliated with or endorsed by Apify.

BundleActorsEndpoint
Public job boards (Greenhouse, Lever, multi-ATS)greenhouse-public-jobs, lever-salary-jobs, ats-public-jobshttps://mcp.apify.com/?tools=ahmed.fouaad82/greenhouse-public-jobs,ahmed.fouaad82/lever-salary-jobs,ahmed.fouaad82/ats-public-jobs
Content for RAG (RSS, podcast transcripts, PDF text)rss-feed-reader, podcast-published-transcripts, public-pdf-texthttps://mcp.apify.com/?tools=ahmed.fouaad82/rss-feed-reader,ahmed.fouaad82/podcast-published-transcripts,ahmed.fouaad82/public-pdf-text
Site audit (sitemap URLs, link/status checks, dedup)sitemap-extractor, url-status-checker, dataset-dedup-mergehttps://mcp.apify.com/?tools=ahmed.fouaad82/sitemap-extractor,ahmed.fouaad82/url-status-checker,ahmed.fouaad82/dataset-dedup-merge

Each bundle folder has: cursor.mcp.json, vscode.mcp.json, token variants, claude_desktop_config.json (stdio bridge via mcp-remote) and a server.json (official MCP Registry entry).

Why presets?

  • Fewer, sharper tools. A preselected endpoint exposes only the tools for one job, which keeps the agent's tool list short and its choices predictable (Apify recommends pinning tools in production).
  • Fresh public data. Job boards, feeds, transcripts, PDFs, sitemaps and link status, fetched at run time, returned as structured JSON.
  • Pay per result. No subscription for these Actors; the first results of every run are free.

Verified

On 2026-11-11 the three endpoints were initialized against https://mcp.apify.com (server apify-mcp-server 0.21.5) and tools/list returned the expected tools, for example for the jobs bundle:

text
ahmed-dot-fouaad82--greenhouse-public-jobsahmed-dot-fouaad82--lever-salary-jobsahmed-dot-fouaad82--ats-public-jobsget-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run

The jobs bundle's claude_desktop_config.json was also run as-is through npx mcp-remote@latest (stdio bridge, Node 22): initialize and tools/list returned the same 7 tools.

A real tool call (ahmed-dot-fouaad82--rss-feed-reader, 3 items from the Hacker News RSS feed) returned SUCCEEDED with 3 dataset rows and 0 charged results (free slice). Re-run the check yourself with scripts/check_preset.py.

Notes from that test:

  • Endpoints that preload an Actor require authentication (OAuth or token); without it the server answers HTTP 401. Only discovery tools (search-actors, fetch-actor-details, docs) work anonymously.
  • OAuth sign-in was not exercised by the script (it used a token header); OAuth is the method Apify documents as recommended.

Security

  • Never commit your Apify token. The token variants read it from an environment variable or a secure prompt.
  • The Actors only read public pages (no logins, no private data). Each Store page documents its sources and robots/ToS limits.

Licence

MIT for the configs and script in this repo. The Actors are separate paid products on Apify Store.

Source: README.md at commit e6e1639

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.0LatestNov 11, 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 Audit integrations