getdr

io.github.index-pages由 GitHub 帳號 index-pages 發布v0.2.0更新於 Oct 29, 2026

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

概覽

AI 產生的概覽

一個小型 stdio MCP 伺服器,只提供一個 get_dr 工具,透過 getdr 回傳網域或網址的 Ahrefs Domain Rating(0–100)。

可以做什麼
  • 批次查詢網域或網址的 Ahrefs Domain Rating
  • 選擇 DR 公式版本(dr3 或 dr4),或略過快取重新抓取
  • 依輸入順序回傳每個目標的 JSON 記錄,Ahrefs 無資料時 DR 為 null,無效目標會帶錯誤標記
適用情境
適合需要快速取得一個或多個網域 Domain Rating 的情況,例如 SEO 或外部連結開發工作,且你已有 getdr 環境或網路內的 getdr 伺服器。
執行需求
透過 npx 以 stdio 在本機執行,需要 Node.js 18 或更新版本。需設定 GETDR_API 指向 getdr 伺服器(可選 GETDR_SERVE_TOKEN),或在 PATH 中有 0.2.0 或更新版本的 getdr 執行檔,後者本身需要 Ahrefs API 金鑰(AHREFS_KEY)。呼叫逾時為 120 秒。
安裝前請注意
Ahrefs API 金鑰保存在 getdr 伺服器或執行檔中;GETDR_SERVE_TOKEN 是傳送給該伺服器的 Bearer 密鑰。Domain Rating 資料受 Ahrefs 授權條款約束,發布數字時須標註「Domain Rating by Ahrefs」,但工具結果本身不含標註。HTTP 後端預設忽略 HTTP_PROXY/HTTPS_PROXY,除非設定 NODE_USE_ENV_PROXY。

安裝

在 SourceWeft 中

  1. 開啟 儀表板中的 getdr,將其新增到工作區。
  2. 為需要使用其工具的對話啟用該服務。

Desktop only,透過 STDIO。 STDIO 服務會啟動本機處理程序,因此需要 SourceWeft 桌面主機。

其他 MCP 客戶端

參照 儲存庫 中的啟動說明。

README

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):

json
{  "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:

json
{  "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/<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

sh
npm cinpm run buildnpm 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.

來源:README.md,提交 01c586b

工具

0
SourceWeft 尚未在沙箱中啟動過該軟體包,因此其工具未知。

版本歷史

1
  1. v0.2.0最新Oct 29, 2026

評分

已滿足適用檢查項的 50%

該評分衡量此收錄條目的完整程度,依據註冊中心條目、端點與公開來源計算得出。它不是對伺服器本身的評價,也不表示伺服器安全或目前可用:可連通性是帶日期的檢查結果,評分也不包含安裝量或使用者評價。

  • 近 30 天內可連通25 分

    請保持端點能夠回應 MCP 握手;SourceWeft 每 30 天探測一次。

  • 已宣告認證方式10 分

    請在註冊中心條目中宣告憑證請求標頭,或保持端點能夠回應探測,以便判定其認證方式。

  • 已列出工具15 分

    請讓伺服器在無憑證時回應 tools/list,或發布可在沙箱中無憑證啟動的軟體包。

  • 描述必需15 分
  • 圖示10 分
  • 文件15 分
  • 授權條款10 分