how.is MCP

An official MCP server providing domain and IP intelligence tools. It enables agents to perform DNS lookups, WHOIS queries, TLS certificate checks, DNSSEC validation, email authentication analysis, blacklist checks, and IP address intelligence. The server supports pay-per-call pricing via prepaid API keys or crypto payments, allowing automated security assessments and domain monitoring.

Endpoint and access

No sign-in: your client connects and lists tools immediately, with no account or key.

No sign-inEndpoint checked 2026-10-26Operated by how.is

MCP endpoint (Streamable HTTP)

https://how.is/mcp

Vendor documentation

What you can do with it

Perform DNS record lookups and resolve timing analysis
Check domain WHOIS details and registration age
Validate TLS certificate validity and expiration
Verify email authentication posture (SPF, DKIM, DMARC)

Tools advertised by the last live check:

domain_profile
domain_trust
domain_dns
domain_whois
domain_age
domain_available
domain_tls
domain_dnssec
domain_email_auth
domain_security_score
domain_blacklist
ip_lookup
site_status
site_screenshot
page_watch
bot_observatory
add_credit

Connect from your client

Each snippet registers the same endpoint; pick the client you use.

This server is operated by the named third party. Listing and endpoint checks are not an endorsement or a security audit. Review the operator's permissions, terms, and data handling before connecting. How listings are checked and corrected.

Claude Code

Run this once in a terminal. It registers a Streamable HTTP server. Use --scope project to write .mcp.json for the repo.

Claude Code configuration

claude mcp add --transport http how-is-mcp https://how.is/mcp

Codex

Run this once. Codex stores MCP servers in ~/.codex/config.toml (or .codex/config.toml in a trusted project).

Codex configuration

codex mcp add how-is-mcp --url https://how.is/mcp

Cursor

Merge this server into .cursor/mcp.json in your project, then enable how-is-mcp in your MCP settings.

Cursor configuration

{
  "mcpServers": {
    "how-is-mcp": {
      "url": "https://how.is/mcp"
    }
  }
}

Cline

Merge this into cline_mcp_settings.json (Cline → MCP Servers → Configure). The type must be streamableHttp for a remote HTTP server.

Cline configuration

{
  "mcpServers": {
    "how-is-mcp": {
      "type": "streamableHttp",
      "url": "https://how.is/mcp",
      "disabled": false
    }
  }
}

VS Code

Merge this server into .vscode/mcp.json. Use MCP: List Servers to start how-is-mcp and inspect its tools.

VS Code configuration

{
  "servers": {
    "how-is-mcp": {
      "type": "http",
      "url": "https://how.is/mcp"
    }
  }
}

Gemini CLI

Run this once. It writes .gemini/settings.json in the current project; pass --scope user for ~/.gemini/settings.json.

Gemini CLI configuration

gemini mcp add --transport http how-is-mcp https://how.is/mcp

Claude Desktop

Merge this into claude_desktop_config.json (macOS: ~/Library/Application Support/Claude/, Windows: %APPDATA%\Claude\), then restart Claude Desktop.

Claude Desktop configuration

{
  "mcpServers": {
    "how-is-mcp": {
      "url": "https://how.is/mcp"
    }
  }
}

Windsurf

Merge this into ~/.codeium/windsurf/mcp_config.json, then refresh MCP in Cascade. Windsurf remote servers use serverUrl, not url.

Windsurf configuration

{
  "mcpServers": {
    "how-is-mcp": {
      "serverUrl": "https://how.is/mcp"
    }
  }
}

Ground your agent in cited data

how.is MCP gives your agent tools. Koskamo gives it reviewed, cited facts to check its answers against. Add it as a second MCP server; public reads need no API key.

Connect Koskamo Browse datasets

See all 1,274

Do you run how.is MCP?

Prove ownership with a DNS record, a well-known file, or your Official MCP Registry entry, and your edits publish immediately. Proofs are re-checked weekly; admins can still hide or remove a listing.

Claim this listing