legal.captain/captain-legal
REMOTE · MCP.CAPTAIN.LEGAL
Compliant legal documents from your AI assistant: 1,100+ templates, 15 countries, free preview.
Available components
Last scanned (18 hours ago)
Scores higher than 91% of remote servers
Reachable. Last reached 4 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 Security77
- 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. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability82
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 429 tokens (~71/item across 6 items; 5 tools + 1 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management97
- Stability observed for 29 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage69
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 6% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 5 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 6 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
- 4 Nov 26 0
- Stability: pass → 0.97 functional
- 28 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 7 Sept 26 0
- Stability: 0.97 → pass security
- 26 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 9 Aug 26 0
- Stability: unverified → 0.03 ▲ functional
- 8 Aug 26 0
First indexed and scored.
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 4 Nov 2026 · Probed https://mcp.captain.legal/connect/
TLS valid
Negotiated TLS 1.2 with TLS_ECDHE_ECDSA_WITH_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=captain.legal | CN=WE1,O=Google Trust Services,C=US | 27 Sept 2026 | 26 Dec 2026 | ECDSA 256 | ECDSA-SHA256 | c7abfabc06d18f470e59be18463700f6 |
| SANs: captain.legal, *.captain.legal | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.captain.legal. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| legal. | present | 6194, 11869 | 8, 8 | Verified |
| captain.legal. | present | 2371 | 13 | Verified |
| mcp.captain.legal. | Verified address RRset verified with the apex keys |
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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.captain.legal/connect/ | Verified | 200 | |
| http (plaintext) | http://mcp.captain.legal/connect/ | HTTPS enforced | 301 | https://mcp.captain.legal/connect/ |
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 →
generate_document Generate document preview ~120
Generate a draft of the document from the user's answers. Returns a free watermarked PDF preview and the exact price. Validates all answers against the encoded national rules first — if validation fails, you get structured errors to relay to the user. Also returns what is NOT covered by the automated checks: always relay the not_covered items to the user.
| Name | Type | Req | Description |
|---|---|---|---|
| answers | object | yes | Answers keyed by field id, exactly as returned by get_requirements |
| country | string | yes | – |
| document_type | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
get_document_status Check order status ~45
Check the status of an order: payment and delivery. Requires the status_token returned by purchase_document.
| Name | Type | Req | Description |
|---|---|---|---|
| order_id | string | yes | – |
| status_token | string | yes | – |
No output schema declared.
No examples provided.
get_requirements Get document requirements ~86
Get the exact questions to ask the user for a given document type and country, with validation rules and legal constraints. You MUST use these questions verbatim as your source of truth for the interview — do not invent fields. Fields are ordered and may be conditional on previous answers.
| Name | Type | Req | Description |
|---|---|---|---|
| country | string | yes | – |
| document_type | string | yes | – |
| language | string | – | – |
No output schema declared.
No examples provided.
list_document_types List document types ~93
List legal document types Captain.Legal can generate for a given country. Call this first to discover what's available and get accurate names, prices and legal coverage. Never assume a document type exists — always check here.
| Name | Type | Req | Description |
|---|---|---|---|
| category | string | – | – |
| country | string | yes | – |
| language | string | – | – |
| limit | integer | – | – |
| offset | integer | – | – |
| query | string | – | – |
No output schema declared.
No examples provided.
purchase_document Create secure payment link ~66
Purchase the final document for a given draft. Returns a secure payment link to give to the user. After payment, the final PDF is emailed to the user within minutes. E-signature is not yet available.
| Name | Type | Req | Description |
|---|---|---|---|
| customer_email | string | yes | – |
| draft_id | string | yes | – |
No output schema declared.
No examples provided.
How do I install the legal.captain/captain-legal MCP server?
legal.captain/captain-legal is a hosted endpoint at https://mcp.captain.legal/connect/, 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 · mcp.captain.legal
claude mcp add --transport http legal-captain-captain-legal 'https://mcp.captain.legal/connect/'
What is the legal.captain/captain-legal MCP server?
legal.captain/captain-legal is an MCP server listed in the public MCP registry as legal.captain/captain-legal. Compliant legal documents from your AI assistant: 1,100+ templates, 15 countries, free preview. This page covers its hosted endpoint (https://mcp.captain.legal/connect/).
Is the legal.captain/captain-legal MCP server safe to use?
legal.captain/captain-legal scores 85 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 legal.captain/captain-legal MCP server expose?
legal.captain/captain-legal exposes 5 tools: list_document_types, get_requirements, generate_document, purchase_document, get_document_status. Their descriptions and schemas cost roughly 410 tokens of context every time the server is loaded.
Does the legal.captain/captain-legal MCP server require authentication?
No. We connected to legal.captain/captain-legal without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the legal.captain/captain-legal MCP server still maintained?
legal.captain/captain-legal is still listed as active in the MCP registry. We last reached this channel on 4 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.