Linkinator

Created By
Justin Beckwith7 months ago
A Model Context Protocol (MCP) server that provides link checking capabilities using linkinator. This allows AI assistants like Claude to scan webpages and local files for broken links.
Overview

what is Linkinator?

Linkinator is a Model Context Protocol (MCP) server that provides link checking capabilities using linkinator. It allows AI assistants like Claude to scan webpages and local files for broken links.

how to use Linkinator?

To use Linkinator, you can either install it automatically using the install-mcp tool or configure it manually in your MCP client's configuration file. After installation, you can ask Claude to check links on any webpage or local file.

key features of Linkinator?

  • Comprehensive link checking for websites and local files
  • Recursive crawling to follow links within the same domain
  • Support for multiple content types including HTML, CSS, and Markdown
  • Fragment validation for anchor links and URL fragments
  • Flexible configuration options for timeouts, retries, and SSL
  • Detailed reporting of status codes and broken links

use cases of Linkinator?

  1. Checking for broken links on a website
  2. Validating links in documentation files
  3. Ensuring all links in a project are functional before deployment

FAQ from Linkinator?

  • Can Linkinator check links in all file types?

Yes! Linkinator can check links in HTML, CSS, and Markdown files.

  • Is Linkinator easy to set up?

Yes! You can set it up automatically or manually based on your preference.

  • What kind of reports does Linkinator generate?

Linkinator provides detailed reports showing the status of links, including broken links grouped by error type.

Server Config

{
  "mcpServers": {
    "linkinator": {
      "command": "npx",
      "args": [
        "linkinator-mcp"
      ]
    }
  }
}
Project Info
Created At
7 months ago
Updated At
7 months ago
Author Name
Justin Beckwith
Star
-
Language
-
License
-

Recommend Servers

View All
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

17 hours ago