io.github.klmlfl/case-doha-record
REMOTE · WWW.CLEARANCESEARCHENGINE.COM · SCANNED SEP 21
Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record.
Available components
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. How we score → Why this is hard to score →
Endpoint Security80
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC check failed: this domain isn't protected by DNSSEC. See how to fix → View diagnostics → Fail
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability79
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 684 tokens (~97/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage96
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 88% of tool parameters carry a description.Partial
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 8 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
- Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
How do I install the io.github.klmlfl/case-doha-record MCP server?
io.github.klmlfl/case-doha-record is a hosted endpoint at https://www.clearancesearchengine.com/api/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
remote · www.clearancesearchengine.com
claude mcp add --transport http klmlfl-case-doha-record 'https://www.clearancesearchengine.com/api/mcp'
{
"mcpServers": {
"klmlfl-case-doha-record": {
"url": "https://www.clearancesearchengine.com/api/mcp"
}
}
} {
"servers": {
"klmlfl-case-doha-record": {
"type": "http",
"url": "https://www.clearancesearchengine.com/api/mcp"
}
}
} [mcp_servers.klmlfl-case-doha-record] url = "https://www.clearancesearchengine.com/api/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"klmlfl-case-doha-record": {
"type": "remote",
"url": "https://www.clearancesearchengine.com/api/mcp",
"enabled": true
}
}
} openclaw mcp add klmlfl-case-doha-record --url 'https://www.clearancesearchengine.com/api/mcp' --transport streamable-http
mcp_servers:
klmlfl-case-doha-record:
url: "https://www.clearancesearchengine.com/api/mcp" {
"McpServers": {
"klmlfl-case-doha-record": {
"Transport": "http",
"Url": "https://www.clearancesearchengine.com/api/mcp"
}
}
} assistant mcp add klmlfl-case-doha-record -t streamable-http -u 'https://www.clearancesearchengine.com/api/mcp'
{
"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.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 25 Aug 26 0
- Stability: 0.97 → pass security
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 26 Jul 26 0
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Probed https://www.clearancesearchengine.com/api/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=www.clearancesearchengine.com | CN=YR2,O=Let's Encrypt,C=US | 6 Sept 2026 | 5 Dec 2026 | RSA 2048 | SHA256-RSA | 62a6cf319a51ff285c82bafcb55e74352a6 |
| SANs: www.clearancesearchengine.com | ||||||
| CN=YR2,O=Let's Encrypt,C=US (CA) | CN=Root YR,O=ISRG,C=US | 3 Sept 2025 | 2 Sept 2028 | RSA 2048 | SHA256-RSA | 4ebd24947e24d394802d84a52fd5b319 |
| CN=Root YR,O=ISRG,C=US (CA) | CN=ISRG Root X1,O=Internet Security Research Group,C=US | 13 May 2026 | 2 Sept 2032 | RSA 4096 | SHA256-RSA | f24b6d17f9d9ad7cb1c9fea78782699f |
Background: What to check on a remote MCP endpoint →
DNSSEC insecure
Validation of www.clearancesearchengine.com. — Not signed
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| clearancesearchengine.com. | absent | Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation |
Authentication No authorisation required
The endpoint answered without asking for a token. Anyone who knows the URL can reach it.
| Result | No authorisation required |
|---|---|
| HTTP status | 200 |
| Header | Value |
|---|---|
| strict-transport-security | max-age=63072000 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://www.clearancesearchengine.com/api/mcp | Verified | 200 | |
| http (plaintext) | http://www.clearancesearchengine.com/api/mcp | HTTPS enforced | 308 | https://www.clearancesearchengine.com/api/mcp |
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
get_candor_outcomes ~89
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.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
get_case ~66
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | The numeric case id from search_cases |
No output schema declared.
No examples provided.
get_conduct_recency ~111
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.
| Name | Type | Req | Description |
|---|---|---|---|
| guideline | string | – | Optional single concern letter to scope to: H drugs, G alcohol, J criminal, D sexual behavior, K protected information, M IT misuse |
No output schema declared.
No examples provided.
get_statistics ~86
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.
| Name | Type | Req | Description |
|---|---|---|---|
| by | string | – | Grouping (default year) |
| guideline | string | – | Optional single guideline letter A-M to scope to |
| year_from | integer | – | – |
| year_to | integer | – | – |
No output schema declared.
No examples provided.
get_timelines ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| year | integer | – | Optional decision year to scope to |
No output schema declared.
No examples provided.
search_cases ~162
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.
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
similar_cases ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| case_id | integer | yes | The numeric case id |
| limit | integer | – | Max results, 1-10 (default 5) |
No output schema declared.
No examples provided.
What is the io.github.klmlfl/case-doha-record MCP server?
io.github.klmlfl/case-doha-record is an MCP server listed in the public MCP registry as io.github.klmlfl/case-doha-record. Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record. This page covers its hosted endpoint (https://www.clearancesearchengine.com/api/mcp).
Is the io.github.klmlfl/case-doha-record MCP server safe to use?
io.github.klmlfl/case-doha-record scores 86 out of 100 on VerifyMCP. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.klmlfl/case-doha-record MCP server expose?
io.github.klmlfl/case-doha-record exposes 7 tools: search_cases, get_case, similar_cases, get_statistics, get_timelines, and 2 more. Their descriptions and schemas cost roughly 640 tokens of context every time the server is loaded.
Does the io.github.klmlfl/case-doha-record MCP server require authentication?
No. We connected to io.github.klmlfl/case-doha-record without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the io.github.klmlfl/case-doha-record MCP server still maintained?
io.github.klmlfl/case-doha-record is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.