AI Website Check
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| KI_CHECK_KENNUNG | No | A user agent with your contact, so site owners know who is reading (see .env.example). | |
| ANTHROPIC_API_KEY | No | Optional API key for the AI part. Without it the check runs with the fixed rules only. |
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_websiteA | Walks through a small-business website the way a customer would (Google listing, phone view, services, price, hours, calling, address, trust, inquiry) and reports where a customer gets stuck. Rule findings come from the HTML. AI findings only count with a verbatim quote from the site that the server has checked. Reads only, never submits forms, follows robots.txt. Takes about 5 to 60 seconds. |
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 confusing it with another. Its purpose is clearly described and distinct.
The single tool uses a clear verb_noun pattern (check_website) in snake_case. No inconsistency exists because there are no other names to compare.
A single tool for an entire website-checking workflow is borderline thin. While the tool itself is comprehensive, the surface offers no granularity for separate checks or stages.
The tool covers the key customer-journey aspects: Google listing, mobile view, services, pricing, hours, calling, address, trust, and inquiry. It reports where customers get stuck and respects read-only and robots.txt constraints, leaving no obvious gap for the stated purpose.