Bouncefern: Bulk URL Status Checker — broken links, redirects, loops

dev.workers.cybermax-tools.cybermaxPublished by cybermax.cybermax-tools.workers.devv1.0.0Updated Oct 29, 2026

Check many URLs at once: HTTP status, redirect chains and loops, so you see which links break.

The publisher's own server: status.live national parks

VerifiedStreamable HTTPWeb executableWeb Search & Scraping

Overview

AI-generated overview

Remote MCP server that checks many URLs at once, reporting HTTP status codes, redirect chains and redirect loops so an assistant can spot broken links.

What you can do
  • Check a batch of URLs in one run and get back each URL's HTTP status.
  • Follow redirect chains to see where links ultimately land.
  • Detect redirect loops that prevent a link from resolving.
  • Summarize which links in a list are broken or misdirected.
When to use it
Useful when auditing a site's outbound or internal links, cleaning up a link list, or verifying that URLs in documentation, campaigns or datasets still resolve before publishing.
Requirements
A remote MCP endpoint reached over streamable HTTP with OAuth authentication; an Apify API token supplied as a Bearer token in the Authorization header is required. No local package or runtime is needed.
Before you install
The Authorization header carries an Apify API token, so treat it as a secret. Runs are billed per URL to the Apify account, so large batches cost money. URL lists are sent to the remote Apify-hosted service.

Installation

In SourceWeft

  1. Open Bouncefern: Bulk URL Status Checker — broken links, redirects, loops in the dashboard and add it to a workspace.
  2. Connect the required credentials. They are stored privately and never shown on public pages.
  3. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/dev.workers.cybermax-tools.cybermax%2Furl-status-checker/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config. The client completes OAuth sign-in on first connect.

{
  "mcpServers": {
    "bouncefern-bulk-url-status-checker-broke": {
      "type": "http",
      "url": "https://mcp.apify.com/?tools=cybermax/url-status-checker&via=mcp-registry"
    }
  }
}

Tools

0
This server asks you to sign in, so SourceWeft could not read its tools without an account and has not indexed them. What a connected account sees can depend on that account and its permissions.

Version history

1
  1. v1.0.0LatestOct 29, 2026

Score

67% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listed15 pts

    Answer tools/list without a credential, or ship a package that starts in a sandbox without one.

  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • LicenseNot applicable

    A hosted service is used under its provider's terms, so no license is expected here. This check is left out of the percentage.

Other Status integrations