Config is the same across clients — only the file and path differ.
{
"mcpServers": {
"dechonet": {
"args": [
"-y",
"dechonet-mcp"
],
"command": "npx"
}
}
}Are you the author?
Add this badge to your README to show your security score and help users find safe servers.
Domain security reconnaissance tools for AI agents via Model Context Protocol.
Run this in your terminal to verify the server starts. Then let us know if it worked — your result helps other developers.
npx -y 'dechonet-mcp' 2>&1 | head -1 && echo "✓ Server started successfully"
After testing, let us know if it worked:
Five weighted categories — click any category to see the underlying evidence.
No known CVEs.
Checked dechonet-mcp against OSV.dev.
Be the first to review
Have you used this server?
Share your experience — it helps other developers decide.
Sign in to write a review.
Others in security
An evil MCP server used for redteam testing
AI-powered reverse engineering assistant that bridges IDA Pro with language models through MCP.
Proof primitive for AI agents on MultiversX. Anchor file hashes on-chain as verifiable proofs.
mcpki-server is the backend infrastructure for https://www.mcpki.org, enabling secure public key management and autonomous certificate handling for large language models (LLMs).
MCP Security Weekly
Get CVE alerts and security updates for io.github.node-man/dechonet-mcp and similar servers.
Start a conversation
Ask a question, share a tip, or report an issue.
Sign in to join the discussion.
Domain security reconnaissance tools for AI agents via Model Context Protocol.
13 security tools — DNS, SSL, HTTP headers, email auth, port scan, propagation, reverse DNS, ASN/BGP, RDAP/WHOIS, subnet calc, and comprehensive security scan — callable from Claude Desktop and any MCP-compatible AI agent.
Add to your claude_desktop_config.json:
{
"mcpServers": {
"dechonet": {
"command": "npx",
"args": ["-y", "dechonet-mcp"]
}
}
}
Or if installed locally:
{
"mcpServers": {
"dechonet": {
"command": "node",
"args": ["/path/to/dechonet/mcp/build/index.js"]
}
}
}
Config file location:
~/Library/Application Support/Claude/claude_desktop_config.json%APPDATA%\Claude\claude_desktop_config.jsonRestart Claude Desktop. You'll see the DechoNet tools icon in the input area.
# Via npx (no install needed)
npx dechonet-mcp
# Or install globally
npm install -g dechonet-mcp
| Tool | Description |
|---|---|
security_scan | Comprehensive scan — 9 checks in parallel, 0-100 Health Score, A-F grade |
dns_lookup | DNS records + DNSSEC + SPF/DMARC validation |
ssl_check | SSL/TLS certificate, chain, TLS version, A-F grade |
http_security | HTTP redirect trace + 10 security headers audit, A-F grade |
email_auth | SPF, DMARC, DKIM, BIMI, MTA-STS, DANE + blacklist check |
port_scan | Open TCP ports with service identification |
dns_propagation | DNS propagation across 8+ global resolvers |
reverse_dns | PTR record + FCrDNS verification |
asn_lookup | ASN/BGP network identification + abuse contact |
whois_lookup | RDAP/WHOIS domain registration data |
ip_info | Public IP, ISP, ASN, proxy detection |
email_header_analysis | Email delivery route tracing + auth results |
subnet_calc | CIDR subnet calculator (offline) |
Once connected, try asking Claude:
For remote/HTTP-based MCP connections:
cd mcp
npm run start:sse
# Server runs on http://localhost:3100
# SSE endpoint: http://localhost:3100/sse
cd mcp
npm install
npm run build # TypeScript → build/
npm run dev # Run with tsx (stdio)
npm run start:sse # Run SSE server
The MCP server calls DechoNet's public API (https://dechonet.com/api/util/*) and returns structured results with:
All data comes from public sources (DNS, HTTP headers, SSL certificates, RDAP). No active exploitation.
| Variable | Default | Description |
|---|---|---|
DECHONET_URL | https://dechonet.com | API base URL |
DECHONET_LOCALE | en | Response language (en or ko) |
PORT | 3100 | SSE server port |