io.github.tidybytetools/link-check-lite
Related Servers
Alternatives to io.github.tidybytetools/link-check-lite
No user-submitted related servers found.
Related Servers
- AlicenseNot gradedqualityBmaintenanceEnables AI assistants to check a single web page for broken links, trace redirect chains hop by hop, and detect mixed content through a remote Streamable HTTP tool.MIT
- AlicenseAqualityFmaintenanceEnables checking for broken links on web pages and entire websites through natural language commands. Provides detailed reports including HTTP status codes and supports options like excluding external links and respecting robots.txt.2MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to validate AI infrastructure claims, check endpoint availability, solve CAPTCHA challenges, convert web pages to Markdown, search the web, extract structured JSON, and fetch bot-protected HTML through native tool calls.MIT
- AlicenseNot gradedqualityCmaintenanceConnects AI assistants to a hosted website-checking service so they can retrieve detected issues such as typos, broken links, slow pages, and expiring domains or certificates, then edit site code, mark items fixed or ignored, and request rechecks after publishing.MIT
- AlicenseAqualityDmaintenanceEnables AI agents to extract structured content from URLs, search the web via DuckDuckGo, monitor site availability, and convert HTML to markdown without requiring API keys.536 npmMIT
- AlicenseAqualityAmaintenanceEnables AI assistants to capture screenshots and PDFs, read web pages as Markdown, preview links, look up DNS/SSL/WHOIS and email records, verify addresses, generate QR codes, barcodes and social images, convert images, and translate text.1923 npmMIT
TDQS
Scored across 1 tool
There is only one tool, so there is no possibility of confusing it with another. Its purpose—checking a batch of URLs and reporting status, redirects, and errors—is stated unambiguously.
The single tool name check_links follows a clear verb_noun snake_case convention, and its parameters (urls, timeout) are consistently lower snake_case. There is no competing convention to clash with.
A one-tool surface is thin even for a narrow link-checking domain; common adjacent operations (single-URL check, redirect resolution only, or batch job status) are not separable. The rubric's 'too few (1)' bracket applies, though the tightly scoped purpose softens the mismatch.
The tool returns per-link status, ok flag, final_url, redirect chain, and error, which covers the core lifecycle of a link check including failures and unreachable hosts. Minor gaps remain (e.g., HTTP method/header control, retry or concurrency options, handling links beyond the 200 cap), but agents can work around them.