whois-mcp-server

An MCP server that provides WHOIS lookup capabilities to AI agents (e.g., to query domain registration/registrar and related WHOIS records) via MCP tools.

Evaluated Apr 04, 2026 (17d ago)
Homepage ↗ Repo ↗ Infrastructure whois mcp osint domain-reputation agent-tools
⚙ Agent Friendliness
40
/ 100
Can an agent use this?
🔒 Security
47
/ 100
Is it safe for agents?
⚡ Reliability
8
/ 100
Does it work consistently?

Score Breakdown

⚙ Agent Friendliness

MCP Quality
45
Documentation
30
Error Messages
0
Auth Simplicity
60
Rate Limits
10

🔒 Security

TLS Enforcement
70
Auth Strength
40
Scope Granularity
30
Dep. Hygiene
45
Secret Handling
50

Security posture depends on how the MCP server is implemented and hosted (network exposure, transport security, and whether any upstream WHOIS credentials/API keys are used). No repository details were provided, so scores are necessarily conservative and based on common patterns for self-hosted MCP tool servers.

⚡ Reliability

Uptime/SLA
0
Version Stability
0
Breaking Changes
0
Error Recovery
30
AF Security Reliability

Best When

You need automated WHOIS lookups integrated into an agent workflow and can tolerate variability/inconsistency in WHOIS responses across TLDs/registries.

Avoid When

You have strict requirements around data accuracy/consistency, or you need predictable pagination/structured datasets across all WHOIS sources.

Use Cases

  • Domain reconnaissance for security investigations
  • Checking domain registration/expiration details
  • Supporting OSINT workflows in automated agents
  • Enriching datasets with WHOIS-derived fields

Not For

  • High-volume bulk WHOIS scraping at scale (may violate registrar/WHOIS terms or rate limits)
  • Use as the sole source of truth for compliance or legal determinations
  • Applications that require a formal paid/regulated data product with guaranteed accuracy

Interface

REST API
No
GraphQL
No
gRPC
No
MCP Server
Yes
SDK
No
Webhooks
No

Authentication

Methods: None or upstream MCP host auth (not determinable from provided info)
OAuth: No Scopes: No

No authentication requirements were provided in the input. Many MCP servers do not require auth if self-hosted, but this can’t be confirmed without the repository/manifest details.

Pricing

Free tier: No
Requires CC: No

Pricing cannot be determined from the provided package name alone.

Agent Metadata

Pagination
none
Idempotent
False
Retry Guidance
Not documented

Known Gotchas

  • WHOIS responses vary widely by TLD/registry and may be incomplete or differently formatted.
  • Some WHOIS endpoints/rate limits may throttle or block automated queries; agents may need backoff and caching.
  • WHOIS data can be inconsistent; agents should validate/normalize fields and handle missing values gracefully.

Alternatives

Full Evaluation Report

Comprehensive deep-dive: security analysis, reliability audit, agent experience review, cost modeling, competitive positioning, and improvement roadmap for whois-mcp-server.

AI-powered analysis · PDF + markdown · Delivered within 30 minutes

$99

Package Brief

Quick verdict, integration guide, cost projections, gotchas with workarounds, and alternatives comparison.

Delivered within 10 minutes

$3

Score Monitoring

Get alerted when this package's AF, security, or reliability scores change significantly. Stay ahead of regressions.

Continuous monitoring

$3/mo

Scores are editorial opinions as of 2026-04-04.

8642
Packages Evaluated
17761
Need Evaluation
586
Need Re-evaluation
Community Powered