// SCAN REPORT

Deadlink Checker

3 tools. 1 can modify or destroy data without limits.

1 write tool that can modify data. Rate limits recommended.

Last updated: 3 Jul 2026

1 can modify or destroy data

2 read-only

3 tools total

Community server · catalogue entry verified 03/07/2026

How to control Deadlink Checker ↓

TOOL MAP

What Deadlink Checker exposes to your agents

Read (2) Write / Execute (1) Destructive / Financial (0)

Running more than one server? Check your whole stack →

MOST DANGEROUS TOOLS

High Risk

The most dangerous Deadlink Checker tools

Execute · Medium deep_scan Recursively crawling a website is an active external operation, not a passive read of stored data.

1 of Deadlink Checker's 3 tools can modify, destroy, or commit something on every call — and an agent calls them with no built-in limits.

POLICY

How to control Deadlink Checker

PolicyLayer is an MCP gateway — it sits between your AI agents and Deadlink Checker, and nothing reaches the server without passing your rules. These are the rules we recommend:

Cap read operations

{
  "check_links": {
    "limits": [
      {
        "counter": "check_links_per_minute",
        "window": "minute",
        "max": 60,
        "scope": "grant"
      }
    ]
  }
}

Controls API costs and prevents retry loops from exhausting upstream rate limits.

Create a free account and register Deadlink Checker — nothing to install.
Add these rules — paste them, or build them visually. Tune the limits to your setup.
Point your MCP client (Claude, Cursor, anything) at your gateway URL.

ENFORCE POLICY ON DEADLINK CHECKER →

Instant setup, no code required.

FULL CATALOGUE

All 3 Deadlink Checker tools

EXECUTE 1 tools

Execute deep_scan Recursively crawl a website

READ 2 tools

Read check_links Check all links on a webpage for broken URLs (404s), redirects (301/302), and timeouts. Returns status, respon Read check_sitemap Fetch a sitemap.xml file and check all listed URLs for broken links, redirects, and timeouts. Supports sitemap

FAQ

Questions about Deadlink Checker

Is the Deadlink Checker MCP server safe to use without restrictions? +

The Deadlink Checker server is primarily read-only with 2 read tools. While it cannot modify data, an agent in a retry loop can make thousands of API calls per minute, exhausting rate limits and running up costs. Rate limiting is still recommended.

How many tools does the Deadlink Checker MCP server expose? +

3 tools across 1 categories: Read. 2 are read-only. 1 can modify, create, or delete data.

How do I enforce a policy on Deadlink Checker? +

Register the Deadlink Checker MCP server in PolicyLayer, apply the suggested rules above (adjust the limits to your use case), and point your AI client at the PolicyLayer proxy URL instead of the server directly. Your agents keep the same tools; PolicyLayer evaluates every call against policy before it executes. Nothing to install, live in minutes.

Enforce policy on every Deadlink Checker tool call.

Deterministic rules across all 3 Deadlink Checker tools. Per-identity grants. Full audit log. Live in minutes. Nothing to install.

ENFORCE POLICY ON DEADLINK CHECKER →

Instant setup, no code required.

3 Deadlink Checker tools catalogued and risk-classified — across an index of 43,000+ MCP servers.