Skip to main content
Glama
Sign In
io.github.tidybytetools/link-check-lite

io.github.tidybytetools/link-check-lite

by tidybytetools
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Server Configuration

Describes the environment variables required to run the server.

NameRequiredDescriptionDefault

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

CapabilityDetails
tools
{
  "listChanged": false
}
prompts
{
  "listChanged": false
}
resources
{
  "subscribe": false,
  "listChanged": false
}
experimental
{}

Tools

Functions exposed to the LLM to take actions

NameDescription
check_linksA

Check web links and follow their redirects.

urls: up to 200 http(s) links.
timeout: seconds to wait for each link.

Returns one result per link: {url, status, ok, final_url, redirects, error}.
status is the HTTP code of the last hop (null if it could not connect).
ok is true for 200-399. redirects lists each hop as "CODE url".

Prompts

Interactive templates invoked by user choice

NameDescription

No prompts

Resources

Contextual data attached and managed by the client

NameDescription

No resources

Deploy Server
Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

TDQS

A4.1/5.0

Scored across 1 tool

Disambiguation5/5

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.

Naming Consistency5/5

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.

Tool Count2/5

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.

Completeness4/5

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.

Maintenance

ActivityMaintained
ResponsivenessNo issues

Resources