getdr-mcp
Use the get_dr tool to retrieve Ahrefs Domain Rating (0–100) for domains or URLs via getdr.
Accepts a required
targetsstring array of domains/URLs; URLs are normalized to hosts,www.dropped, lowercased, deduped, and results preserve input order.Supports optional
version(dr3ordr4) andfreshto ignore the cache and refetch.Returns per-target records with
target,dr(number ornull),version,checked_at(RFC 3339 ornull), andcached; the output schema also requires anattributionstring alongsideresults.Invalid targets or targets without data can appear as normal records where applicable; backend/setup failures surface as tool errors.
Works through either a configured getdr HTTP server (
GETDR_API, optionalGETDR_SERVE_TOKEN) or a localgetdrbinary onPATH.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@getdr-mcp What's the Ahrefs Domain Rating for stripe.com and shopify.com?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
getdr-mcp
getdr-mcp is a small open-source MCP server by
Index Pages that gives AI agents one tool, get_dr: Ahrefs Domain Rating (DR) for
domains or URLs. It is a thin front for getdr – it asks a getdr server or the
getdr binary and makes no Ahrefs requests of its own. Stdio transport, no runtime dependencies. Docs:
index-pages.com/getdr/.
Setup
Add it to your MCP client (Claude Desktop, Claude Code, Cursor and others use this shape):
{
"mcpServers": {
"getdr": {
"command": "npx",
"args": ["-y", "getdr-mcp"]
}
}
}That uses the getdr binary on your PATH. To use a getdr server on your network instead:
{
"mcpServers": {
"getdr": {
"command": "npx",
"args": ["-y", "getdr-mcp"],
"env": {
"GETDR_API": "http://lan-host:8080",
"GETDR_SERVE_TOKEN": "s3cret"
}
}
}
}Requires Node.js 18 or later.
Related MCP server: mcp-dns
Backends
Checked on every call, in this order:
GETDR_APIis set – onePOST $GETDR_API/drto that getdr server (getdr serve), withAuthorization: Bearer $GETDR_SERVE_TOKENwhen the token is set. The server holds the Ahrefs key and the shared cache, so this machine needs neither.getdr(0.2.0 or newer) is onPATH– runsgetdr --format json -q [--version V] [--fresh] -f -with the targets on stdin, no shell (as arguments after--when a target starts with#, which-fwould skip as a comment). The binary uses its own config, cache and key (AHREFS_KEY), or its ownapisetting.Neither – the tool returns an error with setup instructions.
Install the binary with brew install index-pages/tap/getdr, npm install -g getdr, pipx install getdr,
go install github.com/index-pages/getdr@latest or from
Releases, then get a free Ahrefs API key:
index-pages.com/getdr/#key.
Both backends return the same records. Calls time out after 120 seconds.
Proxies: the HTTP backend uses Node's built-in fetch, which ignores HTTP_PROXY/HTTPS_PROXY unless
NODE_USE_ENV_PROXY=1 is set (Node 22.21 or later, or 24 and later; older versions have no built-in proxy
support). The binary backend honours HTTP_PROXY, HTTPS_PROXY and NO_PROXY as usual.
Tool
get_dr – "Ahrefs Domain Rating (0–100) for domains or URLs, via getdr by Index Pages".
argument | type | |
| string[] | required, non-empty; domains or URLs |
|
| DR formula; when left out, the backend's config decides: the getdr server's with |
| boolean | ignore the cache and fetch again |
Targets are normalized by getdr: a URL becomes its host, www. is dropped, everything is lower-cased and
duplicates are removed. Results follow the input order.
Output
The text result is a JSON array with one record per target, and nothing else:
[
{"target":"index-pages.com","dr":69,"version":"dr4","checked_at":"2026-11-19T12:00:00Z","cached":true},
{"target":"nodata.example","dr":null,"version":"dr4","checked_at":"2026-11-19T12:00:00Z","cached":false}
]The record is the getdr JSON contract, the same as getdr --format json and getdr serve. dr is null
when Ahrefs has no data; checked_at is null too when there was no response or the target is invalid. An
invalid target (not a domain or URL, or refused by Ahrefs, such as localhost) also has
"error":"invalid target"; no other record has an error key. Clients on MCP protocol 2025-06-18 or later
also get structuredContent – {"results": […]} – and an outputSchema for it.
Invalid targets and targets without a response are part of a normal result. Failures come back as a tool
error (isError: true) with getdr's message:
no target got a response at all;
getdr server answered 401 – the token is missing or wrong, set
GETDR_SERVE_TOKEN;getdr server answered 503, or the binary exited with code 3 – the Ahrefs key is missing or rejected;
the server is unreachable, the binary failed, or a call timed out.
Supported MCP protocol versions: 2026-07-28 (stateless: server/discover and per-request _meta, no
handshake) and the initialize-based 2025-11-25, 2025-06-18, 2025-03-26 and 2024-11-05, served side by side.
Attribution
Domain Rating data comes from Ahrefs and is subject to the Domain Rating License, which requires the attribution "Domain Rating by Ahrefs" wherever you publish the numbers. The tool result carries only the data, with no attribution in it.
getdr is not affiliated with Ahrefs.
No telemetry
getdr-mcp connects to exactly one place: the getdr server in GETDR_API, when you set it. Otherwise it only
starts the getdr binary. No telemetry, no update checks, no analytics, no pings. Requests carry the
User-Agent getdr-mcp/<version> (+https://index-pages.com/getdr/). You can verify this in the source: the only
outgoing request and the only child process are in src/backends.ts.
Development
npm ci
npm run build
npm testThe backend tests build getdr and its mock-backed server from the getdr source tree (../bin, or
GETDR_SRC) and need Go; without it they are skipped. The live check runs only when AHREFS_KEY is set.
Releasing
Bump the version in package.json, server.json (twice) and src/version.ts, update CHANGELOG.md, then
push a tag vX.Y.Z. .github/workflows/release.yml builds, runs the tests against the getdr source at the
same tag, checks that every version matches the tag and that the packed tarball holds dist/index.js with its
shebang, and publishes with npm trusted publishing (OIDC, no token, provenance included).
Trusted publishing can only be configured for a package that already exists on npm, so the first release is
published by hand once: npm login, then npm run release. Right after that, add the trusted publisher on
npmjs.com (package Settings → Trusted publishing: GitHub Actions, index-pages / getdr-mcp, workflow
release.yml); the workflow has to complete its first publish within 2 days or the configuration expires.
For any manual publish use npm run release (build, tests, check-release, npm publish), never a bare
npm publish: with install scripts disabled (ignore-scripts) prepack does not run and the package would
ship without dist/. prepack stays as a fallback for setups that run scripts.
The same workflow then publishes server.json to the MCP Registry
as io.github.index-pages/getdr-mcp: it waits until npm shows the new version (the registry checks mcpName
in the npm package), proves the index-pages namespace with the workflow's OIDC token
(mcp-publisher login github-oidc, no secret) and runs mcp-publisher publish with a pinned, checksummed
mcp-publisher. A version already in the registry is skipped.
License
MIT, see LICENSE. Made by Index Pages.
Available Tools
1 toolget_drAhrefs Domain RatingBRead-only
Ahrefs Domain Rating (0–100) for domains or URLs, via getdr by Index Pages
Inputs: targets (required), fresh, version. Returns: results, attribution
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
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.
Maintenance
Related MCP Connectors
29 DNS, SEO, SSL, security, WHOIS & mail tools for AI agents. Pay per call (x402) or card API key.
Free, no-API-key network lookups for AI agents — IP geolocation, DNS, WHOIS, HTTP and SSL/TLS certificate checks, and full domain health reports.
URL intelligence for AI agents and developers. 16 tools, 25 signal weights, 20 free checks.
IP intelligence, network diagnostics, and AI service availability tools for AI agents.
Related MCP Servers
- AlicenseAqualityDmaintenanceEnables AI agents to check backlinks, domain rating, and expired domains using the seo-backlinks.net API.552 npmMIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to perform DNS lookups and reverse DNS queries through typed tools, resolving A, AAAA, CNAME, MX, TXT, NS, SOA, SRV, CAA, and PTR records.MIT
- AlicenseNot gradedqualityBmaintenanceEnables AI agents to validate AI infrastructure claims, check endpoint availability, solve CAPTCHA challenges, convert web pages to Markdown, search the web, extract structured JSON, and fetch bot-protected HTML through native tool calls.MIT

fairquery-webofficial
AlicenseAqualityAmaintenanceEnables AI agents to check a list of websites by running an Apify Actor through one tool, returning per-site tech stack, on-page SEO issues and score, robots.txt rules for AI crawlers, sitemap, llms.txt presence, and an AI-readiness score. Supports local stdio operation with an Apify token for tool calls.8MIT