DomScan MCP Server
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 |
|---|---|
| domscan_mcp_statusA | Check whether this wrapper is configured with a DomScan API key and show setup details for the hosted domain-intelligence MCP endpoint. |
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 between tools. The single tool has a clearly defined purpose of checking configuration status.
The single tool name 'domscan_mcp_status' follows a clear lowercase_with_underscores convention, and there are no other tools to create inconsistency.
The server is positioned as a domain-intelligence MCP endpoint, but it exposes only a status check tool. This is a trivial single tool that does not fulfill the apparent scope of providing domain intelligence functionality.
The tool surface is severely incomplete for a domain-intelligence server. There are no tools to actually query, scan, or analyze domains; only a configuration status check is provided.