# io.github.klmlfl/case-doha-record (remote · www.clearancesearchengine.com)

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

- Trust score: 74/100 (medium)
- Change this week: +5
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `www.clearancesearchengine.com`: 74/100 (this document), [markdown](https://verifymcp.io/servers/klmlfl-case-doha-record/api-mcp.md), [page](https://verifymcp.io/servers/klmlfl-case-doha-record/api-mcp)

## Channel facts

- Endpoint: `https://www.clearancesearchengine.com/api/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 80/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 77/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 684 tokens (~97/item across 7 items; 7 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 96/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 88% of tool parameters carry a description.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.klmlfl-case-doha-record]
url = "https://www.clearancesearchengine.com/api/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "klmlfl-case-doha-record": {
      "type": "remote",
      "url": "https://www.clearancesearchengine.com/api/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add klmlfl-case-doha-record --url https://www.clearancesearchengine.com/api/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  klmlfl-case-doha-record:
    url: "https://www.clearancesearchengine.com/api/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 73, +4)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, −2)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 71, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-28 (score 70, +1)

No change was recorded against any check on this day. Stability & Change Management went from 3 to 7. That category is still filling its 30-day observation window: 1 days of observed history at the previous scan, 2 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 69, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 69)

First indexed and scored.

## MCP tools (7)

### `search_cases` (~162 tokens)

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.

Input parameters:

- `guideline` (string): Single guideline letter A-M (e.g. F = financial, B = foreign influence)
- `level` (string): Decision level
- `limit` (integer): Max results, 1-25 (default 10)
- `outcome` (string): Final outcome filter
- `query` (string): Full-text search, e.g. "gambling debts sports betting"
- `year_from` (integer): Earliest decision year, e.g. 2020
- `year_to` (integer): Latest decision year

### `get_case` (~66 tokens)

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.

Input parameters:

- `case_id` (integer, required): The numeric case id from search_cases

### `similar_cases` (~70 tokens)

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.

Input parameters:

- `case_id` (integer, required): The numeric case id
- `limit` (integer): Max results, 1-10 (default 5)

### `get_statistics` (~86 tokens)

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.

Input parameters:

- `by` (string): Grouping (default year)
- `guideline` (string): Optional single guideline letter A-M to scope to
- `year_from` (integer)
- `year_to` (integer)

### `get_timelines` (~56 tokens)

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.

Input parameters:

- `year` (integer): Optional decision year to scope to

### `get_conduct_recency` (~111 tokens)

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.

Input parameters:

- `guideline` (string): Optional single concern letter to scope to: H drugs, G alcohol, J criminal, D sexual behavior, K protected information, M IT misuse

### `get_candor_outcomes` (~89 tokens)

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.

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/klmlfl-case-doha-record/api-mcp#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 73
- 2026-08-01: 73
- 2026-07-31: 73
- 2026-07-30: 69
- 2026-07-29: 71
- 2026-07-28: 70
- 2026-07-27: 69
- 2026-07-26: 69

## Links

- Remote endpoint: https://www.clearancesearchengine.com/api/mcp
- Repository: https://github.com/klmlfl/dohasearch
- Website: https://www.clearancesearchengine.com/developers
- Changelog RSS feed: https://verifymcp.io/servers/klmlfl-case-doha-record/api-mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/klmlfl-case-doha-record/api-mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/klmlfl-case-doha-record/api-mcp