ai-visibility-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": true
} |
| logging | {} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
| extensions | {
"io.modelcontextprotocol/ui": {}
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| check_ai_visibilityA | Check how discoverable a website is to AI assistants and AI search engines. |
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 confusion or overlap. The tool's purpose is clearly unique and distinct.
A single tool with a descriptive snake_case verb_noun name. There is no inconsistency to assess, but the naming is clear and follows conventional MCP patterns.
A single tool feels thin for a dedicated MCP server, even for a focused purpose. The borderline count leaves little room for related operations but is not excessively sparse.
The tool directly covers the core stated purpose of checking AI visibility. Minor gaps exist, such as batch checks or historical analysis, but they do not block the primary use case.