# work.dutiful/dutiful (remote · dutiful.work)

Cited company background reports for agents from official registries. $3 per report via x402.

- Trust score: 72/100 (medium)
- Change this week: −1
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `dutiful.work`: 72/100 (this document), [markdown](https://verifymcp.io/servers/work-dutiful-dutiful/dutiful.md), [page](https://verifymcp.io/servers/work-dutiful-dutiful/dutiful)

## Channel facts

- Endpoint: `https://dutiful.work/mcp`
- 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-11-05.

- **Endpoint Security**: 69/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 enforcement could not be verified: the plaintext port answered with HTTP 404, which proves neither a plaintext path nor enforcement.
  - 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**: 74/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 380 tokens (~126/item across 3 items; 3 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 33/100
  - Stability observed for 10 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the work.dutiful/dutiful MCP server?

work.dutiful/dutiful is a hosted endpoint at https://dutiful.work/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http work-dutiful-dutiful 'https://dutiful.work/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "work-dutiful-dutiful": {
      "url": "https://dutiful.work/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "work-dutiful-dutiful": {
      "type": "http",
      "url": "https://dutiful.work/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.work-dutiful-dutiful]
url = "https://dutiful.work/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "work-dutiful-dutiful": {
      "type": "remote",
      "url": "https://dutiful.work/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add work-dutiful-dutiful --url 'https://dutiful.work/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  work-dutiful-dutiful:
    url: "https://dutiful.work/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "work-dutiful-dutiful": {
      "Transport": "http",
      "Url": "https://dutiful.work/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add work-dutiful-dutiful -t streamable-http -u 'https://dutiful.work/mcp'
```

### Other

```json
{
  "mcpServers": {
    "work-dutiful-dutiful": {
      "type": "http",
      "url": "https://dutiful.work/mcp"
    }
  }
}
```

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-11-04 (score 72, +1)

No change was recorded against any check on this day. Stability & Change Management went from 27 to 30. That category is still filling its 30-day observation window: 8 days of observed history at the previous scan, 9 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-02 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 20 to 23. That category is still filling its 30-day observation window: 6 days of observed history at the previous scan, 7 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-11-01 (score 70, −4)

- [security regression] HTTPS: pass → unverified

### 2026-10-30 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-28 (score 73, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-10-27 (score 72, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-10-26 (score 72)

First indexed and scored.

## MCP tools (3)

### `check_coverage` (~141 tokens)

Check coverage

Free. Searches the official company register of the given country for the company name and returns the matching entities (idx, registry reference, name, address), an order id, and what a report covers. Nothing is charged. Supported country codes: GB, FR, NO, FI, CZ, EE, SK, LV, IL, CA, CY, US (CA: federal corporations only; US: SEC reporting companies only).

Input parameters:

- `company` (string, required): Company name to look up.
- `country` (string, required): Two-letter country code: GB, FR, NO, FI, CZ, EE, SK, LV, IL, CA, CY, US.

### `create_order` (~130 tokens)

Create order

Selects one entity from the check_coverage results (idx, starting at 0) and returns the x402 payment requirements for a report (USDC on Base, exact amount in the requirements). This tool does not pay. To pay, send the signed payment in a PAYMENT-SIGNATURE header to the returned pay_url, then read the report with get_report.

Input parameters:

- `company` (string, required): Same company name used in check_coverage.
- `country` (string, required): Same country code used in check_coverage.
- `idx` (integer, required): Index of the chosen entity in the check_coverage candidates.

### `get_report` (~70 tokens)

Get report

Returns the status of an order and, once delivered, the report (structured JSON and plain text). Status values: pending_entity, pending_payment, paid, delivered. An unpaid order returns its payment requirements.

Input parameters:

- `order_id` (string, required): Order id (UUID) returned by check_coverage or create_order.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/work-dutiful-dutiful/dutiful#diagnostics

## Score history

- 2026-11-05: 72
- 2026-11-04: 72
- 2026-11-03: 71
- 2026-11-02: 71
- 2026-11-01: 70
- 2026-10-31: 74
- 2026-10-30: 74
- 2026-10-29: 73
- 2026-10-28: 73
- 2026-10-27: 72
- 2026-10-26: 72

## Common questions

### What is the work.dutiful/dutiful MCP server?

work.dutiful/dutiful is an MCP server listed in the public MCP registry as work.dutiful/dutiful. Cited company background reports for agents from official registries. $3 per report via x402. This page covers its hosted endpoint (https://dutiful.work/mcp).

### Is the work.dutiful/dutiful MCP server safe to use?

work.dutiful/dutiful scores 72 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

### What tools does the work.dutiful/dutiful MCP server expose?

work.dutiful/dutiful exposes 3 tools: check_coverage, create_order, get_report. Their descriptions and schemas cost roughly 341 tokens of context every time the server is loaded.

### Does the work.dutiful/dutiful MCP server require authentication?

No. We connected to work.dutiful/dutiful without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the work.dutiful/dutiful MCP server still maintained?

work.dutiful/dutiful is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

## Links

- Remote endpoint: https://dutiful.work/mcp
- Repository: https://github.com/dutiful-hq/dutiful-mcp
- Changelog RSS feed: https://verifymcp.io/servers/work-dutiful-dutiful/dutiful.xml
- Changelog JSON feed: https://verifymcp.io/servers/work-dutiful-dutiful/dutiful.json
- HTML version of this page: https://verifymcp.io/servers/work-dutiful-dutiful/dutiful