Claim Done
REMOTE · CLAIMDONE.COM.AU
Australian legal documents drafted from your answers for a flat fee. Not a law firm.
Available components
Last scanned (7 hours ago)
Scores higher than 84% of remote servers
Reachable. Last reached 5 Nov 2026.
Category Documents and Files
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- 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. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability71
- AI-judged instruction clarity (good).Pass
- 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. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management73
- Stability observed for 22 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 8 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 9 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
Checks we ran (13)
- TLS certificate
- Authorization
- HTTPS
- HSTS header
- DNSSEC
- Transport
- Schema quality
- Stability
- Tool coverage
- Injection markers
- Destructive annotations
- Judged manipulation
- MCP protocol
Does not apply to this hosted endpoint (2)
- Supply Chain SecurityScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
- Provenance & TransparencyScored on package channels only. This is a hosted endpoint, so there is nothing to install or inspect.
The score does not measure everything. What the score does not measure →
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +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.
- 1 Nov 26 +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.
- 30 Oct 26 +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.
- 28 Oct 26 +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.
- 26 Oct 26 +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.
- 24 Oct 26 +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.
- 22 Oct 26 +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.
- 19 Oct 26 0
- 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 security
- Schema quality: pass → fail ▼ functional
- Server version: 1.0.0 → 1.1.0 functional
- New tool “prepare_protected_draft” functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Probed https://claimdone.com.au/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=claimdone.com.au | CN=YE2,O=Let's Encrypt,C=US | 13 Oct 2026 | 11 Jan 2027 | ECDSA 256 | ECDSA-SHA384 | 53ed1037464a64a53194f643fdecbb4cc4a |
| SANs: claimdone.com.au, www.claimdone.com.au | ||||||
| CN=YE2,O=Let's Encrypt,C=US (CA) | CN=Root YE,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | ECDSA 384 | ECDSA-SHA384 | 4df3b15dd6c0784c507cd37b58e6f115 |
| CN=Root YE,O=ISRG,C=US (CA) | CN=ISRG Root X2,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | ECDSA-SHA384 | 872165fc34b6e5fba8add5b3705fb53a |
| CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | ECDSA 384 | SHA256-RSA | 6c8f1dc727c7117f7baf853ac980f9cd |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of claimdone.com.au. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | Trust anchor | 20326, 38696 | 8, 8 | Verified |
| au. | DS published | 26642 | 8 | Verified |
| com.au. | DS published | 14185 | 8 | Verified |
| claimdone.com.au. | No DS | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=31536000 |
| x-content-type-options | nosniff |
| x-frame-options | SAMEORIGIN |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=(), payment=(self "https://js.stripe.com" "https://checkout.stripe.com") |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://claimdone.com.au/mcp | Verified | 200 | |
| http (plaintext) | http://claimdone.com.au/mcp | HTTPS enforced | 301 | https://claimdone.com.au/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
answer_questions Answer the questions for a document ~108
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The access_token returned by start_document. |
| answers | object | yes | Question key => the person's answer. For a question with choices, pass one choice exactly. |
| case_id | integer | yes | The case id returned by start_document. |
No output schema declared.
No examples provided.
get_document Read the drafted document ~92
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The access_token returned by start_document. |
| case_id | integer | yes | The case id returned by start_document. |
No output schema declared.
No examples provided.
get_payment_link Get the payment link ~166
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | 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 | yes | The case id returned by start_document. |
| registered_post | boolean | – | Add registered post delivery of a letter (extra fee, shown in list_services). |
No output schema declared.
No examples provided.
get_status Check a case ~74
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The access_token returned by start_document. |
| case_id | integer | yes | The case id returned by start_document. |
No output schema declared.
No examples provided.
list_services List the documents Claim Done drafts ~57
Every document Claim Done drafts, with its live flat price in AUD, what the person receives and how it is delivered.
| Name | Type | Req | Description |
|---|---|---|---|
| query | string | – | Optional word to filter by, e.g. "tenant", "invoice", "tribunal". |
No output schema declared.
No examples provided.
match_problem Match a situation to the right document ~67
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.
| Name | Type | Req | Description |
|---|---|---|---|
| problem | string | yes | The situation in the person's own words, 10 to 500 characters. |
No output schema declared.
No examples provided.
prepare_protected_draft Create the protected draft before payment ~101
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.
| Name | Type | Req | Description |
|---|---|---|---|
| access_token | string | yes | The access_token returned by start_document. |
| case_id | integer | yes | The case id returned by start_document. |
No output schema declared.
No examples provided.
start_document Start a document ~151
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.
| Name | Type | Req | Description |
|---|---|---|---|
| service | string | yes | Service slug from list_services or match_problem, e.g. "letter-of-demand". |
| state | string | yes | The person's Australian state or territory. |
| what_happened | string | yes | What happened, in the person's words (2 to 6 sentences). |
| your_email | string | yes | The person's email address: the draft, the receipt and the dashboard link go there. |
| your_name | string | yes | The person's full name or business name, as it should appear on the document. |
No output schema declared.
No examples provided.
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.
remote · claimdone.com.au
claude mcp add --transport http au-com-claimdone-claimdone 'https://claimdone.com.au/mcp'
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.