# Domduck (remote · domduck.com)

Domain reputation over time: Domain Rating, Tranco rank, TLS, and AI crawler policy.

- Trust score: 72/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `domduck.com`: 36/100, [markdown](https://verifymcp.io/servers/com-domduck-domduck/api-mcp.md), [page](https://verifymcp.io/servers/com-domduck-domduck/api-mcp)
- remote · `domduck.com`: 72/100 (this document), [markdown](https://verifymcp.io/servers/com-domduck-domduck/api-mcp-public.md), [page](https://verifymcp.io/servers/com-domduck-domduck/api-mcp-public)

## Channel facts

- Endpoint: `https://domduck.com/api/mcp/public`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 409 tokens (~136/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a current MCP spec version (2026-07-28).

**Unverified: 1 category.** A category scored 0 because we could not verify it: authentication we do not have, an unreachable endpoint, or not enough scan history. We only credit what we can confirm.

## Install

### Claude

```bash
claude mcp add --transport http com-domduck-domduck https://domduck.com/api/mcp/public
```

### Codex

```toml
[mcp_servers.com-domduck-domduck]
url = "https://domduck.com/api/mcp/public"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-domduck-domduck": {
      "type": "remote",
      "url": "https://domduck.com/api/mcp/public",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-domduck-domduck --url https://domduck.com/api/mcp/public --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-domduck-domduck:
    url: "https://domduck.com/api/mcp/public"
```

### Other

```json
{
  "mcpServers": {
    "com-domduck-domduck": {
      "type": "http",
      "url": "https://domduck.com/api/mcp/public"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 72)

First indexed and scored.

## MCP tools (3)

### `lookup_domain` (~105 tokens)

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.

Input parameters:

- `domain` (string, required): A domain name. Scheme, www and trailing dots are stripped.

### `get_ai_crawler_policy` (~110 tokens)

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.

Input parameters:

- `domain` (string, required): A domain name. Scheme, www and trailing dots are stripped.

### `list_sources` (~59 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-domduck-domduck/api-mcp-public#diagnostics

## Score history

- 2026-08-03: 72

## Links

- Remote endpoint: https://domduck.com/api/mcp/public
- Website: https://domduck.com/
- Changelog RSS feed: https://verifymcp.io/servers/com-domduck-domduck/api-mcp-public/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-domduck-domduck/api-mcp-public/changelog.json
- HTML version of this page: https://verifymcp.io/servers/com-domduck-domduck/api-mcp-public