# dev.redirx/redirx (remote · app.redirx.dev)

Map old site URLs to new ones during a migration, review proposals and export approved redirects.

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

## Components

- remote · `app.redirx.dev`: 76/100 (this document), [markdown](https://verifymcp.io/servers/dev-redirx-redirx/app.md), [page](https://verifymcp.io/servers/dev-redirx-redirx/app)

## Channel facts

- Endpoint: `https://app.redirx.dev/mcp`
- Transports: `streamable-http`
- Auth: `required`
- Version: `0.3.0`

## 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-11-06.

- **Endpoint Security**: 78/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation is enforced on tool calls, advertised via RFC 9728 protected-resource metadata. Discovery is public, which costs nothing: no tool can be invoked without a token.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
  - The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 72/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 2198 tokens (~169/item across 13 items; 12 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 82/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 38% of tool parameters carry a description.
  - Structured output schemas are declared (92% 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 12 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 14 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 dev.redirx/redirx MCP server?

dev.redirx/redirx is a hosted endpoint at https://app.redirx.dev/mcp, 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 dev-redirx-redirx 'https://app.redirx.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-redirx-redirx": {
      "url": "https://app.redirx.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-redirx-redirx": {
      "type": "http",
      "url": "https://app.redirx.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-redirx-redirx]
url = "https://app.redirx.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-redirx-redirx": {
      "type": "remote",
      "url": "https://app.redirx.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-redirx-redirx --url 'https://app.redirx.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-redirx-redirx:
    url: "https://app.redirx.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-redirx-redirx": {
      "Transport": "http",
      "Url": "https://app.redirx.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-redirx-redirx -t streamable-http -u 'https://app.redirx.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-redirx-redirx": {
      "type": "http",
      "url": "https://app.redirx.dev/mcp"
    }
  }
}
```

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-11-06 (score 76, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-11-03 (score 75, +1)

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

### 2026-11-01 (score 74, +1)

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

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

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

### 2026-10-28 (score 72, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “export_redirects” rewrote its description, which is the text the model reads
- [security] Tool “list_matches” rewrote its description, which is the text the model reads
- [security] Tool “resolve_matches” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: 130 → 169
- [functional] New tool “group_matches”
- [functional] New tool “resolve_group”
- [cosmetic] “export_redirects” added an optional parameter “accept_proposals_above”
- [cosmetic] “export_redirects” added an optional parameter “slash_variants”
- [cosmetic] “list_matches” added an optional parameter “group_id”

### 2026-10-27 (score 72, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 71)

First indexed and scored.

## MCP tools (12)

### `plan_migration` (~156 tokens)

Plan a migration

Create an owned old-site/new-site plan. Next call import_inventory for the old and new URL lists; planning does not crawl or run the model.

Input parameters:

- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `name` (string)
- `new_site` (string, required): Origin of available destination pages, e.g. https://new.example; no path, query, fragment or credentials.
- `old_site` (string, required): Origin of existing source pages, e.g. https://old.example; no path, query, fragment or credentials.
- `site_aliases` (object): Additional explicitly allowed origins per side (www or staging). Aliases are never inferred.

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `import_inventory` (~170 tokens)

Import a URL inventory

Import explicit HTTP(S) URL strings into an owned, immutable old or new inventory. No crawl or page fetch. Use data.inventory.id with run_migration only when data.inventory.status is complete; a partial import lists its exclusions and needs corrected input and a new key. Up to 15,000 old / 20,000 new URLs and 16 MiB of URL text. Importing never authorizes a charge.

Input parameters:

- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `migration_id` (string, required)
- `side` (string, required): old = existing source pages; new = available destination pages.
- `urls` (array, required): Absolute page URLs, not a sitemap URL. Path case, escapes and query strings are kept exactly.

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `run_migration` (~175 tokens)

Run a migration

Match old URLs to new ones from two complete inventories. Migrations up to 500 old URLs run free (one free run a day, five in total per account). Otherwise the answer is payment_required with the one-time price ($1 per 50 old URLs, $10 minimum) and a checkout link that only a person can complete; after paying, retry with the same input and key. A queued run finishes in minutes: poll get_migration after retry_after_seconds. confirmed_pairs must be pairs a person confirmed, never guesses.

Input parameters:

- `confirmed_pairs` (array)
- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `migration_id` (string, required)
- `new_inventory_id` (string, required)
- `old_inventory_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `get_migration` (~66 tokens)

Get migration status

Read an owned migration, its latest inventories, runs (with progress), exports and verifications, and the next recoverable action. Keep migration_id across reconnects; poll only after retry_after_seconds. A finished run still needs review before export.

Input parameters:

- `migration_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `group_matches` (~217 tokens)

Group migration matches

Start review here. Groups a run's mappings by the URL rewrite they apply (from → to, e.g. /product/{slug}/ → /products/{slug}), groups with the most undecided rows first. kind is moved, kept_tail, same_path, unchanged (no redirect needed) or unmatched; renamed counts rows whose last segment also changed. Each group has counts by state, the confidence range of its undecided proposals and up to three examples, lowest confidence first. Show the person each group as a rule with its examples and let them decide per group (resolve_group), opening a group with list_matches group_id when they want to see every row. A group is a way to read proposals, not a decision. Keep data.selection_revision for resolve_group.

Input parameters:

- `filter` (string): Group only rows in this state.
- `limit` (integer)
- `migration_id` (string, required)
- `offset` (integer): Groups to skip; use data.next_offset until it is null.
- `run_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `list_matches` (~179 tokens)

List migration matches

Read a run's mappings in stable URL order: the latest proposal, the current decision and its revision. Pass group_id (from group_matches) to read one group's rows. Follow data.next_cursor until null with the same run, filter and group; one page is not the whole run. data.counts are for the whole run. Keep each revision and data.selection_revision for resolve_matches and export_redirects. Confidence is an uncalibrated model estimate. Decisions with actor_kind "engine" came from the previous RedirX engine and can be changed like any other.

Input parameters:

- `cursor` (string)
- `filter` (string)
- `group_id` (string): Only this group's rows (a group_id from group_matches).
- `limit` (integer)
- `migration_id` (string, required)
- `run_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `resolve_group` (~207 tokens)

Resolve a group of matches

After the person decides on a whole group from group_matches: record one decision (approve confirms each row's latest proposal; reject, defer or intentional_removal) for every row in the group that has no decision yet. Rows already decided are never changed, and rows in except_mapping_ids are left for resolve_matches. expected_selection_revision is the data.selection_revision you showed the person; a revision_conflict means read group_matches again and re-confirm. A data.remaining above 0 means call again with the new selection_revision and a new key.

Input parameters:

- `action` (string, required)
- `except_mapping_ids` (array): Rows of the group the person wants to decide separately.
- `expected_selection_revision` (integer, required)
- `group_id` (string, required)
- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `migration_id` (string, required)
- `rationale` (string)
- `run_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `resolve_matches` (~146 tokens)

Resolve matches

Record audited decisions on individual rows with optimistic concurrency, after the user agrees (for a whole group, use resolve_group): approve (confirms the proposed target, or target_url if given), set_target (an exact URL from the new inventory), reject, defer or intentional_removal. Each needs mapping_id and the expected_revision you read. Inspect every outcome: a batch can partly fail; on revision_conflict reread list_matches and reassess.

Input parameters:

- `decisions` (array, required)
- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `migration_id` (string, required)
- `run_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `refine_matches` (~117 tokens)

Refine matches

Resume a run that stopped part-way (same pass, kept proposals), or start its next pass, which learns from the targets people confirmed and the most confident proposals. Up to three passes per run; no new charge. Read the run's seed_revision from get_migration or list_matches first.

Input parameters:

- `expected_seed_revision` (integer, required)
- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `migration_id` (string, required)
- `run_id` (string, required)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `export_redirects` (~367 tokens)

Export redirects

Create an immutable redirect file at exactly the selection revision you showed the person (data.selection_revision). Before exporting, ask the person what to include: every proposal is the default, or only those at or above a confidence; say how many fall below RedirX's recommended review threshold (data.review from group_matches). Pass their answer as accept_proposals_above (0 for every proposal): each undecided proposal at or above it becomes their decision. Rejected rows are left out without asking; any other exclusion (held for review, no destination, unsafe for the format) needs allow_partial after the person agrees. Each old URL's other trailing-slash spelling is added as its own rule to the same destination unless slash_variants is false. Small files come back in data.content; every file is readable as the returned resource_uri. Save the file into the person's project yourself; download_url is for a person working without an agent. Export does not install redirects.

Input parameters:

- `accept_proposals_above` (number): Only with the person's answer: accept every undecided proposal at or above this confidence as their decision (0 = all). Omit to export decisions only.
- `allow_partial` (boolean)
- `format` (string, required): wordpress is Redirection plugin CSV; cloudflare is Pages _redirects, not Bulk Redirects CSV. csv and json are generic review mappings that need adaptation before installation.
- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `migration_id` (string, required)
- `revision` (integer, required)
- `run_id` (string, required)
- `slash_variants` (boolean): Also redirect each old URL's other trailing-slash spelling (/about-us and /about-us/).

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `verify_redirects` (~169 tokens)

Verify redirects

Only after the user confirms an export is installed: check each of its redirects on the live site (status, hops, final destination). Give live_origin (where the old URLs are served) and origin_rewrites mapping export destination origins to live ones ({} keeps them). Poll get_migration for results. This does not install rules or establish Google indexing, canonicals, robots or sitemaps; inspect unchecked results before claiming success.

Input parameters:

- `artifact_id` (string, required): The export id (data.export.id).
- `deployment_confirmation` (boolean, required)
- `idempotency_key` (string, required): Unique per intended change; retry an uncertain call with the identical input and key.
- `live_origin` (string, required)
- `migration_id` (string, required)
- `origin_rewrites` (object)

Output parameters:

- `contract_version` (string)
- `data` (object)
- `error`
- `migration_id` (string|null)
- `next_action` (string)
- `operation_id` (string|null)
- `retry_after_seconds` (number)
- `status` (string)

### `ping` (~19 tokens)

Ping

Connection check. Returns "pong". Has no side effects.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-redirx-redirx/app#diagnostics

## Score history

- 2026-11-06: 76
- 2026-11-05: 75
- 2026-11-04: 75
- 2026-11-03: 75
- 2026-11-02: 74
- 2026-11-01: 74
- 2026-10-31: 73
- 2026-10-30: 73
- 2026-10-29: 72
- 2026-10-28: 72
- 2026-10-27: 72
- 2026-10-26: 71

## Common questions

### What is the dev.redirx/redirx MCP server?

dev.redirx/redirx is an MCP server listed in the public MCP registry as dev.redirx/redirx. Map old site URLs to new ones during a migration, review proposals and export approved redirects. This page covers its hosted endpoint (https://app.redirx.dev/mcp).

### Is the dev.redirx/redirx MCP server safe to use?

dev.redirx/redirx scores 76 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 dev.redirx/redirx MCP server expose?

dev.redirx/redirx exposes 12 tools: plan_migration, import_inventory, run_migration, get_migration, group_matches, and 7 more. Their descriptions and schemas cost roughly 1,988 tokens of context every time the server is loaded.

### Does the dev.redirx/redirx MCP server require authentication?

Yes. dev.redirx/redirx asked us for credentials when we connected, so you will need to authorise it in your MCP client before it can do anything.

### Is the dev.redirx/redirx MCP server still maintained?

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

### What did VerifyMCP test on the dev.redirx/redirx MCP server?

VerifyMCP ran 12 checks on dev.redirx/redirx, covering TLS certificate, Authorization, HSTS header, DNSSEC and 8 more. One item could not be completed, a gap on our side rather than a finding about dev.redirx/redirx: HTTPS. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://app.redirx.dev/mcp
- Website: https://redirx.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-redirx-redirx/app.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-redirx-redirx/app/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/dev-redirx-redirx/app.json
- HTML version of this page: https://verifymcp.io/servers/dev-redirx-redirx/app