io.github.Bishop81/domainintel-mcp
NPM · @DOMAININTEL/MCP · SCANNED SEP 21
Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 58 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability80
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 477 tokens (~68/item across 7 items; 7 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
- No destabilizing schema changes in the last 30 days.Pass
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 7 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the io.github.Bishop81/domainintel-mcp server?
io.github.Bishop81/domainintel-mcp runs locally as an npm package, launched with npx -y @domainintel/mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @domainintel/mcp
claude mcp add bishop81-domainintel-mcp -- npx -y @domainintel/mcp
{
"mcpServers": {
"bishop81-domainintel-mcp": {
"command": "npx",
"args": [
"-y",
"@domainintel/mcp"
]
}
}
} {
"servers": {
"bishop81-domainintel-mcp": {
"command": "npx",
"args": [
"-y",
"@domainintel/mcp"
]
}
}
} codex mcp add bishop81-domainintel-mcp -- npx -y @domainintel/mcp
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"bishop81-domainintel-mcp": {
"type": "local",
"command": [
"npx",
"-y",
"@domainintel/mcp"
],
"enabled": true
}
}
} openclaw mcp add bishop81-domainintel-mcp --command npx --arg -y --arg @domainintel/mcp
mcp_servers:
bishop81-domainintel-mcp:
command: "npx"
args: ["-y", "@domainintel/mcp"] {
"McpServers": {
"bishop81-domainintel-mcp": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@domainintel/mcp"
]
}
}
} assistant mcp add bishop81-domainintel-mcp -t stdio -c npx -a -y @domainintel/mcp
{
"mcpServers": {
"bishop81-domainintel-mcp": {
"command": "npx",
"args": [
"-y",
"@domainintel/mcp"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 21 Sept 26 0
- Stability: 0.97 → pass security
- 20 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 17 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
- 16 Sept 26 0
- Security disclosure: fail → unverified ▼ functional
- 15 Sept 26 −2
- Stability: pass → 0.80 functional
- 14 Sept 26 0
- Stability: 0.97 → pass security
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 10 Sept 26 +1
- Security disclosure: unverified → fail ▼ functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 21 Sept 2026 · Analysed npm/@domainintel/mcp@1.0.2
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
dns_records DNS records ~71
Resolves A, AAAA, MX, TXT, NS and CNAME records, plus CAA records, SPF/DMARC presence and common DNS misconfiguration warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
domain_reputation Domain reputation ~62
Checks the domain/IP against DNS blocklists (DNSBL, Spamhaus) and returns a reputation score and any listings.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
full_domain_report Full domain report ~76
Runs every analyzer (WHOIS, DNS, SSL, security headers, reputation, subdomains) in parallel and returns a combined report with an overall security score and A+ to F rating.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
security_headers HTTP security headers ~77
Fetches HTTP response headers and scores security headers (HSTS, CSP, X-Frame-Options, X-Content-Type-Options, Referrer-Policy, Permissions-Policy) with recommendations.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
ssl_certificate SSL/TLS certificate ~62
Inspects the live TLS certificate: validity, issuer, subject, expiration, days remaining, protocol/cipher and certificate warnings.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
subdomain_discovery Subdomain discovery ~63
Discovers subdomains via Certificate Transparency logs (crt.sh) and common-prefix probing, with DNS resolution status for each.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
whois_lookup WHOIS lookup ~66
Registration data for a domain: registrar, creation/expiry/updated dates, registrant country, privacy/redaction status, and name servers.
| Name | Type | Req | Description |
|---|---|---|---|
| domain | string | yes | Domain name to analyze, e.g. "example.com" (protocol, www. and paths are stripped automatically) |
No output schema declared.
No examples provided.
What is the io.github.Bishop81/domainintel-mcp server?
io.github.Bishop81/domainintel-mcp is listed in the public MCP registry as io.github.Bishop81/domainintel-mcp. Domain intelligence for agents: WHOIS, DNS, SSL/TLS, security headers, reputation, subdomains. This page covers its npm package (@domainintel/mcp).
Is the io.github.Bishop81/domainintel-mcp server safe to use?
io.github.Bishop81/domainintel-mcp scores 85 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 21 September 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.Bishop81/domainintel-mcp server expose?
io.github.Bishop81/domainintel-mcp exposes 7 tools: whois_lookup, dns_records, ssl_certificate, security_headers, domain_reputation, and 2 more. Their descriptions and schemas cost roughly 477 tokens of context every time the server is loaded.
Is the io.github.Bishop81/domainintel-mcp server still maintained?
io.github.Bishop81/domainintel-mcp is still listed as active in the MCP registry. We last reached this channel on 21 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.Bishop81/domainintel-mcp server under?
io.github.Bishop81/domainintel-mcp declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.