Home / MCP registry index / io.github.klmlfl/case-doha-record

io.github.klmlfl/case-doha-record

io.github.klmlfl/case-doha-record in the official MCP registry. Endpoint https://www.clearancesearchengine.com/api/mcp. Source: github.com/klmlfl/dohasearch.

The registry describes it as: Search 30,000+ decided U.S. DOHA security-clearance decisions, cited to the public record.

We read its 7 tools on 2026-10-29. Nothing in them matched our tool-poisoning rules. It also sets server instructions, text a client puts in front of the model on connect; those were read too.

A clean read means these rules found nothing, not that the server is harmless. A server can change its tools at any time, which is why the index reads it again every week.

Connect it

The endpoint answers MCP over HTTP; that is how we read it. Add it to your client:

Claude Code
claude mcp add --transport http case-doha-record https://www.clearancesearchengine.com/api/mcp
Cursor: ~/.cursor/mcp.json
{
  "mcpServers": {
    "case-doha-record": {
      "url": "https://www.clearancesearchengine.com/api/mcp"
    }
  }
}
VS Code
code --add-mcp '{"name":"case-doha-record","type":"http","url":"https://www.clearancesearchengine.com/api/mcp"}'

Some servers ask you to sign in the first time a client connects, or want a key from the people who run them; the server's own docs say which. The free lazaretto-guard plugin reads a server's tools the moment Claude Code adds it and asks you if one of our rules matches.

Tools it advertises

search_cases get_case similar_cases get_statistics get_timelines get_conduct_recency get_candor_outcomes

Run this server? Show the check in your README

The badge reflects the latest weekly read: MCP tool check badge

Markdown
[![MCP tool check](https://lazaretto.dev/mcp-registry/io-github-klmlfl-case-doha-record/badge.svg)](https://lazaretto.dev/mcp-registry/io-github-klmlfl-case-doha-record)

How this was checked

Lazaretto connects to the endpoint the way any MCP client does, asks the server to introduce itself and list its tools, and reads every name, description, parameter schema and server instruction for tool poisoning: hidden directive blocks, orders to read local secrets, parameters built to carry secrets or the conversation out, orders that redirect another server's tools, and invisible characters. It never calls a tool. What we found across the registry.

To run the same check every time Claude Code adds a server, install the free lazaretto-guard plugin. Browse every server in the index.

Related

Security MCP servers

ScorpTech x402 API
com.it.scorptech/x402
200 tools, nothing matched
2026-10-26
com.freedailypro/tools
com.freedailypro/tools
178 tools, nothing matched
2026-10-27
BlackVeil DNS & Email Security Scanner
com.blackveilsecurity/dns
81 tools, nothing matched
2026-10-22
com.validoria/validoria-mcp
com.validoria/validoria-mcp
78 tools, nothing matched
2026-10-27
Security Recipes
io.github.stevologic/security-recipes
75 tools, nothing matched
2026-10-21
ContrastAPI
com.contrastcyber/api
55 tools, nothing matched
2026-10-27