mcp-link-doctor
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| MCPCAT_PROJECT_ID | No | Optional project ID from mcpcat.io. If not provided, analytics are disabled. |
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
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check-linksA | Find broken links, missing meta tags, and redirect chains on any website. Returns a structured report with fix suggestions. |
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, there is no possibility of confusion between tools. The tool's purpose is clear and unambiguous.
A single tool cannot exhibit inconsistency. The name 'check-links' follows a simple verb_noun pattern and is self-explanatory.
The server has only one tool, which is borderline thin for a domain that could involve multiple types of checks (e.g., broken links, meta tags, redirects). However, it may still be acceptable for a lightweight diagnostic tool.
The single tool covers checking for broken links, missing meta tags, and redirect chains, which are core features. However, missing tools for batch processing, history, or fixing actions leave notable gaps.