# Crawlgraph (npm · @pipeworx/mcp-crawlgraph)

CrawlGraph MCP — backlink intelligence on the public Common Crawl webgraph (4.4B edges, 120M…

- Trust score: 83/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `gateway.pipeworx.io`: 77/100, [markdown](https://verifymcp.io/servers/pipeworx-io-crawlgraph/crawlgraph-mcp.md), [page](https://verifymcp.io/servers/pipeworx-io-crawlgraph/crawlgraph-mcp)
- npm · `@pipeworx/mcp-crawlgraph`: 83/100 (this document), [markdown](https://verifymcp.io/servers/pipeworx-io-crawlgraph/pipeworx-mcp-crawlgraph.md), [page](https://verifymcp.io/servers/pipeworx-io-crawlgraph/pipeworx-mcp-crawlgraph)

## Channel facts

- Registry: `npm`
- Package: `@pipeworx/mcp-crawlgraph`
- Version: `0.2.1`
- Transport: `stdio`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, 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-11-05.

- **Supply Chain Security**: 100/100
  - No malware found by supply-chain analysis.
  - No known CVEs affecting this package version or its production dependencies.
  - No install/post-install scripts declared.
  - No production dependencies, so there is no dependency health to assess.
- **Provenance & Transparency**: 97/100
  - Source repository is publicly reachable at the declared URL.
  - Cryptographically verified build provenance (signed, bound to pipeworx-io/mcp-crawlgraph).
  - Clear OSI-approved license (MIT).
  - Actively maintained (last published 4 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 864 tokens (~144/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 23/100
  - Stability observed for 7 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Crawlgraph MCP server?

Crawlgraph runs locally as an npm package, launched with npx -y @pipeworx/mcp-crawlgraph. 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 pipeworx-io-crawlgraph -- npx -y @pipeworx/mcp-crawlgraph
```

### Cursor

```json
{
  "mcpServers": {
    "pipeworx-io-crawlgraph": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crawlgraph"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "pipeworx-io-crawlgraph": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crawlgraph"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add pipeworx-io-crawlgraph -- npx -y @pipeworx/mcp-crawlgraph
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "pipeworx-io-crawlgraph": {
      "type": "local",
      "command": [
        "npx",
        "-y",
        "@pipeworx/mcp-crawlgraph"
      ],
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add pipeworx-io-crawlgraph --command npx --arg -y --arg @pipeworx/mcp-crawlgraph
```

### Hermes

```yaml
mcp_servers:
  pipeworx-io-crawlgraph:
    command: "npx"
    args: ["-y", "@pipeworx/mcp-crawlgraph"]
```

### Netclaw

```json
{
  "McpServers": {
    "pipeworx-io-crawlgraph": {
      "Transport": "stdio",
      "Command": "npx",
      "Arguments": [
        "-y",
        "@pipeworx/mcp-crawlgraph"
      ]
    }
  }
}
```

### Vellum

```bash
assistant mcp add pipeworx-io-crawlgraph -t stdio -c npx -a -y @pipeworx/mcp-crawlgraph
```

### Other

```json
{
  "mcpServers": {
    "pipeworx-io-crawlgraph": {
      "command": "npx",
      "args": [
        "-y",
        "@pipeworx/mcp-crawlgraph"
      ]
    }
  }
}
```

## 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-11-03 (score 83, +1)

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

### 2026-11-01 (score 82, +27)

- [security improvement] Known CVEs: unverified → pass
- [security improvement] Malware scan: unverified → pass
- [functional improvement] Dependency health: unverified → pass

### 2026-10-31 (score 55, −26)

- [security regression] Known CVEs: pass → unverified
- [security regression] Malware scan: pass → unverified
- [functional regression] Dependency health: pass → unverified
- [functional] Package version: 0.2.0 → 0.2.1

### 2026-10-30 (score 81, +1)

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

### 2026-10-29 (score 80)

First indexed and scored.

## MCP tools (6)

### `crawlgraph_backlinks` (~203 tokens)

Referring domains for a target domain from the Common Crawl webgraph (4.4B edges, 120M domains). Returns linking domains ranked by CrawlGraph authority — useful for SEO audits, competitor backlink profiles, link-building gap research, and verifying who is citing a brand. One call = one quota credit.

Input parameters:

- `_apiKey` (string, required): CrawlGraph API key (cg_live_… Bearer token).
- `domain` (string, required): Target domain to look up (e.g., "example.com"). Bare host, no scheme.
- `limit` (number): Max linking domains to return (default 1000, max 10000).
- `release_id` (string): Optional Common Crawl release (e.g., "CC-MAIN-2026-04"). Default = latest. Use crawlgraph_releases to list.
- `sort` (string): Sort by "authority" (default) or "hosts" (number of distinct linking hosts).

### `crawlgraph_gap_analysis` (~145 tokens)

Backlink gap analysis: find domains linking to your competitors but NOT to you. Submit your domain + 1–5 competitor domains and CrawlGraph runs an async job (typically completes in seconds; longer for large profiles). This tool polls up to ~10s and either returns the full gap list, or — if still running — returns the job_id so you can resume via crawlgraph_gap_status. Counts against the gap-analysis quota when the job is submitted.

Input parameters:

- `_apiKey` (string, required): CrawlGraph API key.
- `competitor_domains` (array, required): 1–5 competitor domains to compare against.
- `my_domain` (string, required): Your domain (bare host).

### `crawlgraph_gap_outreach_targets` (~176 tokens)

The warm-outreach play: gap_analysis filtered to ONLY the linking domains that link to EVERY competitor you listed but not to you. These are the highest-conviction outreach candidates — every competitor in the set has the link, so the topic/audience is verified. Same async pattern as crawlgraph_gap_analysis (polls up to ~10s; returns job_id if still running). Counts as one gap-analysis quota call.

Input parameters:

- `_apiKey` (string, required): CrawlGraph API key.
- `competitor_domains` (array, required): 2–5 competitor domains. The filter is strongest with more competitors; 2 is the minimum for "warm outreach" to be meaningful.
- `min_authority` (number): Optional minimum CrawlGraph authority threshold to filter results client-side.
- `my_domain` (string, required): Your domain.

### `crawlgraph_gap_status` (~103 tokens)

Poll a previously-submitted gap analysis job by ID. Use this when crawlgraph_gap_analysis or crawlgraph_gap_outreach_targets returned status=pending with a job_id — call this with the same job_id to retrieve the result once status=completed. Read-only; no quota cost.

Input parameters:

- `_apiKey` (string, required): CrawlGraph API key.
- `job_id` (string, required): The gap job ID (looks like "gap_a1b2c3").

### `crawlgraph_releases` (~47 tokens)

List the Common Crawl releases CrawlGraph has indexed (used as release_id in backlinks). Free; not counted against quota.

Input parameters:

- `_apiKey` (string, required): CrawlGraph API key.

### `crawlgraph_domain_changes` (~137 tokens)

Quarter-over-quarter diff of referring domains for a domain — what was added or lost between two Common Crawl releases. Useful for catching link rot, sudden spikes (PR coverage), and outreach campaign attribution. Counts as one call against the backlinks quota.

Input parameters:

- `_apiKey` (string, required): CrawlGraph API key.
- `domain` (string, required): Target domain.
- `from` (string): Older release_id (e.g., "CC-MAIN-2025-51"). Default = previous release.
- `to` (string): Newer release_id (e.g., "CC-MAIN-2026-04"). Default = latest release.

## Diagnostics

Captured diagnostic sections: Provenance, Dependencies. The full working is on the page: https://verifymcp.io/servers/pipeworx-io-crawlgraph/pipeworx-mcp-crawlgraph#diagnostics

## Score history

- 2026-11-05: 83
- 2026-11-04: 83
- 2026-11-03: 83
- 2026-11-02: 82
- 2026-11-01: 82
- 2026-10-31: 55
- 2026-10-30: 81
- 2026-10-29: 80

## Common questions

### What is the Crawlgraph MCP server?

Crawlgraph is an MCP server listed in the public MCP registry as io.github.pipeworx-io/crawlgraph. CrawlGraph MCP, backlink intelligence on the public Common Crawl webgraph (4.4B edges, 120M… This page covers its npm package (@pipeworx/mcp-crawlgraph).

### Is the Crawlgraph MCP server safe to use?

Crawlgraph scores 83 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. Its build provenance is signed and verified. 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 Crawlgraph MCP server expose?

Crawlgraph exposes 6 tools: crawlgraph_backlinks, crawlgraph_gap_analysis, crawlgraph_gap_outreach_targets, crawlgraph_gap_status, crawlgraph_releases, crawlgraph_domain_changes. Their descriptions and schemas cost roughly 811 tokens of context every time the server is loaded.

### Is the Crawlgraph MCP server still maintained?

Crawlgraph is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What licence is the Crawlgraph MCP server under?

Crawlgraph declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.

## Links

- npm package: https://www.npmjs.com/package/@pipeworx/mcp-crawlgraph
- Socket report: https://socket.dev/npm/package/@pipeworx/mcp-crawlgraph
- Repository: https://github.com/pipeworx-io/mcp-crawlgraph
- Website: https://pipeworx.io/packs/crawlgraph
- Changelog RSS feed: https://verifymcp.io/servers/pipeworx-io-crawlgraph/pipeworx-mcp-crawlgraph.xml
- Changelog JSON feed: https://verifymcp.io/servers/pipeworx-io-crawlgraph/pipeworx-mcp-crawlgraph.json
- HTML version of this page: https://verifymcp.io/servers/pipeworx-io-crawlgraph/pipeworx-mcp-crawlgraph