
Checker Mcp
com.oksigeniaPublished by oksigenia.comv0.1.1Updated Oct 24, 2026
Domain security & privacy checker as an MCP server. 17 live checks, 0-100 score, local-first.
Overview
Lets an assistant scan a domain and return a scored security and privacy report covering TLS, email authentication, DNS, and web headers.
- What you can do
- Exposes three tools: check_domain scans a domain or URL and returns a scored report from 17 live checks across ssl, email, dns, and web categories, weighted to a 0-100 score; list_checks lists every check grouped by category with why each matters; explain_check explains one check by id and how to remediate a failure. Reports render in English or Spanish and can be returned as a report or JSON.
- When to use it
- Useful when you want an assistant to audit a domain's security posture, review certificate, SPF, DMARC, DKIM, DNSSEC, CAA, or HTTP security header configuration, or explain what a specific check means and how to fix a failure.
- Requirements
- Runs locally over stdio as an npm package, typically via npx, so Node.js is needed; Docker is an alternative. No accounts, API keys, or environment variables are required, though OKSIGENIA_LANG can set the default language. Network access is needed for the checks themselves.
Installation
In SourceWeft
- Open Checker Mcp in the dashboard and add it to a workspace.
- Enable the server for the chats that should use its tools.
Desktop only via STDIO. STDIO servers start a local process, so they need the SourceWeft desktop host.
Other MCP clients
Follow the launch instructions in the repository.
README
@oksigenia/checker-mcp
A domain security and privacy checker exposed as an MCP server. It runs entirely on your machine, makes no telemetry calls, and resolves DNS through Cloudflare DoH instead of Google.
Ask any MCP client to scan a domain and get back a scored report covering the certificate, email authentication, DNS and infrastructure, and web security headers, with a plain remediation for anything that fails.
Why it's different
- Local-first. The server runs over stdio and does its own DNS-over-HTTPS, HTTP, RDAP and TLS lookups. The only network traffic is the checks themselves.
- Zero telemetry. No analytics, no phone-home, no third-party scoring service in the loop.
- Privacy by default. DNS goes to Cloudflare DoH rather than Google, and the reputation check uses Cloudflare's malware/phishing resolver.
- Free software. Licensed GPL-3.0-or-later. Read it, run it, change it, self-host it.
Tools
The server exposes three tools.
check_domain
Scan a domain or URL and return a scored report from real live checks.
list_checks
List every check grouped by category, with the reason each one matters.
explain_check
Explain a single check by id, why it matters, and how to remediate a failure.
Checks
Seventeen checks across four categories, weighted to a 0-100 score.
Run list_checks for the full descriptions, or explain_check for one at a time.
Install
Run it straight from npm with npx:
Register it with Claude Code:
Or add it to any MCP client config (works in Claude Desktop, Claude Code, or any MCP client):
Then ask: "Check the security of example.com" or "Explain the dmarc check."
Run with Docker
Build and run it as a container. It speaks MCP over stdio, so run it attached to your client's stdin/stdout (-i), not on a port.
Languages
Reports render in Spanish and English. Set the default with OKSIGENIA_LANG (es or en), or pass lang on any tool call. It defaults to English.
Privacy
The only thing that leaves your machine is the domain name you scan, sent to:
- Cloudflare DoH (
cloudflare-dns.com) and Cloudflare's security resolver, for DNS and reputation - public RDAP (
rdap.org), for registration and WHOIS-privacy data - the HSTS preload API, for preload status
- the target site itself, over HTTPS, to read its certificate and security headers
There is no telemetry, no analytics, and no third-party scoring service. Nothing about your queries is stored or transmitted anywhere else.
Develop
Dev watch: npm run dev.
src/engine.ts— the network engine. Language-agnostic: returns i18n keys, not text. Every check is individually resilient andrunChecksnever throws.src/i18n.ts— es/en dictionaries andt().src/index.ts— the MCP server: renders engine keys into the requested language and exposes the three tools.
See CONTRIBUTING.md for the PR flow.
License
GPL-3.0-or-later © Oksigenia SL
Source: README.md at commit 2b065af
Tools
0Version history
1- v0.1.1LatestSep 16, 2026
Score
50% of the applicable checks met
How complete this listing is, computed from the registry entry, the endpoint and public sources. Not a rating of the server and not a statement that it is safe or working today: reachability is a dated check, and no installs or reviews go into the score.
- Reached in the last 30 days25 pts
Keep the endpoint answering the MCP handshake; SourceWeft probes it every 30 days.
- Auth declared10 pts
Declare the credential headers in the registry entry, or keep the endpoint answering the probe so its auth can be classified.
- Tools listed15 pts
Answer tools/list without a credential, or ship a package that starts in a sandbox without one.
- DescriptionRequired15 pts
- Logo10 pts
- Documentation15 pts
- License10 pts