Remote MCP · Endpoint

Claim Done MCP server

No. Claim Done answered an MCP handshake 43 minutes ago.

UpLast checked 43 minutes ago

Server URL

https://claimdone.com.au/mcp

The last check completed an MCP handshake.

Registry name
au.com.claimdone/claimdone
Transport
Streamable HTTP
Protocol negotiated
2025-06-18
Handshake latency
646 ms
Tools exposed
8 tools
Uptime, last 30 days
92.9% from 14 checks
Described by its publisher as
Australian legal documents drafted from your answers for a flat fee. Not a law firm.
Listing
From the official MCP registry (active).
Recent checks of Claim Done
CheckedResultHandshake
43 minutes agoHandshake completed646 ms
8 days agoHandshake completed679 ms
9 days agoHandshake completed650 ms
11 days agoHandshake completed648 ms
12 days agoFailed - the request timed out—
13 days agoHandshake completed645 ms
14 days agoHandshake completed644 ms
14 days agoHandshake completed688 ms
16 days agoHandshake completed665 ms
19 days agoHandshake completed646 ms
21 days agoHandshake completed656 ms
24 days agoHandshake completed661 ms
26 days agoHandshake completed646 ms
28 days agoHandshake completed637 ms

The last 14 checks. Full history is kept for 30 days; the all-time counter stands at 15 responding of 16.

How to read this

  • ·Handshake latency is one measurement from one probe, from our infrastructure. It is a smoke signal about the endpoint, not a benchmark of your own connection to it.
  • ·An authentication challenge counts as responding. A hosted server that refuses an anonymous prober is behaving correctly.
  • ·A tool count of “behind credentials” means the handshake worked but listing tools needed a token we do not hold.
  • ·Uptime covers the last 30 days of our own checks, at most one an hour, and says how many checks it is drawn from.

Listing data comes from the official MCP registry. Glide is not affiliated with Claim Done and makes no claim about it beyond what these checks measured.