getdr-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| GETDR_API | No | URL of a getdr server on your network to use as the backend, e.g. http://lan-host:8080. When set, the server sends one POST $GETDR_API/dr per call instead of using the getdr binary. | |
| AHREFS_KEY | No | Ahrefs API key used by the getdr binary backend when GETDR_API is not set. The binary can also use its own config or api setting instead. | |
| GETDR_SERVE_TOKEN | No | Bearer token sent as Authorization: Bearer $GETDR_SERVE_TOKEN when GETDR_API is set and the getdr server requires 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": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| get_drB | Ahrefs Domain Rating (0–100) for domains or URLs, via getdr by Index Pages |
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 a single tool there is no possibility of selecting the wrong one. The tool's purpose (fetching Ahrefs Domain Rating for a domain or URL) is unambiguous.
The name get_dr follows a clear verb_noun snake_case pattern, so there is no risk of convention mixing. The abbreviation 'dr' is slightly less descriptive than a fuller name like get_domain_rating, but it is readable and matches the product name.
One tool is defensible for a narrow, single-metric lookup service, and it is clearly scoped. However, the surface is thin: there is no batch lookup or companion operation, leaving the server at the borderline of minimal.
The stated domain is Domain Rating lookup, and the single tool fully covers that core operation. Minor gaps exist only in conveniences such as querying multiple domains in one call, which agents can work around by repeating the call.