Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.basicScandal/whoisgenius

REMOTE · API.WHOISGENI.US · SCANNED SEP 21

Domain attribution and correlation for AI agents, with confidence and per-signal evidence.

Available components

0 this week 79 Trust /100
Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability81
  • AI-judged instruction clarity (excellent).Pass
  • Tool/resource definitions use about 133 tokens (~66/item across 2 items; 2 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 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities20
  • Spec-recency check failed: implements MCP spec 2024-11-05; the latest is 2026-07-28. See how to fix → Fail
Install

How do I install the io.github.basicScandal/whoisgenius MCP server?

io.github.basicScandal/whoisgenius is a hosted endpoint at https://api.whoisgeni.us/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · api.whoisgeni.us

# add to Claude Code
claude mcp add --transport http basicscandal-whoisgenius 'https://api.whoisgeni.us/mcp'
// .cursor/mcp.json
{
  "mcpServers": {
    "basicscandal-whoisgenius": {
      "url": "https://api.whoisgeni.us/mcp"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "basicscandal-whoisgenius": {
      "type": "http",
      "url": "https://api.whoisgeni.us/mcp"
    }
  }
}
# ~/.codex/config.toml
[mcp_servers.basicscandal-whoisgenius]
url = "https://api.whoisgeni.us/mcp"
// opencode.json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "basicscandal-whoisgenius": {
      "type": "remote",
      "url": "https://api.whoisgeni.us/mcp",
      "enabled": true
    }
  }
}
# add to OpenClaw
openclaw mcp add basicscandal-whoisgenius --url 'https://api.whoisgeni.us/mcp' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  basicscandal-whoisgenius:
    url: "https://api.whoisgeni.us/mcp"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "basicscandal-whoisgenius": {
      "Transport": "http",
      "Url": "https://api.whoisgeni.us/mcp"
    }
  }
}
# add to Vellum
assistant mcp add basicscandal-whoisgenius -t streamable-http -u 'https://api.whoisgeni.us/mcp'
// mcp.json
{
  "mcpServers": {
    "basicscandal-whoisgenius": {
      "type": "http",
      "url": "https://api.whoisgeni.us/mcp"
    }
  }
}

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

Changelog

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.

  • 26 Aug 26 +2
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 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.

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 26 Jul 26 0

    First indexed and scored.

Diagnostics

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 · Probed https://api.whoisgeni.us/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=api.whoisgeni.us CN=Amazon RSA 2048 M01,O=Amazon,C=US 10 Sept 2026 26 Mar 2027 RSA 2048 SHA256-RSA caa26ab663ad4a91a03105f34a9ce19
SANs: api.whoisgeni.us
CN=Amazon RSA 2048 M01,O=Amazon,C=US (CA) CN=Amazon Root CA 1,O=Amazon,C=US 23 Aug 2022 23 Aug 2030 RSA 2048 SHA256-RSA 77312380b9d6688a33b1ed9bf9ccda68e0e0f
CN=Amazon Root CA 1,O=Amazon,C=US (CA) CN=Starfield Services Root Certificate Authority - G2,O=Starfield Technologies\, Inc.,L=Scottsdale,ST=Arizona,C=US 25 May 2015 31 Dec 2037 RSA 2048 SHA256-RSA 67f944a2a27cdf3fac2ae2b01f908eeb9c4c6

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of api.whoisgeni.us. Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
us. present 59017 8 Verified
whoisgeni.us. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains; preload
content-security-policy default-src 'self'; script-src 'self' 'unsafe-inline' https://us.i.posthog.com https://us-assets.i.posthog.com; connect-src 'self' https://api.whoisgeni.us https://us.i.posthog.com https://us-assets.i.posthog.com https://cognito-idp.us-west-2.amazonaws.com; style-src 'self' 'unsafe-inline' https://fonts.googleapis.com; img-src 'self' data:; font-src 'self' https://fonts.gstatic.com
x-content-type-options nosniff
x-frame-options DENY
referrer-policy strict-origin-when-cross-origin
permissions-policy camera=(), microphone=(), geolocation=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://api.whoisgeni.us/mcp Verified 200
http (plaintext) http://api.whoisgeni.us/mcp HTTPS enforced 301 https://api.whoisgeni.us/mcp
MCP tools · 2 exposed · ~133 tokens

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 →

Tool Tokens
analyze_domain ~64

Analyze a domain name to identify its operator and attribution signals. Returns a human-readable Markdown summary and machine-readable structured output containing ranked entity candidates with confidence scores and per-signal evidence.

NameTypeReqDescription
domainstringyesFully qualified domain name to analyze (e.g. 'example.com').

No output schema declared.

No examples provided.

correlate_domains ~69

Correlate 2-15 domain names to detect shared infrastructure, common operators, and clustering evidence. Returns a human-readable Markdown summary and machine-readable structured output containing correlation clusters, pairwise scores, and shared signals.

NameTypeReqDescription
domainsarrayyesList of domain names to correlate (2-15).

No output schema declared.

No examples provided.

Common questions

What is the io.github.basicScandal/whoisgenius MCP server?

io.github.basicScandal/whoisgenius is an MCP server listed in the public MCP registry as io.github.basicScandal/whoisgenius. Domain attribution and correlation for AI agents, with confidence and per-signal evidence. This page covers its hosted endpoint (https://api.whoisgeni.us/mcp).

Is the io.github.basicScandal/whoisgenius MCP server safe to use?

io.github.basicScandal/whoisgenius scores 79 out of 100 on VerifyMCP. 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.basicScandal/whoisgenius MCP server expose?

io.github.basicScandal/whoisgenius exposes 2 tools: analyze_domain, correlate_domains. Their descriptions and schemas cost roughly 133 tokens of context every time the server is loaded.

Does the io.github.basicScandal/whoisgenius MCP server require authentication?

No. We connected to io.github.basicScandal/whoisgenius without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the io.github.basicScandal/whoisgenius MCP server still maintained?

io.github.basicScandal/whoisgenius 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.