# Quietwork Payouts (remote · qw-payouts.quietworklabs.workers.dev)

Check crypto payout lists (EIP-55, dupes, totals) + Cherum batch-payout link. 0.3% fee disclosed.

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

## Components

- remote · `qw-payouts.quietworklabs.workers.dev`: 64/100 (this document), [markdown](https://verifymcp.io/servers/dev-workers-quietworklabs-qw-payouts-quietwork-payouts/qw-payouts.md), [page](https://verifymcp.io/servers/dev-workers-quietworklabs-qw-payouts-quietwork-payouts/qw-payouts)

## Channel facts

- Endpoint: `https://qw-payouts.quietworklabs.workers.dev/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**: 46/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 2 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS enforcement could not be verified: the plaintext port answered with HTTP 405, which proves neither a plaintext path nor enforcement.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 67/100
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 297 tokens (~148/item across 2 items; 2 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 37/100
  - Stability observed for 11 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.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 3 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### How do I install the Quietwork Payouts MCP server?

Quietwork Payouts is a hosted endpoint at https://qw-payouts.quietworklabs.workers.dev/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 dev-workers-quietworklabs-qw-payouts-quietwork-p 'https://qw-payouts.quietworklabs.workers.dev/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "dev-workers-quietworklabs-qw-payouts-quietwork-p": {
      "url": "https://qw-payouts.quietworklabs.workers.dev/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "dev-workers-quietworklabs-qw-payouts-quietwork-p": {
      "type": "http",
      "url": "https://qw-payouts.quietworklabs.workers.dev/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.dev-workers-quietworklabs-qw-payouts-quietwork-p]
url = "https://qw-payouts.quietworklabs.workers.dev/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "dev-workers-quietworklabs-qw-payouts-quietwork-p": {
      "type": "remote",
      "url": "https://qw-payouts.quietworklabs.workers.dev/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add dev-workers-quietworklabs-qw-payouts-quietwork-p --url 'https://qw-payouts.quietworklabs.workers.dev/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  dev-workers-quietworklabs-qw-payouts-quietwork-p:
    url: "https://qw-payouts.quietworklabs.workers.dev/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "dev-workers-quietworklabs-qw-payouts-quietwork-p": {
      "Transport": "http",
      "Url": "https://qw-payouts.quietworklabs.workers.dev/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add dev-workers-quietworklabs-qw-payouts-quietwork-p -t streamable-http -u 'https://qw-payouts.quietworklabs.workers.dev/mcp'
```

### Other

```json
{
  "mcpServers": {
    "dev-workers-quietworklabs-qw-payouts-quietwork-p": {
      "type": "http",
      "url": "https://qw-payouts.quietworklabs.workers.dev/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-05 (score 64, +1)

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

### 2026-11-03 (score 63, +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-01 (score 62, +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-10-30 (score 61, +1)

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

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

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

### 2026-10-26 (score 59, +1)

- [functional improvement] Stability: unverified → 0.03
- [functional improvement] Tool “check_payout_list” now declares an output schema
- [functional improvement] Tool “payout_links” now declares an output schema
- [functional] First check of Tool coverage: 100
- [functional] Server version: 1.0.0 → 1.0.1

### 2026-10-25 (score 58)

First indexed and scored.

## MCP tools (2)

### `payout_links` (~45 tokens)

Get the hosted, non-custodial Cherum batch-payout and multi-chain fan-out links (the user signs in their own wallet), with the full fee and risk disclosure.

Output parameters:

- `batchPayouts` (string)
- `fanoutSend` (string)
- `fees`
- `operator` (string)
- `page` (string)
- `risk` (string)

### `check_payout_list` (~158 tokens)

Validate a payout list before paying many wallets: parses 'address,amount' rows (CSV/TSV/space), checks EVM address format and EIP-55 checksums, flags zero/invalid amounts, duplicate and zero addresses, merges duplicates on request, and returns totals, a clean CSV ready to paste into the batch-payout card, and the fee estimate. Pure computation; nothing is stored or sent.

Input parameters:

- `decimals` (integer): Max decimals allowed for the token (default 6, e.g. USDC)
- `mergeDuplicates` (boolean): Sum amounts for repeated addresses (default false: duplicates are reported as issues)
- `rows` (string, required): One recipient per line: address,amount (header line optional)

Output parameters:

- `csv` (string): address,amount lines ready for the batch-payout card
- `estimatedFees` (object)
- `issues` (array)
- `note` (string)
- `ok` (boolean)
- `payWith` (string)
- `recipients` (integer)
- `total` (string)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/dev-workers-quietworklabs-qw-payouts-quietwork-payouts/qw-payouts#diagnostics

## Score history

- 2026-11-05: 64
- 2026-11-04: 63
- 2026-11-03: 63
- 2026-11-02: 62
- 2026-11-01: 62
- 2026-10-31: 61
- 2026-10-30: 61
- 2026-10-29: 60
- 2026-10-28: 60
- 2026-10-27: 59
- 2026-10-26: 59
- 2026-10-25: 58

## Common questions

### What is the Quietwork Payouts MCP server?

Quietwork Payouts is an MCP server listed in the public MCP registry as dev.workers.quietworklabs.qw-payouts/quietwork-payouts. Check crypto payout lists (EIP-55, dupes, totals) + Cherum batch-payout link. 0.3% fee disclosed. This page covers its hosted endpoint (https://qw-payouts.quietworklabs.workers.dev/mcp).

### Is the Quietwork Payouts MCP server safe to use?

Quietwork Payouts scores 64 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 Quietwork Payouts MCP server expose?

Quietwork Payouts exposes 2 tools: payout_links, check_payout_list. Their descriptions and schemas cost roughly 203 tokens of context every time the server is loaded.

### Does the Quietwork Payouts MCP server require authentication?

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

### Is the Quietwork Payouts MCP server still maintained?

Quietwork Payouts 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://qw-payouts.quietworklabs.workers.dev/mcp
- Website: https://qw-payouts.quietworklabs.workers.dev/
- Changelog RSS feed: https://verifymcp.io/servers/dev-workers-quietworklabs-qw-payouts-quietwork-payouts/qw-payouts.xml
- Changelog JSON feed: https://verifymcp.io/servers/dev-workers-quietworklabs-qw-payouts-quietwork-payouts/qw-payouts.json
- HTML version of this page: https://verifymcp.io/servers/dev-workers-quietworklabs-qw-payouts-quietwork-payouts/qw-payouts