Web Check MCP
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| WEB_CHECK_TIMEOUT | No | Timeout in seconds for API requests. | |
| WEB_CHECK_BASE_URL | No | Base URL of the Web Check API. If not set, public bases are probed automatically. | |
| WEB_CHECK_MAX_CHARS | No | Maximum number of characters for payload truncation. | |
| WEB_CHECK_MAX_WORKERS | No | Maximum number of parallel workers for fan-out. |
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 |
|---|---|
| webcheck_list_checksA | List available Web Check endpoints/groups (ssl, dns, headers, ports, …). |
| webcheck_healthA | Probe whether the configured Web Check API base URL is reachable. |
| webcheck_runA | Run one or more Web Check jobs against a URL (parallel fan-out). Prefer group=quick for recon; avoid heavy (screenshot/ports/traceroute) unless needed. |
| webcheck_sslA | Fetch SSL certificate chain for a URL via Web Check /ssl. |
| webcheck_dnsA | Fetch DNS records for a domain via Web Check /dns. |
| webcheck_securityC | Security bundle: ssl, tls, hsts, http-security, firewall, dnssec, security-txt, threats, block-lists. |
| webcheck_headersA | Fetch HTTP response headers via Web Check /headers. |
| webcheck_whoisB | WHOIS / domain registration data via Web Check /whois. |
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 8 tools
The specific check tools (ssl, dns, headers, whois) are clearly distinct, but webcheck_run and webcheck_security overlap with them by design as generic and bundled operations. The descriptions clarify intended use cases, so agents can select appropriately, though run's generality introduces some redundancy.
All tools share the webcheck_ prefix and snake_case, but the suffixes mix nouns (ssl, dns) and verb/noun phrases (list_checks) or bare verbs (run). This is consistent enough to predict purpose, but not a uniform verb_noun pattern.
At 8 tools, the set is well-scoped for a web check service: discovery, health, specific checks, a generic runner, and a bundle. Each tool serves a purpose without bloat.
The tool surface covers the full workflow: discover available checks via list_checks, verify API health, run individual checks (ssl, dns, headers, whois), execute arbitrary jobs via run, and get the security bundle. The generic run tool compensates for missing specific wrappers, making the set complete.