_ registry / mcp streamable-http · checked 41m ago

case-doha-record

https://www.clearancesearchengine.com

Registry code: c367ee0c3b8cc6e0

api record

Query the decided public DOHA security-clearance record: search cases, fetch one case, find similar cases, and compute statistics and timelines. Everything is descriptive of decided public cases; cite the returned URLs.

endpoint
https://www.clearancesearchengine.com/api/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is case-doha-record live?
Yes — it answered the hub's last check (checked 41m ago). It answered 99% of checks over the last 30 days.
Is case-doha-record free to use?
Yes — the hub reached it with no key and no payment.
What tools does case-doha-record have?
7 tools: similar_cases, get_case, search_cases, get_conduct_recency, get_timelines, get_statistics, get_candor_outcomes.
Is case-doha-record safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
99.2%

90 days 99%· all time 99%

latency
1,005ms

last good check

priced tools
0

of 7 tools

_ answered our checks, 90 days 396 checks · signed record
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
  • live → degraded· timeout after 20000ms
  • degraded → live
_ what it is for
used for
  • search doha security clearance decisions
  • get clearance grant and denial statistics
  • find similar clearance cases
  • get clearance case timelines
takes → gives
text → data, text
tools
7 reads
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

_ what it can do 7 tools
5 open 2 never probed 5 of 7 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • search_cases reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "level": {
          "enum": [
            "hearing",
            "appeal"
          ],
          "type": "string",
          "description": "Decision level"
        },
        "limit": {
          "type": "integer",
          "description": "Max results, 1-25 (default 10)"
        },
        "query": {
          "type": "string",
          "description": "Full-text search, e.g. \"gambling debts sports betting\""
        },
        "outcome": {
          "enum": [
            "granted",
            "denied"
          ],
          "type": "string",
          "description": "Final outcome filter"
        },
        "year_to": {
          "type": "integer",
          "description": "Latest decision year"
        },
        "guideline": {
          "type": "string",
          "description": "Single guideline letter A-M (e.g. F = financial, B = foreign influence)"
        },
        "year_from": {
          "type": "integer",
          "description": "Earliest decision year, e.g. 2020"
        }
      }
    }
    arguments 41 lines
  • get_conduct_recency reads open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "guideline": {
          "type": "string",
          "description": "Optional single concern letter to scope to: H drugs, G alcohol, J criminal, D sexual behavior, K protected information, M IT misuse"
        }
      }
    }
    arguments 9 lines
  • get_timelines reads open 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "year": {
          "type": "integer",
          "description": "Optional decision year to scope to"
        }
      }
    }
    arguments 9 lines
  • get_statistics reads open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {
        "by": {
          "enum": [
            "year",
            "guideline"
          ],
          "type": "string",
          "description": "Grouping (default year)"
        },
        "year_to": {
          "type": "integer"
        },
        "guideline": {
          "type": "string",
          "description": "Optional single guideline letter A-M to scope to"
        },
        "year_from": {
          "type": "integer"
        }
      }
    }
    arguments 23 lines
  • get_candor_outcomes reads open 14h ago

    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.

    mcp-tool

    {
      "type": "object",
      "properties": {}
    }
    arguments 4 lines
  • similar_cases reads unknown 7h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "case_id"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "description": "Max results, 1-10 (default 5)"
        },
        "case_id": {
          "type": "integer",
          "description": "The numeric case id"
        }
      }
    }
    arguments 16 lines
  • get_case reads unknown 11h ago

    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.

    mcp-tool

    {
      "type": "object",
      "required": [
        "case_id"
      ],
      "properties": {
        "case_id": {
          "type": "integer",
          "description": "The numeric case id from search_cases"
        }
      }
    }
    arguments 12 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id c367ee0c3b8cc6e0.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/c367ee0c3b8cc6e0/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/c367ee0c3b8cc6e0/badge.svg)](https://brick.blue/agent/c367ee0c3b8cc6e0?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
100%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.