Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

dev.redirx/redirx

REMOTE · APP.REDIRX.DEV

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

Available components

+3 this week 76 Trust /100

Last scanned (11 hours ago)

Scores higher than 65% of remote servers

Reachable. Last reached 6 Nov 2026.

Category Marketing and SEO

Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security78
  • The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
  • 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. View diagnostics → Pass
  • HTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement. View diagnostics → Unverified
  • HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
  • DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
  • The authorisation server offers only Dynamic Client Registration (RFC 7591), which MCP 2026-07-28 deprecated in favour of Client ID Metadata Documents. View diagnostics → Partial
Transport & Reachability100
Schema Quality & AI Usability72
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management37
  • Stability observed for 11 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage82
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 38% of tool parameters carry a description.Partial
  • Structured output schemas are declared (92% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 12 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 14 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
What we tested

Checks we ran (12)

  • TLS certificate
  • Authorization
  • HSTS header
  • DNSSEC
  • Transport
  • Schema quality
  • Stability
  • Tool coverage
  • Injection markers
  • Destructive annotations
  • Judged manipulation
  • MCP protocol

Checks we could not complete (1)

These are gaps on our side, not findings about this hosted endpoint. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • HTTPS in Endpoint SecurityHTTPS enforcement could not be verified: the plaintext port answered with HTTP 401, which proves neither a plaintext path nor enforcement.

Does not apply to this hosted endpoint (2)

  • Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
  • Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 6 Nov 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 3 Nov 26 +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.

  • 1 Nov 26 +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.

  • 30 Oct 26 +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.

  • 28 Oct 26 0
    • 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 security
    • Schema quality: 130 → 169 ▼ functional
    • New tool “group_matches” functional
    • New tool “resolve_group” functional
    • “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” cosmetic
  • 27 Oct 26 +1
    • Stability: unverified → 0.03 ▲ functional
  • 26 Oct 26 71

    First indexed and scored.

Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 6 Nov 2026 · Probed https://app.redirx.dev/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=redirx.dev CN=WE1,O=Google Trust Services,C=US 26 Oct 2026 24 Jan 2027 ECDSA 256 ECDSA-SHA256 15f7c6425da7b007131c2b651ef6ad24
SANs: redirx.dev, app.redirx.dev, *.app.redirx.dev
CN=WE1,O=Google Trust Services,C=US (CA) CN=GTS Root R4,O=Google Trust Services LLC,C=US 13 Dec 2023 20 Feb 2029 ECDSA 256 ECDSA-SHA384 7ff31977972c224a76155d13b6d685e3
CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE 15 Nov 2023 28 Jan 2028 ECDSA 384 SHA256-RSA 7fe530bf331343bedd821610493d8a1b

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of app.redirx.dev. — Not signed

Zone DS Keys Algorithms Outcome
. Trust anchor 20326, 38696 8, 8 Verified
dev. DS published 60074 8 Verified
redirx.dev. No DS Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication Enforced and verified

The endpoint asked for a token and published valid RFC 9728 metadata describing how to get one.

Result Enforced and verified
Enforced On tool calls
HTTP status 200

WWW-Authenticate challenge Bearer resource_metadata="https://app.redirx.dev/.well-known/oauth-protected-resource/mcp"

Bearer resource_metadata="https://app.redirx.dev/.well-known/oauth-protected-resource/mcp"

Protected resource metadata

Document https://app.redirx.dev/.well-known/oauth-protected-resource/mcp
Retrieved Yes
Resource https://app.redirx.dev/mcp
Authorisation server https://app.redirx.dev/api/auth

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://app.redirx.dev/mcp Verified 200
http (plaintext) http://app.redirx.dev/mcp Inconclusive 401
MCP tools · 12 exposed · ~1,988 tokens

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tool Tokens
export_redirects ~367

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.

NameTypeReqDescription
accept_proposals_abovenumber–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_partialboolean––
formatstringyeswordpress 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_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
migration_idstringyes–
revisionintegeryes–
run_idstringyes–
slash_variantsboolean–Also redirect each old URL's other trailing-slash spelling (/about-us and /about-us/).
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

get_migration ~66

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.

NameTypeReqDescription
migration_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

group_matches ~217

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.

NameTypeReqDescription
filterstring–Group only rows in this state.
limitinteger––
migration_idstringyes–
offsetinteger–Groups to skip; use data.next_offset until it is null.
run_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

import_inventory ~170

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.

NameTypeReqDescription
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
migration_idstringyes–
sidestringyesold = existing source pages; new = available destination pages.
urlsarrayyesAbsolute page URLs, not a sitemap URL. Path case, escapes and query strings are kept exactly.
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

list_matches ~179

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.

NameTypeReqDescription
cursorstring––
filterstring––
group_idstring–Only this group's rows (a group_id from group_matches).
limitinteger––
migration_idstringyes–
run_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

ping ~19

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

Input schema present but exposes no named parameters.

No output schema declared.

No examples provided.

plan_migration ~156

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.

NameTypeReqDescription
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
namestring––
new_sitestringyesOrigin of available destination pages, e.g. https://new.example; no path, query, fragment or credentials.
old_sitestringyesOrigin of existing source pages, e.g. https://old.example; no path, query, fragment or credentials.
site_aliasesobject–Additional explicitly allowed origins per side (www or staging). Aliases are never inferred.
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

refine_matches ~117

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.

NameTypeReqDescription
expected_seed_revisionintegeryes–
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
migration_idstringyes–
run_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

resolve_group ~207

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.

NameTypeReqDescription
actionstringyes–
except_mapping_idsarray–Rows of the group the person wants to decide separately.
expected_selection_revisionintegeryes–
group_idstringyes–
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
migration_idstringyes–
rationalestring––
run_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

resolve_matches ~146

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.

NameTypeReqDescription
decisionsarrayyes–
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
migration_idstringyes–
run_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

run_migration ~175

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.

NameTypeReqDescription
confirmed_pairsarray––
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
migration_idstringyes–
new_inventory_idstringyes–
old_inventory_idstringyes–
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

verify_redirects ~169

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.

NameTypeReqDescription
artifact_idstringyesThe export id (data.export.id).
deployment_confirmationbooleanyes–
idempotency_keystringyesUnique per intended change; retry an uncertain call with the identical input and key.
live_originstringyes–
migration_idstringyes–
origin_rewritesobject––
NameTypeReqDescription
contract_versionstringyes–
dataobjectyes–
error–yes–
migration_idstring|nullyes–
next_actionstringyes–
operation_idstring|nullyes–
retry_after_secondsnumber––
statusstringyes–

No examples provided.

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.

remote · app.redirx.dev

# add to Claude Code
claude mcp add --transport http dev-redirx-redirx 'https://app.redirx.dev/mcp'
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.