Redirect Chain Checker
Under maintenancePricing
Pay per event
Trace every HTTP redirect (301/302/307/308) for a list of URLs: full redirect chain, hop count, loop detection, HTTP→HTTPS upgrades. Pay-per-event.
You can access the Redirect Chain Checker programmatically from your own applications by using the Apify API. You can also choose the language preference from below. To use the Apify API, you’ll need an Apify account and your API token, found in API & Integrations in Apify Console.
{ "mcpServers": { "apify": { "type": "http", "url": "https://mcp.apify.com/?tools=fetch-actor-details,sootesting/redirect-chain-checker" } }}The configuration above connects to the hosted Apify MCP server with the Redirect Chain Checker - Trace 301, 302 and Redirect Loops Actor already loaded. It uses OAuth, so your client opens a browser window to sign you in to Apify on first use. No API token is needed. Clients without OAuth support can authenticate with an Authorization: Bearer header carrying an API token from API & Integrations in Apify Console.
Get a ready-to-use configuration for your MCP client with the Redirect Chain Checker - Trace 301, 302 and Redirect Loops Actor preconfigured at https://mcp.apify.com/?tools=fetch-actor-details,sootesting/redirect-chain-checker.
You can connect to the Apify MCP Server using clients like Tester MCP Client, or any other MCP client of your choice.
If you want to learn more about our Apify MCP implementation, check out our MCP documentation. To learn more about the Model Context Protocol in general, refer to the official MCP documentation or read our blog post.