linkinator-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": true
} |
| resources | {
"listChanged": true
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| scan_pageA | Scan links in a webpage or local file path using linkinator. Checks for broken links, validates anchors, and can crawl recursively. Supports progress notifications for long-running scans. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 1 tool
With only one tool exposed, there is no possibility of misselection or overlap with another tool. Its purpose—scanning links in a page or local path—is unambiguous.
The single name scan_page follows a clear verb_noun snake_case pattern, which would remain predictable if more tools were added.
A single tool matches the narrow link-checking purpose and is non-trivial (recursive crawl, anchor validation, progress), but the surface is thin—no separate options for batch URLs, sitemap crawling, or result formatting.
Core scanning is covered, including recursion and anchor checks, but there are no companion operations such as scanning multiple targets in one call, site/sitemap-level entry points, or output filtering/report retrieval.