website-checks-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": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_llms_txtA | Check a website's /llms.txt against the llmstxt.org format and its robots.txt for blocked AI crawlers. Returns a 0-100 score, the problems found with a plain fix for each, and a draft llms.txt built from the site's home page and sitemap when the file is missing. Example input: "example.com". |
| check_mcp_server_securityA | Run a read-only security check of a remote MCP server (Streamable HTTP). Checks HTTPS and the certificate, whether login is required, OAuth discovery and PKCE support, CORS, HSTS and version leaks. For open servers it also lists tools (it never calls them) and flags risky tools without safety hints, tool-poisoning phrases and missing Origin checks. Only check servers you own or are allowed to test. Example input: "https://mcp.example.com/mcp". |
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 2 tools
The two tools target entirely different artifacts: a website's llms.txt/robots.txt versus a remote MCP server's security posture. There is no plausible way for an agent to confuse one for the other, and the inputs (domain vs. HTTPS URL) are clearly disjoint.
Both follow the same check_<subject> snake_case pattern, and the subject portion is descriptive of exactly what is inspected. No mixed conventions or vague verbs.
Two tools is thin for a server branded as 'website-checks', which implies a broader catalog of checks. Each tool is substantial on its own, but the surface feels minimal rather than deliberately scoped.
Each check is self-contained and returns actionable output (score, problems with fixes, and even a generated draft llms.txt), so there are no dead ends within a single call. Gaps exist at the domain level — e.g., no general site hygiene, DNS/TLS or MCP functional/health checks — but these are minor for the apparent narrow purpose.