# Sitemap URL Extractor for AI Agents (remote · mcp.apify.com)

x402 sitemap discovery and URL extraction for agents. $0.0001 per emitted URL.

- Trust score: 71/100 (medium)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-10-18

## Components

- remote · `mcp.apify.com`: 71/100 (this document), [markdown](https://verifymcp.io/servers/industrial-platform-ai-sitemap/mcp-2.md), [page](https://verifymcp.io/servers/industrial-platform-ai-sitemap/mcp-2)

## Channel facts

- Endpoint: `https://mcp.apify.com?tools=industrial_platform/sitemap-intelligence&payment=x402`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.2`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-10-18.

- **Endpoint Security**: 60/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation check failed: no authorisation is required to call this server, and it exposes a tool marked destructive (industrial_platform--sitemap-intelligence).
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 61/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1940 tokens (~388/item across 5 items; 5 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 60/100
  - Stability observed for 18 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

## Install

### How do I install the Sitemap URL Extractor for AI Agents MCP server?

Sitemap URL Extractor for AI Agents is a hosted endpoint at https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http industrial-platform-ai-sitemap 'https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402'
```

### Cursor

```json
{
  "mcpServers": {
    "industrial-platform-ai-sitemap": {
      "url": "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "industrial-platform-ai-sitemap": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402"
    }
  }
}
```

### Codex

```toml
[mcp_servers.industrial-platform-ai-sitemap]
url = "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "industrial-platform-ai-sitemap": {
      "type": "remote",
      "url": "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add industrial-platform-ai-sitemap --url 'https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  industrial-platform-ai-sitemap:
    url: "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402"
```

### Netclaw

```json
{
  "McpServers": {
    "industrial-platform-ai-sitemap": {
      "Transport": "http",
      "Url": "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402"
    }
  }
}
```

### Vellum

```bash
assistant mcp add industrial-platform-ai-sitemap -t streamable-http -u 'https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402'
```

### Other

```json
{
  "mcpServers": {
    "industrial-platform-ai-sitemap": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-10-17 (score 71, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional] Server version: 0.18.3 → 0.18.4

### 2026-10-16 (score 70, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [functional improvement] Schema quality: 459 → 391
- [functional] Server version: 0.18.2 → 0.18.3

### 2026-10-15 (score 70, 0)

- [functional] Server version: 0.18.0 → 0.18.2

### 2026-10-14 (score 70, +1)

- [functional] Server version: 0.17.4 → 0.18.0

### 2026-10-12 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 33 to 40. That category is still filling its 30-day observation window: 10 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-10 (score 68, +2)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 33. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-07 (score 66, +1)

- [functional] Server version: 0.17.2 → 0.17.3

### 2026-10-03 (score 65, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (5)

### `industrial_platform--sitemap-intelligence` (~286 tokens)

industrial_platform/sitemap-intelligence

This tool calls the Actor "industrial_platform/sitemap-intelligence" and retrieves its output results.
Actor description: Discover and expand sitemaps into crawl URLs. Price: $0.0001 per emitted URL.

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Input parameters:

- `max_sitemaps` (integer): Maximum sitemap and sitemap-index documents processed during one run. Example values: 100
- `max_urls` (integer): Maximum unique URL rows emitted and charged during one run. Example values: 50000
- `start_urls` (array, required): **REQUIRED** Domains, website URLs, or direct sitemap URLs. Domains use robots.txt discovery plus /sitemap.xml fallback. Example values: ["https://www.google.com/gmail/sitemap.xml"]
- `timeout_seconds` (integer): Maximum time allowed for each robots.txt or sitemap request. Example values: 30
- `waitSecs` (integer): Max seconds (0–45, default 30) to cap the wait for the Actor run to reach terminal state. For long-running Actors the response returns at the cap with the current run status; follow `nextStep` to pol…

### `get-actor-run` (~306 tokens)

Get Actor run

Get detailed information about a specific Actor run.

Returns run result: status, storages (datasets/keyValueStores alias map), stats, summary, nextStep.
\- summary describes the past (e.g. "SUCCEEDED in 22s. 47 items; 3 fields available.").
\- nextStep prescribes one primary follow-up action with identifiers interpolated (e.g. "Use get-dataset-items with datasetId=...").
\- waitSecs (0–45, default 30) waits up to that many seconds for terminal status before returning.

USAGE:
\- Use to check the status of a run started by any Actor-running tool.
\- Pass waitSecs > 0 to block until terminal (or until the cap elapses).

USAGE EXAMPLES:
\- user_input: Show details of run y2h7sK3Wc
\- user_input: Wait for run y2h7sK3Wc to finish

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Input parameters:

- `runId` (string, required): The ID of the Actor run.
- `waitSecs` (integer): Maximum seconds to wait for the run to reach a terminal state (SUCCEEDED, FAILED, ABORTED, TIMED-OUT). 0 returns immediately with the current status. Cap: 45. Default: 30.

### `get-dataset-items` (~406 tokens)

Get dataset items

Get items (rows) from a dataset — the output/results produced by an Actor run.
Returns the rows themselves, not dataset metadata, counts, or a schema.
When the user provides a datasetId and asks to retrieve results, output, data, or rows, call this tool directly.
Default limit is 20. Use clean=true to skip empty items and hidden fields.

USAGE:
\- Use when you need to read data from a dataset (all items or only selected fields).

USAGE EXAMPLES:
\- user_input: Retrieve results from dataset abc123
\- user_input: Get only metadata.url and title from dataset username~my-dataset

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Input parameters:

- `clean` (boolean): If true, returns only non-empty items and skips hidden fields (starting with #). Shortcut for skipHidden=true and skipEmpty=true.
- `datasetId` (string, required): Dataset ID or username~dataset-name.
- `desc` (boolean): If true, results are returned in reverse order (newest to oldest).
- `fields` (string): Comma-separated list of fields to include in results. Fields in output are sorted as specified. Use dot notation for nested objects (e.g. "metadata.url"); the server auto-flattens parent prefixes.
- `flatten` (string): Comma-separated list of fields to flatten (e.g. flatten="metadata" turns {"metadata":{"url":"x"}} into {"metadata.url":"x"}). Normally derived automatically from dot-notation in `fields`; specify onl…
- `limit` (integer): Maximum number of items to return. Default is 20.
- `offset` (number): Number of items to skip at the start. Default is 0.
- `omit` (string): Comma-separated list of fields to exclude from results.

### `get-key-value-store-record` (~184 tokens)

Get key-value store record

Get the value stored under a specific key in a key-value store — a single record, not a listing of all keys.
Requires the exact key name.
The response preserves the original Content-Encoding; most clients handle decompression automatically.

USAGE:
\- Use when you need to retrieve a specific record (JSON, text, or binary) from a store.

USAGE EXAMPLES:
\- user_input: Get record INPUT from store abc123
\- user_input: Get record data.json from store username~my-store

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Input parameters:

- `keyValueStoreId` (string, required): Key-value store ID or username~store-name.
- `recordKey` (string, required): Key of the record to retrieve.

### `abort-actor-run` (~198 tokens)

Abort Actor run

Abort an Actor run that is currently starting or running.
For runs with status SUCCEEDED, FAILED, ABORTING, ABORTED, or TIMED-OUT, this call has no effect.
The results will include the updated run details after the abort request.

USAGE:
\- Use when you need to stop a run that is taking too long or misconfigured.

USAGE EXAMPLES:
\- user_input: Abort run y2h7sK3Wc
\- user_input: Gracefully abort run y2h7sK3Wc

This tool requires an x402 payment. Include a valid x402 payment signature in the request metadata (_meta["x402/payment"]). Your MCP client must support the x402 payment protocol.

Input parameters:

- `gracefully` (boolean): If true, the Actor run will abort gracefully with a 30-second timeout.
- `runId` (string, required): The ID of the Actor run to abort.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/industrial-platform-ai-sitemap/mcp-2#diagnostics

## Score history

- 2026-10-18: 71
- 2026-10-17: 71
- 2026-10-16: 70
- 2026-10-15: 70
- 2026-10-14: 70
- 2026-10-13: 69
- 2026-10-12: 69
- 2026-10-10: 68
- 2026-10-07: 66
- 2026-10-04: 65
- 2026-10-03: 65
- 2026-10-02: 64
- 2026-10-01: 64
- 2026-09-30: 63

## Common questions

### What is the Sitemap URL Extractor for AI Agents MCP server?

Sitemap URL Extractor for AI Agents is an MCP server listed in the public MCP registry as io.github.industrial-platform-ai/sitemap. x402 sitemap discovery and URL extraction for agents. $0.0001 per emitted URL. This page covers its hosted endpoint (https://mcp.apify.com?tools=industrial_platform/sitemap-intelligence&payment=x402).

### Is the Sitemap URL Extractor for AI Agents MCP server safe to use?

Sitemap URL Extractor for AI Agents scores 71 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the Sitemap URL Extractor for AI Agents MCP server expose?

Sitemap URL Extractor for AI Agents exposes 5 tools: industrial_platform--sitemap-intelligence, get-actor-run, get-dataset-items, get-key-value-store-record, abort-actor-run. Their descriptions and schemas cost roughly 1,380 tokens of context every time the server is loaded.

### Does the Sitemap URL Extractor for AI Agents MCP server require authentication?

No. We connected to Sitemap URL Extractor for AI Agents without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Sitemap URL Extractor for AI Agents MCP server still maintained?

Sitemap URL Extractor for AI Agents is still listed as active in the MCP registry. We last reached this channel on 18 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://mcp.apify.com/?tools=industrial_platform/sitemap-intelligence&payment=x402
- Repository: https://github.com/industrial-platform-ai/industrial-platform-agent-tools
- Website: https://apify.com/industrial_platform/sitemap-intelligence
- Changelog RSS feed: https://verifymcp.io/servers/industrial-platform-ai-sitemap/mcp-2.xml
- Changelog JSON feed: https://verifymcp.io/servers/industrial-platform-ai-sitemap/mcp-2.json
- HTML version of this page: https://verifymcp.io/servers/industrial-platform-ai-sitemap/mcp-2