Content Tools

claimdone.com.au

MCP server for Claim Done that matches legal problems to document templates, collects case answers, and generates Stripe payment links.

1 endpoint7 known toolsFirst detected October 13, 2026Last detected October 13, 2026

ENDPOINT 1

https://claimdone.com.au/mcp

No auth detected

MCP server metadata

Name: Claim Done
Version: 1.0.0

Capabilities

tools

Server instructions

Claim Done drafts Australian legal documents (letters of demand, tribunal applications, cease and desist letters, notices, agreements) from a person's answers for a flat fee in AUD. Flow: match_problem (optional) -> start_document -> answer_questions until ready_to_pay -> get_payment_link (the person pays on Stripe's hosted page) -> get_status / get_document. Claim Done is not a law firm and does not give legal advice; the person reads and approves every document on their dashboard before anything is sent. Never invent facts: ask the person for each answer.

Known tools 7

list_services

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

Inferred read-only

match_problem

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.

Inferred read-only

start_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.

Inferred read-only

answer_questions

Saves the person's answers (question key => answer) for a case.

Inferred read-only

get_payment_link

Returns a hosted Stripe Checkout URL for the case at the live flat price, for the person to pay.

Potential side effects

get_status

Whether the case is paid, whether the draft is ready, and the dashboard link where the person reads, edits and approves it.

Inferred read-only

get_document

After payment: the full text of each drafted document, plus the dashboard link where the person reads, edits and approves it (and, for letters, has it sent).

Potential side effects

CONNECT WITH APPROVAL

Client installation

Review this server and its permissions before adding it. Secret placeholders must be set locally.

Codex

~/.codex/config.toml

[mcp_servers.claim-done]
url = "https://claimdone.com.au/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "claim-done": {
      "type": "http",
      "url": "https://claimdone.com.au/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: claim-done
Remote MCP URL: https://claimdone.com.au/mcp

Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.

Cursor

.cursor/mcp.json

{
  "mcpServers": {
    "claim-done": {
      "url": "https://claimdone.com.au/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

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

Generic MCP

Client-specific MCP configuration

{
  "name": "claim-done",
  "transport": "streamable-http",
  "url": "https://claimdone.com.au/mcp"
}

MCP Inspector

Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.

TRUST AND VERIFICATION EVIDENCE

Loading Trust v2 evidence…

Checking the associated registrable domain. The BuiltWith key remains server-side.

Indexed

Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.