Tor Hidden Service Crawler & Contact Extractor: MCP config, n8n workflow and API

{
  "mode": "directories",
  "source": "onionTree",
  "maxResultsPerQuery": 3,
  "maxItems": 3,
  "maxPages": 1,
  "verifyLiveness": false,
  "livenessTimeoutSecs": 8,
  "includeUnreachable": true,
  "extractEmails": false,
  "extractPhones": false,
  "extractSocialHandles": false,
  "extractPgpContacts": false
}

---
name: tor-hidden-service-crawler-and-contact-extractor
description: "One dataset of public onion directory entries and Ahmia index-result metadata, with provenance, neutral categories, PGP contact fields and optional measured liveness. Runs the Apify Actor xyrelith-data/tor-hidden-service-crawler-and-contact-extractor. Use when the user needs Tor Hidden Service data with fields such as name, onionUrl, categories, source, status, description and an Apify token is available."
compatibility: "Needs network access, curl, and an APIFY_TOKEN environment variable. Runs are billed to the token owner's Apify account."
metadata:
  actor: "xyrelith-data/tor-hidden-service-crawler-and-contact-extractor"
  store-url: "https://apify.com/xyrelith-data/tor-hidden-service-crawler-and-contact-extractor"
---

# Tor Hidden Service Crawler & Contact Extractor

Use this skill to fetch Tor Hidden Service data with the Apify Actor `xyrelith-data/tor-hidden-service-crawler-and-contact-extractor` and work with the returned rows.

## Before running

1. Check that `APIFY_TOKEN` is set in the environment. Never print it or write it to a file.
2. Build `input.json` from the user's request using the fields below. Keep limits small for a first run.
3. Confirm the search terms or URLs with the user if the request is ambiguous.

## Input fields

| Field | Type | Meaning |
| --- | --- | --- |
| `mode` | one of `directories`, `search`, `byUrls`, `crawl`, `searchAndCrawl`, required | What to collect. `directories` aggregates public onion directory entries; `search` returns Ahmia index-result metadata; `byUrls` reads directory pages you supply. Legacy `crawl` and `searchAndCrawl` values are accepted and mapped in code. |
| `source` | one of `all`, `onionTree`, `darkFail`, `torTaxi` | Directory aggregation source (mode=directories). `all` merges OnionTree, dark.fail and tor.taxi. |
| `categories` | array | Keep OnionTree entries matching any selected category (mode=directories). |
| `searchQueries` | array | One or more keywords to query against the Ahmia index (mode=search). Each query is one request; result pages are never opened. |
| `maxResultsPerQuery` | integer | Cap on Ahmia rows per query (mode=search). The global maxItems cap still applies. |
| `startUrls` | array | Clearnet or v3 onion directory/index pages to read (mode=byUrls). Only entry links and adjacent structured contact links are parsed; linked onion pages are not opened. |
| `maxItems` | integer | Hard cap on records emitted to the dataset. |
| `maxPages` | integer | Maximum directory pages fetched in mode=byUrls. |
| `verifyLiveness` | boolean | Fetch each unique onion domain once through Tor and fill measured status, HTTP code, page title and check time. Applies to directories and byUrls; search mode never opens result pages. |
| `livenessTimeoutSecs` | integer | Per-domain timeout for the optional Tor liveness check. |
| `includeUnreachable` | boolean | When liveness is enabled, keep entries measured as timeout or unreachable. Applies only when verifyLiveness is true. |
| `extractEmails` | boolean | Include structured emails from OnionTree PGP user IDs and explicit mailto: links on directory pages. No free-text email mining. |
| `extractPhones` | boolean | Include phone numbers from explicit tel: links on directory pages only. No free-text phone mining. |
| `extractSocialHandles` | boolean | Include handles from explicit X/Twitter, Instagram and Telegram profile links on directory pages only. |

Example `input.json` (the Actor's published prefill):

```json
{
  "mode": "directories",
  "source": "onionTree",
  "maxResultsPerQuery": 3,
  "maxItems": 3,
  "maxPages": 1,
  "verifyLiveness": false,
  "livenessTimeoutSecs": 8,
  "includeUnreachable": true,
  "extractEmails": false,
  "extractPhones": false,
  "extractSocialHandles": false,
  "extractPgpContacts": false
}
```

## Run

```bash
curl -sS -X POST "https://api.apify.com/v2/acts/xyrelith-data~tor-hidden-service-crawler-and-contact-extractor/run-sync-get-dataset-items" \
  -H "Authorization: Bearer $APIFY_TOKEN" \
  -H "Content-Type: application/json" \
  -d @input.json > results.json
```

The call waits for the run to finish and returns the dataset items as a JSON array. If the run needs more than 300 seconds the API answers with HTTP 408; then start the run with `POST /v2/acts/xyrelith-data~tor-hidden-service-crawler-and-contact-extractor/runs`, poll `GET /v2/actor-runs/{runId}` until `SUCCEEDED`, and read `GET /v2/datasets/{defaultDatasetId}/items`.

## Output

Each item is one record. Published fields include: `name`, `onionUrl`, `categories`, `source`, `status`, `description`.

Summarise what was found, cite the record URLs when present, and say how many items came back. Do not invent values for empty fields.