Security & Testing
how.is
Provides domain intelligence and security diagnostics including DNS, WHOIS, TLS, DNSSEC, email authentication, blacklist status, and IP intelligence.
ENDPOINT 1
https://how.is/mcp
MCP server metadata
- Name
- how.is
- Version
- 1.0.0
Domain and IP intelligence, priced per call. Every tool has a free sample input (example.com, 1.1.1.1 or https://example.com) that works with no key. Other inputs need a prepaid key sent as 'Authorization: Bearer <key>' on this connection; without one the tool returns payment terms. Prefer domain_profile when you need several facts about one domain: it is cheaper than the separate calls. Reference: https://how.is/llms.txt
Known tools 16
domain_profileEverything about a domain in one call: DNS, WHOIS, TLS, DNSSEC, email auth, security score, blacklist status, plus IP intelligence for its A record.
Potential side effectsdomain_dnsA, AAAA, MX, NS, TXT and other records for a domain, with resolve timing.
Inferred read-onlydomain_whoisRegistrar, creation and expiry dates, nameservers and status codes for a domain.
Inferred read-onlydomain_ageHow old a domain is: registration date, age in days and years, and whether it was registered in the last 30 days (a common phishing signal).
Inferred read-onlydomain_tlsCertificate validity, issuer, protocol and days until expiry for a domain.
Inferred read-onlydomain_security_scoreA letter grade and point score for a domain security posture, with the scored items behind it.
Inferred read-onlydomain_blacklistWhether the addresses behind a domain appear on spam and abuse blocklists.
Inferred read-onlyip_lookupNetwork owner (ASN), company, geolocation, privacy flags and abuse contact for an IP address.
Inferred read-onlysite_statusLive check of one or more URLs: HTTP status, latency, DNS resolve time, resolved IP, TTL, nameservers, TLS days remaining.
Inferred read-onlysite_screenshotSee a web page: a 1280-wide JPEG of any public URL, viewport or full page (capped at 6000 px), with its final URL, HTTP status and title.
Inferred read-onlyCONNECT WITH APPROVAL
Client installation
Review this server and its permissions before adding it. Secret placeholders must be set locally.
Codex
~/.codex/config.toml
[mcp_servers.how-is]
url = "https://how.is/mcp"
enabled = true
Claude Code
.mcp.json
{
"mcpServers": {
"how-is": {
"type": "http",
"url": "https://how.is/mcp"
}
}
}
Claude Desktop
Settings → Connectors → Add custom connector
Name: how-is
Remote MCP URL: https://how.is/mcp
Add this remote URL as a custom connector in Claude Desktop. Availability depends on the user plan and workspace policy.
Cursor
.cursor/mcp.json
{
"mcpServers": {
"how-is": {
"url": "https://how.is/mcp"
}
}
}
Visual Studio Code
.vscode/mcp.json
Add to Visual Studio Code{
"servers": {
"how-is": {
"type": "http",
"url": "https://how.is/mcp"
}
}
}
Generic MCP
Client-specific MCP configuration
{
"name": "how-is",
"transport": "streamable-http",
"url": "https://how.is/mcp"
}
MCP Inspector
Run the official MCP Inspector locally and enter the indexed Streamable HTTP endpoint.
TRUST AND VERIFICATION EVIDENCE
Loading Trust v2 evidence…
Checking the associated registrable domain. The BuiltWith key remains server-side.
Evidence is source-attributed and does not guarantee that a third-party server is safe. Risk labels are conservative metadata heuristics.