Connect

8 clients · secrets stay placeholders

JSON (mcpServers)Claude CodeCodexOpenCodeCursorVS CodeGemini CLIGoose

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

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

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

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

{
  "mcpServers": {
    "case-doha-record": {
      "type": "http",
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  },
  "deeplink": "cursor://anysphere.cursor-deeplink/mcp/install?name=case-doha-record&config=eyJ0eXBlIjoiaHR0cCIsInVybCI6Imh0dHBzOi8vd3d3LmNsZWFyYW5jZXNlYXJjaGVuZ2luZS5jb20vYXBpL21jcCJ9"
}

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

{
  "mcpServers": {
    "case-doha-record": {
      "httpUrl": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}

extensions:
  "case-doha-record":
    enabled: true
    name: "case-doha-record"
    type: streamable_http
    uri: "https://www.clearancesearchengine.com/api/mcp"
    timeout: 300

Quality 85 / 100good

protocol75 · weight 25

warn
protocol.modernnewest supported version is 2025-06-18; 2026-07-28 not supported, older versions are deprecated until 2027-07-28
n/a
protocol.statelessonly applies to 2026-07-28 servers
pass
protocol.transportstreamable HTTP
n/a
protocol.list_ttlonly applies to 2026-07-28 servers

authorizationn/a · weight 15

n/a
auth.prm, auth.as_metadata, auth.cimdno remote uses OAuth
n/a
auth.secret_in_urlno templated URL

tool hygiene86 · weight 30

pass
tools.descriptionsevery tool has a description
pass
tools.description_lengthdescriptions are concise
pass
tools.schemasevery tool has an object input schema
pass
tools.annotations7 of 7 tools declare readOnlyHint or destructiveHint
fail
tools.directory_hintsno tool declares all four of readOnlyHint, destructiveHint, idempotentHint and openWorldHint; missing: search_cases (idempotentHint); get_timelines (idempotentHint); get_case (idempotentHint); …
pass
tools.token_costabout 954 tokens to load every tool
pass
tools.api_dumptools are not a one-to-one API dump

stability100 · weight 15

pass
stability.changesno tool changes in 30 days
pass
stability.rug_pullno tool changed its meaning under the same name

dependenciesn/a · weight 15

n/a
deps.known_vulns, deps.mcp_sdk_version, deps.resolvableno npm or PyPI package

7 tools, about 954 tokens to load them all · tool set fbe66f0f4a3d · checked 2026-10-19 10:20 UTC

Tool changes

No tool definition changes recorded. A server's first observation is its baseline; later probes record what changes.

Checks run on what our credential-free, read-only probes observe; tools are never called and no code audit is performed. How it is computed.

Trust 90 / 100

provenance90

liveness100

freshness65

hygiene100

+repository +namespace-matches-repo +website +reachable +uptime-100% ~updated-93d-ago

Derived from observable signals (official registry feed and our own credential-free probes); no code audit performed. How it is computed.

Endpoints

remote	auth	reachable	uptime 30d	p50	protocol	last ok
`https://www.clearancesearchengine.com/api/mcp` streamable-http	none	yes	100%	285 ms	2025-06-18	2026-10-19

Tools (7)

`get_candor_outcomes`read-only	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.
`get_case`read-only	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.
`get_conduct_recency`read-only	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.
`get_statistics`read-only	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.
`get_timelines`read-only	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.
`search_cases`read-only	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.
`similar_cases`read-only	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.

Schemas: list_tools.

Similar MCP servers

Official server.json

{
  "name": "io.github.klmlfl/case-doha-record",
  "$schema": "https://static.modelcontextprotocol.io/schemas/2025-09-29/server.schema.json",
  "remotes": [
    {
      "url": "https://www.clearancesearchengine.com/api/mcp",
      "type": "streamable-http"
    }
  ],
  "version": "1.0.0",
  "repository": {
    "url": "https://github.com/klmlfl/dohasearch",
    "source": "github"
  },
  "websiteUrl": "https://www.clearancesearchengine.com/developers",
  "description": "Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record."
}