Index / MCP servers / Case Doha Record

Case Doha Record MCP server

Case Doha Record is an MCP server with 7 tools an agent can call, among them get_candor_outcomes, get_case, get_conduct_recency. It answers at https://www.clearancesearchengine.com/api/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 11 September 2026; the last check, on 22 October 2026, succeeded.

Status
Answering
Tools
7
Reliability
6 of 6 checks
Response time
234 ms
Transport
streamable HTTP
Last checked
22 October 2026

Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record.

Description as the publisher wrote it.

The 7 tools Case Doha Record offers

ToolWhat it does
get_candor_outcomesHow 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 applican
get_caseFetch 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. Use case_id from search_cases.
Inputs: case_id
get_conduct_recencyHow 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). Re
Inputs: guideline
get_statisticsGrant/denial statistics over decided hearing-level DOHA cases, grouped by year or by guideline, always with sample sizes. Same population rules as the site's Insights page.
Inputs: by, guideline, year_from, year_to
get_timelinesMeasured DOHA timelines: median days from Statement of Reasons to hearing and to decision, from dates stated in the decisions themselves. Optionally scoped to one decision year.
Inputs: year
search_casesSearch 30,000+ decided public DOHA security-clearance decisions (1996 to present). Full-text query plus filters. Returns matching cases with outcome, date, guidelines, and a citable URL each.
Inputs: query, guideline, outcome, level, year_from, year_to
similar_casesThe most similar decided cases to a given case, ranked by how alike the ALLEGATIONS read (never by outcome). Same list shown on the case page.
Inputs: case_id, limit

Add Case Doha Record to your AI client

Every block below points at https://www.clearancesearchengine.com/api/mcp. Pick your client and copy.

Claude Code: one command in your terminal
claude mcp add --transport http case-doha-record https://www.clearancesearchengine.com/api/mcp
Claude Desktop: claude_desktop_config.json
{
  "mcpServers": {
    "case-doha-record": {
      "command": "npx",
      "args": ["-y", "mcp-remote", "https://www.clearancesearchengine.com/api/mcp"]
    }
  }
}
Cursor: ~/.cursor/mcp.json, or .cursor/mcp.json in a project
{
  "mcpServers": {
    "case-doha-record": {
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
VS Code and GitHub Copilot: .vscode/mcp.json
{
  "servers": {
    "case-doha-record": {
      "type": "http",
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
Zed: Zed settings.json
{
  "context_servers": {
    "case-doha-record": {
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
Windsurf: ~/.codeium/mcp_config.json
{
  "mcpServers": {
    "case-doha-record": {
      "serverUrl": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
JetBrains AI Assistant: Settings, Tools, AI Assistant, MCP, New MCP Server, as JSON
{
  "mcpServers": {
    "case-doha-record": {
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
Continue: .continue/mcpServers/neuronto.yaml
name: Case Doha Record
version: 0.0.1
schema: v1
mcpServers:
  - name: Case Doha Record
    type: streamable-http
    url: https://www.clearancesearchengine.com/api/mcp
Gemini CLI: ~/.gemini/settings.json
{
  "mcpServers": {
    "case-doha-record": {
      "httpUrl": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
Codex CLI: MCP server config
{
  "mcpServers": {
    "case-doha-record": {
      "type": "http",
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
Warp: MCP servers, + Add, paste JSON
{
  "mcpServers": {
    "case-doha-record": {
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
Goose: a one-click extension link
goose://extension?url=https%3A%2F%2Fwww.clearancesearchengine.com%2Fapi%2Fmcp&type=streamable_http&id=case-doha-record&name=Case%20Doha%20Record

Is Case Doha Record up right now?

It answered our last check on 22 October 2026 in 234 ms. Over 6 checks since 11 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.

MCP servers similar to Case Doha Record

Questions about Case Doha Record

How many tools does Case Doha Record have?

7, as returned by the server's own tools/list on 15 September 2026: get_candor_outcomes, get_case, get_conduct_recency, get_statistics, get_timelines, search_cases, similar_cases.

Is Case Doha Record down?

It answered our last check on 22 October 2026 in 234 ms. Over 6 checks since 11 September 2026 it answered 6.

How do I add Case Doha Record to Cursor?

Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://www.clearancesearchengine.com/api/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.

Does Case Doha Record need an API key?

It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.

Where this comes from

Publisher: io.github.klmlfl. Endpoint host: www.clearancesearchengine.com. ARD identifier: urn:air:io.github.klmlfl:mcp:case-doha-record. First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page is inferred from its name. Ranking in Neuronto search is never for sale.

Is this your server? Get a message the day it stops answering or its tools change: monitoring, 14 days free. Or claim the domain to manage how it is listed.