Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

ClauseAI

REMOTE · CLAUSEAI.EXE.XYZ · SCANNED SEP 20

Generate attorney-drafted NDAs, MSAs, DPAs, and more as PDF, ODT, or Markdown. No account required.

Available components

+4 this week 71 Trust /100
Trust breakdown (7 categories)

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 Security63
Transport & Reachability100
Schema Quality & AI Usability79
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 213 tokens (~71/item across 3 items; 3 tools + 0 resources), lean.Pass
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management27
  • Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage94
  • 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
  • 80% of tool parameters carry a description.Partial
  • Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 4 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
  • Implements a current MCP spec version (2026-07-28).Pass
Install

How do I install the ClauseAI MCP server?

ClauseAI is a hosted endpoint at https://clauseai.exe.xyz/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 · clauseai.exe.xyz

# add to Claude Code
claude mcp add --transport http wasauce-clauseai 'https://clauseai.exe.xyz/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "wasauce-clauseai": {
      "url": "https://clauseai.exe.xyz/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "wasauce-clauseai": {
      "type": "http",
      "url": "https://clauseai.exe.xyz/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.wasauce-clauseai]
url = "https://clauseai.exe.xyz/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wasauce-clauseai": {
      "type": "remote",
      "url": "https://clauseai.exe.xyz/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add wasauce-clauseai --url 'https://clauseai.exe.xyz/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  wasauce-clauseai:
    url: "https://clauseai.exe.xyz/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "wasauce-clauseai": {
      "Transport": "http",
      "Url": "https://clauseai.exe.xyz/mcp"
    }
  }
}
# add to Vellum
assistant mcp add wasauce-clauseai -t streamable-http -u 'https://clauseai.exe.xyz/mcp'
// mcp.json
{
  "mcpServers": {
    "wasauce-clauseai": {
      "type": "http",
      "url": "https://clauseai.exe.xyz/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 20 Sept 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.

  • 18 Sept 26 +1

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

  • 16 Sept 26 +1

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

  • 14 Sept 26 +1

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

  • 13 Sept 26 0
    • Stability: unverified → 0.03 functional
  • 12 Sept 26 +42
    • Injection markers: unverified → pass security
    • Transport: fail → pass security
    • First check of Judged manipulation: pass security
    • Authorization: Authorisation not fully verified: no authorisation is required to call this server, and 3 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe. security
    • Tool coverage: unverified → 100 functional
    • MCP protocol: unverified → pass functional
    • First check of Schema quality: fail functional
    • First check of Schema quality: excellent functional
    • First check of Destructive annotations: pass functional
    • First check of Schema quality: pass functional
    • First check of Tool coverage: 80 functional
    • First check of Tool coverage: 100 functional
  • 11 Sept 26 25

    First indexed and scored.

Diagnostics

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 20 Sept 2026 · Probed https://clauseai.exe.xyz/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=exe.xyz CN=YR1,O=Let's Encrypt,C=US 1 Aug 2026 30 Oct 2026 RSA 2048 SHA256-RSA 624f569bbd25acfc4950b2b4ed8e0194881
SANs: *.exe.xyz, exe.xyz
CN=YR1,O=Let's Encrypt,C=US (CA) CN=Root YR,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 RSA 2048 SHA256-RSA a20253f15f2691c05dc1ce13b9bcca4e
CN=Root YR,O=ISRG,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 RSA 4096 SHA256-RSA f24b6d17f9d9ad7cb1c9fea78782699f

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of clauseai.exe.xyz. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
xyz. present 3599, 18130 8, 8 Verified
exe.xyz. absent 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=63072000; includeSubDomains; preload

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://clauseai.exe.xyz/mcp Verified 200
http (plaintext) http://clauseai.exe.xyz/mcp HTTPS enforced 301 https://clauseai.exe.xyz/mcp
MCP tools · 3 exposed · ~154 tokens

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 →

Tool Tokens
generate_document ~90

Generate a filled legal document (PDF, ODT, or Markdown) from a template slug and answers. No account required.

NameTypeReqDescription
answersMap of field keys to values. Missing keys stay as placeholders.
emailOptional contact email recorded with the generation.
formatstringpdf, odt, or markdown.
slugstringyesTemplate slug from list_templates.

Structured output declared, but exposes no named fields.

No examples provided.

get_template_fields ~30

Get the fill-in fields for one legal template before generating a document.

NameTypeReqDescription
slugstringyes

Structured output declared, but exposes no named fields.

No examples provided.

list_templates ~34

List attorney-drafted startup legal templates (NDA, MSA, DPA, privacy policy, offer letter, and more).

Input schema present but exposes no named parameters.

NameTypeReqDescription
resultarrayyes

No examples provided.

Common questions

What is the ClauseAI MCP server?

ClauseAI is an MCP server listed in the public MCP registry as io.github.wasauce/clauseai. Generate attorney-drafted NDAs, MSAs, DPAs, and more as PDF, ODT, or Markdown. No account required. This page covers its hosted endpoint (https://clauseai.exe.xyz/mcp).

Is the ClauseAI MCP server safe to use?

ClauseAI scores 71 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 ClauseAI MCP server expose?

ClauseAI exposes 3 tools: list_templates, get_template_fields, generate_document. Their descriptions and schemas cost roughly 154 tokens of context every time the server is loaded.

Does the ClauseAI MCP server require authentication?

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

Is the ClauseAI MCP server still maintained?

ClauseAI is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.