Remote MCP server to run your Atako AI agents: chat, projects, files, integrations and channels.
- Passed: Handshake
- Passed: Tools listed
- Passed: Updated recently
Median latency 132 ms · Last checked
Explore
Evidence for your next connection.
Independent measurements of remote MCP servers. Every observation has a timestamp.
Read-only probesMCP server · Code & DevOps
Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record.
0 failed · 8 not measured
Median of successful probes over 7 days
Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.
Tool definitions returned by this server
Independent monitoring
Responded
The server completed its last measured handshake. This is an observation, not a guarantee.
Last checked| Test area | Passed | Failed | Unmeasured |
|---|---|---|---|
ConnectionCan a client connect and discover tools? | 5 | 0 | 0 |
Reliability & speedDoes it respond consistently and quickly? | 0 | 0 | 4 |
Access & authenticationWhat is required to use this server? | 1 | 0 | 2 |
Tool qualityAre the tool definitions usable by an agent? | 4 | 0 | 0 |
Publisher identityCan the publisher be traced to its source? | 4 | 0 | 2 |
Unmeasured means there is not enough evidence to decide. How these checks work
Start using io.github.klmlfl/case-doha-record
Choose your client, copy the configuration, then enable the server in your client’s MCP settings.
Run this command in your terminal, then restart Claude Code.
Claude Code
claude mcp add --transport http io-github-klmlfl-case-doha-record https://www.clearancesearchengine.com/api/mcpCapabilities
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.
DiscoveredFetch 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.
DiscoveredHow 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.
DiscoveredGrant/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.
DiscoveredMeasured 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.
DiscoveredSearch 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.
DiscoveredThe 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.
DiscoveredRecent measurements
| Checked | Result | Response | Tools |
|---|---|---|---|
| Connected | 553 ms | 7 |