Case Doha Record

io.github.klmlflPublished by GitHub account klmlflv1.0.0Updated Oct 24, 2026

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

VerifiedStreamable HTTPWeb executableKnowledge & MemoryData & Analytics

Overview

AI-generated overview

A remote MCP server that lets an assistant search and analyze 30,000+ decided public DOHA security-clearance decisions, with citable URLs and statistics.

What you can do
Search decided DOHA cases by full-text query and filters, with outcome, date, guidelines and a citable URL per case. Retrieve a single case in full, including allegations, findings, outcome, judge, representation and appeal history. Find similar cases ranked by how alike the allegations read. Get grant/denial statistics by year or guideline, with sample sizes. Get measured timelines from Statement of Reasons to hearing and decision. Get conduct-recency figures and candor-outcome comparisons.
When to use it
Useful when researching U.S. security-clearance adjudication: finding precedent-like decisions, checking guideline outcomes, or comparing statistics and timelines across the decided record.
Requirements
A remote streamable HTTP endpoint; no package, environment variables or headers are declared. No authentication is declared.
Before you install
Results describe real people's public adjudicative decisions; treat them as sensitive and cite rather than republish. Statistics and comparisons are drawn from the decided record and should be read with their sample sizes.

Installation

In SourceWeft

  1. Open Case Doha Record in the dashboard and add it to a workspace.
  2. Enable the server for the chats that should use its tools.

Web executable via Streamable HTTP. Remote servers run from the web runtime once configured in a workspace.

Use with an agent

Paste this prompt into Claude Code, Codex, Cursor or another agent — or into SourceWeft chat. The agent reads this server's install guide, shows you its publisher, endpoint and sign-in, and adds it to your client once you agree. Keys never go into a command.

Read https://sourceweft.com/mcp/io.github.klmlfl%2Fcase-doha-record/install.md and connect the MCP server it describes to my client. Before changing any config, show me its publisher, endpoint and sign-in method and wait for my OK. Never put an API key in a command or in a file I would commit; ask me where it should come from.

Read the install guide the agent follows

Other MCP clients

Add this to your client's mcpServers config.

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

README

This repository has no README.

Tools

7

search_cases

Search 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.

Parameterslevellimitqueryoutcomeyear_toguidelineyear_from

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. Use case_id from search_cases.

Parameterscase_idrequired

similar_cases

The 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.

Parameterslimitcase_idrequired

get_statistics

Grant/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.

Parametersbyyear_toguidelineyear_from

get_timelines

Measured 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.

Parametersyear

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). Reports median years before favorable vs unfavorable decisions, with counts. Descriptive association, never a prediction.

Parametersguideline

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. Counts and denominators throughout. Descriptive, never a prediction.

Takes no parameters.

Version history

1
  1. v1.0.0LatestSep 16, 2026

Score

75% of the applicable checks met

How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.

  • Reached in the last 30 daysRequired25 pts
  • Auth declaredRequired10 pts
  • Tools listedRequired15 pts
  • DescriptionRequired15 pts
  • Logo10 pts
  • Documentation15 pts

    Declare a GitHub repository with a README, or serve resource_documentation in the OAuth protected-resource metadata.

  • License10 pts

    Declare a license in the repository or the registry entry.