Domain Search MCP
Zero-config domain availability MCP server for Claude & ChatGPT. Live pricing via Porkbun, premium/auction detection via GoDaddy, AI suggestions, RDAP/WHOIS fallback. Stdio + HTTP.
Is Domain Search MCP safe? Promising trust profile, but some evidence still deserves review.
Compare Domain Search MCP
How does it stack up against its MCP Servers neighbours?
Pick any agent to compare →In detail: Domain Search MCP scores 64.1/100 (Grade C), ranked #504 of 1325 tracked open-source AI agent projects, on evidence coverage B (3 of 5 independent signal types). The public evidence: its packages ship with cryptographic provenance; OSSF Scorecard rates its supply-chain practices 3.9/10; 1% of recent commits are signed; last pushed 2026-09-13. Every point is earned from checkable signals — never paid placement. How scoring works →
How Domain Search MCP compares in MCP Servers
- #291 Google Maps MCP Server 64.2 +0.1
- #292 GitLab MCP Server 64.1 ±0
- #293 Domain Search MCP 64.1 this agent
- #294 Google Analytics MCP 63.9 −0.2
- #295 iCloud MCP 63.9 −0.2
Bars show each HVTrust score; the tick marks Domain Search MCP’s 64.1.
Where the 64.1 comes from
HVTrust dimensions vs the MCP Servers average
64.1 / 100 · 100.0% confidenceDomain Search MCP MCP Servers average (775 agents)
Quick Trust Read
How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade C reflects the trust score band: A ≥ 80, B ≥ 65, C ≥ 50, D < 50. Evidence coverage B is separate — it grades how many independent signal types back the score (3 of 5), so a high score on thin evidence stays visible. Full methodology →
Rank Trend
Activity & Reach
Analysis
Activity Inputs
36.3 / 100Supply Chain Trust
Common questions about Domain Search MCP
Does Domain Search MCP publish package provenance?
Does Domain Search MCP have an OpenSSF Scorecard?
Is Domain Search MCP actively maintained?
What license does Domain Search MCP use?
Are Domain Search MCP's commits signed?
Not a safety endorsement. HVTracker describes what public signals show, not whether a project is safe for your use case. Run your own security review before adopting in production.
AI agent surface
MCP, providers, tool surface
These runtime-trust fields — detected from public repo docs and manifests — contribute a bounded adjustment to this project's HVTrust score alongside supply-chain evidence. The exact values each field can add or subtract are documented in the methodology → Compare this surface across every listed agent in the capability matrix →
- database
- MCP signal live
- External deps live
- Tool / plugin surface live
- Package provenance drift live
Detected changes to Domain Search MCP's runtime surface and supply-chain posture, from daily public-signal snapshots. A change here means our detectors see something different — a genuinely changed capability, or better evidence of an existing one.
Maintain Domain Search MCP?
For maintainers
HVTrust scores Domain Search MCP from public signals only — we never contact maintainers first. If a signal is wrong, stale, or missing (provenance you publish, a Scorecard you run, signed releases), tell us and we'll review it. Corrections are public and tracked on GitHub.
Reputation Timeline
Signal history
Embed Badge Badge guide for maintainers →
For maintainers
[](https://hvtracker.net/agents/domain-search-mcp)
<a href="https://hvtracker.net/agents/domain-search-mcp"><img src="https://hvtracker.net/badge/domain-search-mcp.svg" alt="HVTrust"></a>
Other agents in MCP Servers
GitHub REST API (repo, commits, stars, forks, license) · npm Registry (downloads, provenance) · OpenSSF Scorecard CLI
Each agent's signals refresh once daily across 6 staggered batches. Methodology v4.3 · Raw JSON