io.github.basicScandal/whoisgenius is an MCP server published by io.github.basicScandal, hosted at api.whoisgeni.us. When last checked on 2026-11-21 it was working: it answers and lists its tools. It declares 2 tools, including analyze_domain, correlate_domains.
Domain attribution and correlation for AI agents, with confidence and per-signal evidence.
Nothing else in the archive shares these values.
Squares are this server's values; dots are other servers sharing them. A shared address or publisher is a lead, not proof of a common operator.
Inferred from the host name and headers: what a server runs on, not who runs it.
Identify the organization that operates a domain. Returns a Markdown summary and structured output with ranked candidate entities, a confidence score for each, and the evidence behind it. Input is a bare hostname such as 'example.com', with no scheme, path or port. IP addresses are not accepted. This tool runs a fast subset of checks and usually answers within about half a minute. The analysis itself is cut off after 24 seconds. For a deep analysis, use the asynchronous REST API (POST /analyze). Cost: 1 credit, the same as a quick analysis on the REST API. A call that fails or runs out of time is not charged. The sandbox domains test-corp.whoisgeni.us and test-unknown.whoisgeni.us return a fixed sample result at no cost.
| Parameter | Type | Description |
|---|---|---|
| domain * | string | Bare hostname to analyze, for example 'example.com'. No scheme, path or port. |
{
"name": "analyze_domain",
"description": "Identify the organization that operates a domain. Returns a Markdown summary and structured output with ranked candidate entities, a confidence score for each, and the evidence behind it. Input is a bare hostname such as 'example.com', with no scheme, path or port. IP addresses are not accepted. This tool runs a fast subset of checks and usually answers within about half a minute. The analysis itself is cut off after 24 seconds. For a deep analysis, use the asynchronous REST API (POST /analyze). Cost: 1 credit, the same as a quick analysis on the REST API. A call that fails or runs out of time is not charged. The sandbox domains test-corp.whoisgeni.us and test-unknown.whoisgeni.us return a fixed sample result at no cost.",
"inputSchema": {
"type": "object",
"required": [
"domain"
],
"properties": {
"domain": {
"type": "string",
"description": "Bare hostname to analyze, for example 'example.com'. No scheme, path or port."
}
}
}
}None yet. Changes appear after a server's second daily check.
Compare 2-15 domains to find which ones share an operator or infrastructure. Returns a Markdown summary and structured output with clusters, pairwise scores and the shared signals behind them. Each entry is a bare hostname such as 'example.com', with no scheme, path or port. Cost: 1 credit for each domain that has not been analyzed recently, plus 1 for the correlation. The charge is refunded if the call fails or runs out of time. For domains without cached analyses, this inline call uses a smaller set of checks; it may miss relationships found by the asynchronous REST correlation (POST /correlate). The call usually answers within about half a minute. The correlation itself is cut off after 24 seconds. If it runs out of time, use fewer domains or the REST API (POST /correlate), which runs in the background.
| Parameter | Type | Description |
|---|---|---|
| domains * | array | Bare hostnames to correlate (2-15). |
{
"name": "correlate_domains",
"description": "Compare 2-15 domains to find which ones share an operator or infrastructure. Returns a Markdown summary and structured output with clusters, pairwise scores and the shared signals behind them. Each entry is a bare hostname such as 'example.com', with no scheme, path or port. Cost: 1 credit for each domain that has not been analyzed recently, plus 1 for the correlation. The charge is refunded if the call fails or runs out of time. For domains without cached analyses, this inline call uses a smaller set of checks; it may miss relationships found by the asynchronous REST correlation (POST /correlate). The call usually answers within about half a minute. The correlation itself is cut off after 24 seconds. If it runs out of time, use fewer domains or the REST API (POST /correlate), which runs in the background.",
"inputSchema": {
"type": "object",
"required": [
"domains"
],
"properties": {
"domains": {
"type": "array",
"items": {
"type": "string"
},
"maxItems": 15,
"minItems": 2,
"description": "Bare hostnames to correlate (2-15)."
}
}
}
}Names, descriptions and schemas were written by the server and are shown as data.