INDIVIDUAL MCP TOOL

get_case

Fetch one decided DOHA case in full: what was alleged, the judge's findings per allegation, per-guideline formal findings, outcome, judge, representation, and appeal history.

clearancesearchengine.comnone authenticationAvailability not checked

LIVE ENDPOINT

https://www.clearancesearchengine.com/api/mcp

No auth detected

Connect to this endpoint to inspect the live schema for get_case and invoke it with your own arguments.

Indexed input schema

{}

Risk classification

Inferred read-only · medium confidence · heuristic, not a guarantee.

A tool name or description suggests retrieving external content.

Parent server

clearancesearchengine.com

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.case-doha-record]
url = "https://www.clearancesearchengine.com/api/mcp"
enabled = true

Claude Code

.mcp.json

{
  "mcpServers": {
    "case-doha-record": {
      "type": "http",
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}

Claude Desktop

Settings → Connectors → Add custom connector

Name: case-doha-record
Remote MCP URL: https://www.clearancesearchengine.com/api/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": {
    "case-doha-record": {
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}

Visual Studio Code

.vscode/mcp.json

Add to Visual Studio Code

{
  "servers": {
    "case-doha-record": {
      "type": "http",
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}

Generic MCP

Client-specific MCP configuration

{
  "name": "case-doha-record",
  "transport": "streamable-http",
  "url": "https://www.clearancesearchengine.com/api/mcp"
}

MCP Inspector

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

Related tools

search_cases — Search 30,000+ decided public DOHA security-clearance decisions (1996 to present).
similar_cases — The most similar decided cases to a given case, ranked by how alike the ALLEGATIONS read (never by outcome).
get_statistics — Grant/denial statistics over decided hearing-level DOHA cases, grouped by year or by guideline, always with sample sizes.
get_timelines — Measured DOHA timelines: median days from Statement of Reasons to hearing and to decision, from dates stated in the decisions themselves.
get_conduct_recency — How much time had passed between the most recent conduct and the decision, measured from dates stated in the decisions, for the incident-type concerns (drugs, alcohol, criminal conduct, sexual behavior, protected information, IT misuse).
get_candor_outcomes — How cases with a candor allegation (falsification, omission, or lack of candor) were resolved in the decided record: the favorable rate with vs without such an allegation, when the judge found a deliberate falsification vs when the applicant rebutted it, and when the applicant corrected the record before being confronted.