Skip to content

io.github.klmlfl/case-doha-record

by klmlfl · remote · no sign-in to list tools · v1.0.0 · published by GitHub user klmlfl

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

Changes · 1
CompareRegistry entry

7 tools: 1 change things and 6 only read.

Scanned Oct 21, 2026

No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.

claude mcp add --transport http case-doha-record https://www.clearancesearchengine.com/api/mcp

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

7 tools

Changes things 1Claude Code: ask
  • similar_casesThe most similar decided cases to a given case, ranked by how alike the ALLEGATIONS read (never by outcome).No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
Only reads 6Claude Code: allow
  • 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…No findings

    Why it is in this group

    • The name "get_candor_outcomes" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • 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.No findings

    Why it is in this group

    • The name "get_case" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • 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 con…No findings

    Why it is in this group

    • The name "get_conduct_recency" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_statisticsGrant/denial statistics over decided hearing-level DOHA cases, grouped by year or by guideline, always with sample sizes.No findings

    Why it is in this group

    • The name "get_statistics" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • get_timelinesMeasured DOHA timelines: median days from Statement of Reasons to hearing and to decision, from dates stated in the decisions themselves.No findings

    Why it is in this group

    • The name "get_timelines" says "get": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false
  • search_casesSearch 30,000+ decided public DOHA security-clearance decisions (1996 to present).No findings

    Why it is in this group

    • The name "search_cases" says "search": a word for reading.
    Description, as the server wrote it
    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.

    Annotations the server declares

    • readOnlyHint: true
    • destructiveHint: false
    • openWorldHint: false

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 1.0.0. Values in angle brackets are yours to fill in.

claude mcp add --transport http case-doha-record https://www.clearancesearchengine.com/api/mcp

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__case-doha-record__search_cases",
      "mcp__case-doha-record__get_case",
      "mcp__case-doha-record__get_statistics",
      "mcp__case-doha-record__get_timelines",
      "mcp__case-doha-record__get_conduct_recency",
      "mcp__case-doha-record__get_candor_outcomes"
    ],
    "ask": [
      "mcp__case-doha-record__similar_cases"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as case-doha-record. Review it before you use it.