Moz Da Pa1 MCP Server
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| API_KEY | Yes | API key for authentication |
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 |
|---|---|
| getdapaB | Our API provides real data from Moz. Domain Authority, Page Authority, External nofollow urls to url, External urls to url and Spam Score. |
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 possible ambiguity between tools. The single tool has a clearly distinct purpose.
The server has a single tool, so naming consistency is trivially maintained. The name 'getdapa' follows a verb_noun pattern.
The server has only one tool, which feels thin for a service that likely requires operations for different metrics or parameters. It is borderline appropriate.
The tool surface is severely incomplete. The domain of Moz data retrieval typically requires multiple endpoints or operations (e.g., getting specific metrics, filtering by URL), but only one tool is provided, limiting flexibility.