Checker MCP server
{
"mcpServers": {
"oksigenia-checker": {
"command": "npx",
"args": [
"-y",
"@oksigenia/checker-mcp@latest"
]
}
}
}{
"mcpServers": {
"oksigenia-checker": {
"command": "npx",
"args": [
"-y",
"@oksigenia/checker-mcp@latest"
]
}
}
}{
"mcpServers": {
"oksigenia-checker": {
"command": "npx",
"args": [
"-y",
"@oksigenia/checker-mcp@latest"
]
}
}
}{
"servers": {
"oksigenia-checker": {
"command": "npx",
"args": [
"-y",
"@oksigenia/checker-mcp@latest"
]
}
}
}{
"mcpServers": {
"oksigenia-checker": {
"command": "npx",
"args": [
"-y",
"@oksigenia/checker-mcp@latest"
]
}
}
}file .mcp.json (in your project root)file claude_desktop_config.jsonfile ~/.cursor/mcp.jsonfile .vscode/mcp.jsonfile ~/.codeium/windsurf/mcp_config.jsoninstall npx -y @oksigenia/checker-mcpversion 0.1.1
What it does
A domain security and privacy checker that runs locally and exposes 17 security checks across SSL, email authentication, DNS, and web security categories. It scores domains 0-100 and provides remediation guidance, with no telemetry and DNS resolution through Cloudflare DoH.
- Scan a domain to get a scored security report covering certificate validity, email authentication records, DNS configuration, and HTTP security headers.
- Look up individual security checks by category to understand what matters for domain security and how to remediate failures.
- Verify a domain's compliance with standards like DMARC, SPF, DNSSEC, HSTS, and CAA records before deploying or migrating.
Tools this server exposes
| Tool | Does |
|---|---|
| check_domain | Scan a domain or URL and return a scored report from 17 live security checks, with optional filtering by category and language support. |
| list_checks | List all 17 checks grouped by category with explanations of why each one matters. |
| explain_check | Get a detailed explanation of a single check by ID, including why it matters and how to remediate failures. |
Before you enable it
An MCP server runs with whatever access you give it. Start with a development account rather than production, and check which tools the server exposes before you let an agent call them unattended.