Domaintrack

io.github.CloudCorpRecordsPublished by GitHub account CloudCorpRecordsv0.1.0Updated Nov 7, 2026

Look up domain reputation snapshots and AI crawler policy from Domduck's public store.

VerifiedSTDIODesktop onlyWeb Search & ScrapingSecurity & Monitoring

Overview

AI-generated overview

Looks up a domain's public reputation snapshot and AI crawler policy from Domduck's keyless public store, forwarding each call upstream.

What you can do
  • Look up one domain's stored reputation snapshot: Domain Rating, Tranco rank, OpenPageRank, registration date, TLS certificate state and AI crawler policy
  • Check which of eight tracked AI crawlers a domain's robots.txt allows, blocks or never mentions, and whether an llms.txt is published
  • Read the catalogue of data sources behind the other two tools and what each field means
When to use it
Useful when you want an assistant to check a domain's reputation signals or its AI crawler and llms.txt policy while researching sites, vetting links, or auditing crawl permissions. It is a thin forwarding client, so it only returns what Domduck's public store already holds.
Requirements
Runs as a local stdio process via npx (Node.js) or the published Docker image. No account, API key or credentials are needed; it calls Domduck's public endpoint over the network. An optional DOMDUCK_MCP_URL variable overrides the upstream endpoint.
Before you install
Each lookup is forwarded to Domduck's public endpoint, so the domains you query leave your machine. A domain nobody has looked up returns hasReading false rather than an error, so treat that as missing data, not a clean result. The optional DOMDUCK_MCP_URL override points the client at a different upstream.

Installation

In SourceWeft

  1. Open Domaintrack in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.

Other MCP clients

Follow the launch instructions in the repository.

README

domaintrack

domaintrack looks up what is publicly known about a domain: its reputation snapshot, the AI crawler policy its robots.txt sets, and the list of data sources those answers are built from.

It is a forwarding client, not a data store. The answers live in Domduck's public store and are served by its keyless public endpoint; this package carries the endpoint's three-tool surface, serves the tool list locally, and forwards each call upstream, returning the upstream answer exactly as it arrives. There is no account and no API key: the public endpoint is the whole surface. Domduck's authenticated endpoint, with its dated history series, is separate and is not touched here — this client sends no credentials of any kind.

One behaviour is worth knowing before you automate against it: asking about a domain nobody has looked up yet is not an error. The snapshot comes back with hasReading set to false, which is the store honestly saying it holds no reading for that name yet.

Tools

  • lookup_domain — the stored reputation snapshot for one domain: Domain Rating, Tranco rank, OpenPageRank, registration date, TLS certificate state and AI crawler policy. Requires domain.
  • get_ai_crawler_policy — for each of the eight tracked AI crawlers, whether the domain's robots.txt allows it, blocks it, or never mentions it, plus whether an llms.txt is published. Requires domain.
  • list_sources — the catalogue of sources behind the other two tools and what each one means. No arguments; read it first if a snapshot field is unfamiliar.

CLI

bash
npx @reneturcios/domaintrack lookup_domain '{"domain":"example.com"}'npx @reneturcios/domaintrack get_ai_crawler_policy '{"domain":"example.com"}'npx @reneturcios/domaintrack list_sourcesnpx @reneturcios/domaintrack --version

Each tool subcommand forwards one call and prints the result content as JSON. Exit codes: 0 on success, 1 when the upstream call comes back as an error result, 2 on a usage error (unknown subcommand, malformed JSON argument).

MCP server

bash
npx @reneturcios/domaintrack mcp

MCP client configuration:

json
{  "mcpServers": {    "domaintrack": {      "command": "npx",      "args": ["-y", "@reneturcios/domaintrack", "mcp"]    }  }}

The server answers tools/list itself and forwards every tools/call to the public endpoint over a Streamable HTTP session (initialize, then notifications/initialized, then the call), reusing the session — and its Mcp-Session-Id, when the endpoint issues one — for the life of the process.

Failures on the wire are reported in this package's own words, as a text result starting with domaintrack error: — a JSON-RPC error from upstream, a non-2xx HTTP status, an unparseable response body, or a failed request each map to that prefix followed by the detail.

Docker

bash
docker run -i ghcr.io/cloudcorprecords/domaintrack            # stdio MCP serverdocker run --rm ghcr.io/cloudcorprecords/domaintrack lookup_domain '{"domain":"example.com"}'

Configuration

  • DOMDUCK_MCP_URL — overrides the upstream endpoint, which defaults to https://domduck.com/api/mcp/public. (This override is a reconstruction on our side; the endpoint itself is the pinned public one.)

Development

bash
npm installnpm run build   # tsc -> dist/npm test        # node test runner via tsx; stubbed upstream, no networknpm run dev     # run the CLI from source

License

MIT — see LICENSE.

Source: README.md at commit d20bf4d

Tools

3

lookup_domain

Look up one domain

Public reputation snapshot for one domain from Domduck's store: Domain Rating, Tranco rank, OpenPageRank, registration date, TLS certificate state and AI crawler policy. Returns hasReading false for a domain nobody has looked up yet, which is a real answer and not an error. One domain per call, and no history: the dated series is what a Domduck account is for.

Parametersdomainrequired

get_ai_crawler_policy

Get AI crawler policy

Which of the eight tracked AI crawlers a domain's robots.txt admits, and whether it publishes an llms.txt. Three states per agent: allowed, disallowed, unspecified. Unspecified is NOT allowed, because a catch-all Disallow blocks an agent the file never names, so read `effective` for what is in force. Reads the last stored reading; it does not fetch the file.

Parametersdomainrequired

list_sources

List data sources

What Domduck reads and what each source means, including the eight AI crawlers whose robots.txt policy is tracked. A constant. Read it first: it is what lets a model interpret lookup_domain without guessing at field names or at which direction is better.

Takes no parameters.

Version history

1
  1. v0.1.0LatestNov 4, 2026

Score

90% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 days25 pts
  • Auth declared10 pts

    Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.

  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts
  • License10 pts