# Claim Done (remote · claimdone.com.au)

Australian legal documents drafted from your answers for a flat fee. Not a law firm.

- Trust score: 81/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `claimdone.com.au`: 81/100 (this document), [markdown](https://verifymcp.io/servers/au-com-claimdone-claimdone/claimdone.md), [page](https://verifymcp.io/servers/au-com-claimdone-claimdone/claimdone)

## Channel facts

- Endpoint: `https://claimdone.com.au/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**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - 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**: 71/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1063 tokens (~132/item across 8 items; 8 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 73/100
  - Stability observed for 22 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 8 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 9 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 Claim Done MCP server?

Claim Done is a hosted endpoint at https://claimdone.com.au/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 au-com-claimdone-claimdone 'https://claimdone.com.au/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "au-com-claimdone-claimdone": {
      "url": "https://claimdone.com.au/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "au-com-claimdone-claimdone": {
      "type": "http",
      "url": "https://claimdone.com.au/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.au-com-claimdone-claimdone]
url = "https://claimdone.com.au/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add au-com-claimdone-claimdone --url 'https://claimdone.com.au/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  au-com-claimdone-claimdone:
    url: "https://claimdone.com.au/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "au-com-claimdone-claimdone": {
      "Transport": "http",
      "Url": "https://claimdone.com.au/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add au-com-claimdone-claimdone -t streamable-http -u 'https://claimdone.com.au/mcp'
```

### Other

```json
{
  "mcpServers": {
    "au-com-claimdone-claimdone": {
      "type": "http",
      "url": "https://claimdone.com.au/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-03 (score 81, +1)

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

### 2026-11-01 (score 80, +1)

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

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

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

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

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

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

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

### 2026-10-24 (score 76, +1)

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

### 2026-10-22 (score 75, +1)

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

### 2026-10-19 (score 74, 0)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “answer_questions” rewrote its description, which is the text the model reads
- [security] Tool “get_document” rewrote its description, which is the text the model reads
- [security] Tool “get_payment_link” rewrote its description, which is the text the model reads
- [security] Tool “get_status” rewrote its description, which is the text the model reads
- [functional regression] Schema quality: pass → fail
- [functional] Server version: 1.0.0 → 1.1.0
- [functional] New tool “prepare_protected_draft”

## MCP tools (8)

### `list_services` (~57 tokens)

List the documents Claim Done drafts

Every document Claim Done drafts, with its live flat price in AUD, what the person receives and how it is delivered.

Input parameters:

- `query` (string): Optional word to filter by, e.g. "tenant", "invoice", "tribunal".

### `match_problem` (~67 tokens)

Match a situation to the right document

Takes a plain-English description of the person's problem (who, what happened, what they want) and returns the Claim Done document that fits, its price in AUD, and what it does.

Input parameters:

- `problem` (string, required): The situation in the person's own words, 10 to 500 characters.

### `start_document` (~151 tokens)

Start a document

Creates a Claim Done case for a document and returns the questions the person needs to answer, with a case_id and access_token for the later steps. Nothing is charged at this step.

Input parameters:

- `service` (string, required): Service slug from list_services or match_problem, e.g. "letter-of-demand".
- `state` (string, required): The person's Australian state or territory.
- `what_happened` (string, required): What happened, in the person's words (2 to 6 sentences).
- `your_email` (string, required): The person's email address: the draft, the receipt and the dashboard link go there.
- `your_name` (string, required): The person's full name or business name, as it should appear on the document.

### `answer_questions` (~108 tokens)

Answer the questions for a document

Saves the person's answers (question key => answer) for a case. Returns any questions still open and, for eligible ordinary documents, ready_for_protected_draft when the real protected draft can be created for $0 before payment.

Input parameters:

- `access_token` (string, required): The access_token returned by start_document.
- `answers` (object, required): Question key => the person's answer. For a question with choices, pass one choice exactly.
- `case_id` (integer, required): The case id returned by start_document.

### `prepare_protected_draft` (~101 tokens)

Create the protected draft before payment

For an eligible ordinary document whose questions are complete, starts the real draft for $0 and returns the private dashboard link. The person reviews authorised, watermarked raster pages there. Raw unpaid text and original PDF/DOCX files are never returned by the connector. Daily, email and network limits apply.

Input parameters:

- `access_token` (string, required): The access_token returned by start_document.
- `case_id` (integer, required): The case id returned by start_document.

### `get_payment_link` (~166 tokens)

Get the payment link

Returns a hosted Stripe Checkout URL at the live flat price. For an eligible ordinary document, the protected draft must already be ready and the person must have accepted the private review; payment then unlocks the clean PDF, download and delivery options. Purpose-built report/workspace flows may require payment before drafting. If an eligibility notice is returned, the person must hear it before acknowledge_notice is true.

Input parameters:

- `access_token` (string, required): The access_token returned by start_document.
- `acknowledge_notice` (boolean): Set true after the person has heard the eligibility notice returned by answer_questions or a previous call.
- `case_id` (integer, required): The case id returned by start_document.
- `registered_post` (boolean): Add registered post delivery of a letter (extra fee, shown in list_services).

### `get_status` (~74 tokens)

Check a case

Whether the case is paid, whether a protected draft is processing or ready, whether the person accepted the review, and the private dashboard link. It never returns raw unpaid document text.

Input parameters:

- `access_token` (string, required): The access_token returned by start_document.
- `case_id` (integer, required): The case id returned by start_document.

### `get_document` (~92 tokens)

Read the drafted document

After genuine payment only: the full text of each drafted document, plus the dashboard link where the person approves it (and, for eligible letters, has it sent). Before payment, protected drafts remain watermarked raster pages on the private dashboard and raw text is never returned.

Input parameters:

- `access_token` (string, required): The access_token returned by start_document.
- `case_id` (integer, required): The case id returned by start_document.

## Diagnostics

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

## Score history

- 2026-11-05: 81
- 2026-11-04: 81
- 2026-11-03: 81
- 2026-11-02: 80
- 2026-11-01: 80
- 2026-10-31: 79
- 2026-10-30: 79
- 2026-10-29: 78
- 2026-10-28: 78
- 2026-10-27: 77
- 2026-10-26: 77
- 2026-10-25: 76
- 2026-10-24: 76
- 2026-10-23: 75
- 2026-10-22: 75
- 2026-10-21: 74
- 2026-10-20: 74
- 2026-10-19: 74
- 2026-10-18: 74
- 2026-10-17: 73
- 2026-10-16: 73
- 2026-10-15: 72
- 2026-10-14: 72
- 2026-10-13: 33

## Common questions

### What is the Claim Done MCP server?

Claim Done is an MCP server listed in the public MCP registry as au.com.claimdone/claimdone. Australian legal documents drafted from your answers for a flat fee. Not a law firm. This page covers its hosted endpoint (https://claimdone.com.au/mcp).

### Is the Claim Done MCP server safe to use?

Claim Done scores 81 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 Claim Done MCP server expose?

Claim Done exposes 8 tools: list_services, match_problem, start_document, answer_questions, prepare_protected_draft, and 3 more. Their descriptions and schemas cost roughly 816 tokens of context every time the server is loaded.

### Does the Claim Done MCP server require authentication?

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

### Is the Claim Done MCP server still maintained?

Claim Done 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.

### What did VerifyMCP test on the Claim Done MCP server?

VerifyMCP ran 13 checks on Claim Done, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://claimdone.com.au/mcp
- Website: https://claimdone.com.au/connect-your-ai-assistant/
- Changelog RSS feed: https://verifymcp.io/servers/au-com-claimdone-claimdone/claimdone.xml
- Changelog JSON feed: https://verifymcp.io/servers/au-com-claimdone-claimdone/claimdone/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/au-com-claimdone-claimdone/claimdone.json
- HTML version of this page: https://verifymcp.io/servers/au-com-claimdone-claimdone/claimdone