Prototype · Preview: every server in the official registry, synced every 30 minutes. Reviews and accounts come in a later step.
PopNx MCPMCP servers for people who use AI · explained in plain words

getdr

by index-pagesversion 0.2.0i★ –iRuns on your computer
Registry nameio.github.index-pages/getdr-mcp

Install

Overview

Description from the maker (original English)

Ahrefs Domain Rating (0–100) for domains or URLs, via getdr by Index Pages

PopNx MCP’s three pillars

These three are never merged into one score: opinions, measurements and popularity are different things.

What you can do with it

We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.

  • Connection: Runs on your computer
  • Transport: stdio
  • Category: Developer tools
  • You need to fill in: GETDR_SERVE_TOKEN

Install

Pick the AI app you use, then copy the settings.

Before you install

  • Basic checks: 1 of 1 passed
  • Runs on your computer with your user’s permissions (files, network, apps).
  • You fill in yourself: GETDR_API, GETDR_SERVE_TOKEN

Values marked secret are keys to your account. Never share them or paste them into a chat.

You need

  • npmNode.js installed (for the npx command)

Which app do you use?

Pick your app above. We remember it, so next time the button says “Install in …”.

Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json

{
  "mcpServers": {
    "getdr": {
      "command": "npx",
      "args": [
        "-y",
        "getdr-mcp"
      ],
      "env": {
        "GETDR_API": "your-value",
        "GETDR_SERVE_TOKEN": "your-value"
      }
    }
  }
}

Run this in your terminal

claude mcp add getdr --env GETDR_API=your-value --env GETDR_SERVE_TOKEN=your-value -- npx -y getdr-mcp

Fill in the empty values before running it.

Open in Cursor

Or copy the settings yourself

Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json

{
  "mcpServers": {
    "getdr": {
      "command": "npx",
      "args": [
        "-y",
        "getdr-mcp"
      ],
      "env": {
        "GETDR_API": "your-value",
        "GETDR_SERVE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

Open in VS Code

Or copy the settings yourself

Paste into .vscode/mcp.json in your project

{
  "servers": {
    "getdr": {
      "type": "stdio",
      "command": "npx",
      "args": [
        "-y",
        "getdr-mcp"
      ],
      "env": {
        "GETDR_API": "your-value",
        "GETDR_SERVE_TOKEN": "your-value"
      }
    }
  }
}

Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.

This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.

Your choice stays on this device in a cookie; no account needed.

Values you fill in

  • GETDR_API env
    URL of a getdr server (getdr serve). When unset, the getdr binary on PATH is used.
  • GETDR_SERVE_TOKEN secret env
    Bearer token for the getdr server, if it requires one.

These settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.

What it can do

Runs on your computer; the tool list appears in your AI app after you install it.

Basic checksi

We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 8, 2026

  • ✓ Pass

    Maker matches the repo

    The registry name was verified with the GitHub account index-pages, which owns the repo

  • … Not checked yet

    Still maintained

    We have not read this repo from GitHub yet

  • … Not checked yet

    Has a licence

    We have not read this repo from GitHub yet

  • – Not applicable

    Endpoint responds

    This one runs on your computer; there is no internet endpoint

  • – Not applicable

    Sign-in with OAuth

    Runs on your computer and uses local settings instead

  • … Not checked yet

    No hidden instructions in tool descriptions

    Runs on your computer; we can only read tool lists from internet endpoints

Compared with others in Developer toolsi

  • More stars than 0% of the other 5547 servers in this category
  • Published to the registry more recently than 70% of the other 5547 servers in this category
  • Basic checks equal to or better than 100% of the other 5547 servers in this category

Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.

Common questions

Is getdr safe?

It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.

What keys or codes does it need?

You need to fill in: GETDR_SERVE_TOKEN

Does it run on my computer or in the cloud?

It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).

Is it still maintained?

The GitHub repo last changed –, and the latest version (0.2.0) reached the registry 10 days ago.

Which apps can use it?

Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Node.js on your computer.

What can I use instead?

In the same category: GitHub, Desktop Commander, Cloudflare MCP

Alternatives

Servers in the same category from other makers, sorted by stars.

Reading a card:↓ Downloads per weeki★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi

GitHub

GitHub’s official server lets AI read and manage code, issues and pull requests in your account. Use GitHub’s hosted version or run it locally with Docker.

by githubWidely used★ 34.2KUpdated 5 days ago

Computer or cloud

Desktop Commander

MCP server for terminal commands, file operations, and process management

by wonderwhy-erWidely used↓ 709.6K/wk★ 10.2KUpdated 17 days ago

Runs on your computer

Cloudflare MCP

Cloudflare MCP servers

by cloudflareWidely used★ 4.4KUpdated 14 months ago

Runs in the cloud✓ mcp.cloudflare.com

README from the maker

Open the README

Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.

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.

Backends

Checked on every call, in this order:

  1. GETDR_API is set – one POST $GETDR_API/dr to that getdr server (getdr serve), with Authorization: Bearer $GETDR_SERVE_TOKEN when the token is set. The server holds the Ahrefs key and the shared cache, so this machine needs neither.
  2. getdr (0.2.0 or newer) is on PATH – runs getdr --format json -q [--version V] [--fresh] -f - with the targets on stdin, no shell (as arguments after -- when a target starts with #, which -f would skip as a comment). The binary uses its own config, cache and key (AHREFS_KEY), or its own api setting.
  3. Neither – the tool returns an error with setup instructions.

Install the binary with 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".

argumenttype
targetsstring[]required, non-empty; domains or URLs
version"dr3" or "dr4"DR formula; when left out, the backend's config decides: the getdr server's with GETDR_API, otherwise the binary's (also when that binary uses a server), dr3 unless set; values are not comparable between versions
freshbooleanignore 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":"ahrefs.com","dr":91,"version":"dr3","checked_at":"2026-10-28T12:00:00Z","cached":true}, {"target":"nodata.example","dr":null,"version":"dr3","checked_at":"2026-10-28T12: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/ (+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 test

The 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.

Ask PopNx