General Tools

voiceclaw.ca

An MCP server that helps business owners prepare for a sale by generating buyer diligence questions, scoring exit readiness, and listing required diligence documents.

1 endpoint3 known toolsFirst detected October 30, 2026Last detected October 30, 2026

ENDPOINT 1

https://voiceclaw.ca/exit-ready/mcp

No auth detected

MCP server metadata

Name: exit-ready-check
Version: 1.0.0

Capabilities

tools.listChanged

Server instructions

Exit-Ready Check scores how sellable a trades or fleet service business is by whether the questions a buyer asks in diligence can be answered without the owner. Use get_buyer_questions to show the questions, score_exit_readiness once all twelve are answered, and get_diligence_checklist for the records to assemble before listing. Speak plainly. Never invent an answer for the owner.

Known tools 3

get_buyer_questions

Use this when a business owner asks what a buyer will ask for in diligence, or before scoring exit readiness.

Inferred read-only

score_exit_readiness

Use this after the owner has answered all twelve buyer questions from get_buyer_questions.

Inferred read-only

get_diligence_checklist

Use this when an owner asks what documents or records they need to sell their business, or after scoring to show what to gather for the gaps.

Inferred read-only

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.exit-ready-check]
url = "https://voiceclaw.ca/exit-ready/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "exit-ready-check": {
      "type": "http",
      "url": "https://voiceclaw.ca/exit-ready/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: exit-ready-check
Remote MCP URL: https://voiceclaw.ca/exit-ready/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": {
    "exit-ready-check": {
      "url": "https://voiceclaw.ca/exit-ready/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "exit-ready-check": {
      "type": "http",
      "url": "https://voiceclaw.ca/exit-ready/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "exit-ready-check",
  "transport": "streamable-http",
  "url": "https://voiceclaw.ca/exit-ready/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.