updated 2026-11-10 04:07 UTC

Domain Search MCP

Repository

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.

MCP Servers TypeScript Listed MIT

Is Domain Search MCP safe? Promising trust profile, but some evidence still deserves review.

OSSF Scorecard 3.2 / 10
Provenance Attested
Signed commits 1%
Last push yesterday
Advisories None known
Compare Domain Search MCP

How does it stack up against its MCP Servers neighbours?

Pick any agent to compare →
Suggest a correction

In detail: Domain Search MCP scores 65.1/100 (Grade B), ranked #529 of 1374 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.2/10; 1% of recent commits are signed; no published advisory affects its latest release (domain-search-mcp); last pushed 2026-11-09. Every point is earned from checkable signals — never paid placement. How scoring works →

How Domain Search MCP could raise its score

Each line changes one public signal and recomputes with the live scoring function. The gains don't add up exactly, because the score is capped near the top.

Already done? Suggest a correctionAdd the trust badge

Chain of custody

Scanners check what the code says. This traces who ships Domain Search MCP and whether that has changed: from the source repository, through how changes are reviewed and released, to the package you install. These are the checks for OWASP ASI04 Agentic Supply Chain Vulnerabilities.

  1. Source Partly signed

    github.com/dorukardahan/domain-search-mcp, MIT, last pushed 2026-11-09. 1% of the last 100 commits carry a verified signature; the rest can't be tied to a verified identity.

  2. Review and release Weak

    OpenSSF Scorecard rates the repository's practices 3.2/10 (scanned Oct 24, 2026, refresh pending). The checks that decide who can get a change released:

    • Code Review0
    • Branch Protection0
    • Signed Releasesn/a
    • Dangerous Workflow10
    • Token Permissions0
    • Pinned Dependencies2
    All 18 Scorecard checks
    Binary-Artifacts 5
    Branch-Protection 0
    CI-Tests 10
    CII-Best-Practices 0
    Code-Review 0
    Contributors 3
    Dangerous-Workflow 10
    Dependency-Update-Tool 0
    Fuzzing 0
    License 10
    Maintained 1
    Packaging 10
    Pinned-Dependencies 2
    SAST 0
    Security-Policy 10
    Signed-Releases -1
    Token-Permissions 0
    Vulnerabilities 0

  3. Published packages Linked and attested

    • npm domain-search-mcp Source link points back to this repo Build provenance attested

  4. What you install today No known advisories

    Latest release checked: domain-search-mcp 1.13.1. No published advisory affects it (OSV, checked 2026-11-10).

Changes to this chain

  • 2026-09-23 Package provenance attestation detected
  • 2026-08-30 OSSF Scorecard: 3.9/10

Evidence behind this score

Coverage B: 3 of 5 independent evidence types found.

  • GitHub repository data
  • Package downloads
  • Supply-chain checks
  • Public actions (missing)
  • Community mentions (missing)

Verify this score yourself

Every build re-issues Domain Search MCP’s score as an Ed25519-signed credential, valid for 7 days. You can check it offline against HVTracker’s published key; if anyone changes a number after signing, verification fails.

Signed credential (JSON) How to verify

What this score doesn’t check

It covers who ships the code, not what the code does. It doesn’t read tool descriptions or prompts for injected instructions, watch runtime behaviour, or find bugs nobody has disclosed yet. For that, run a content scanner before you connect it, such as Cisco MCP Scanner or Snyk Agent Scan.

How Domain Search MCP compares in MCP Servers

  1. #302 Persistent Project Context for xAI Grok 65.2 +0.1
  2. #303 Freshcontext MCP 65.1 ±0
  3. #304 Domain Search MCP 65.1 this agent
  4. #305 Ghidra MCP 65.0 −0.1
  5. #306 ZulipChat MCP Server 64.9 −0.2

Bars show each HVTrust score; the tick marks Domain Search MCP’s 65.1.

Where the 65.1 comes from

HVTrust dimensions vs the MCP Servers average

65.1 / 100 · 100.0% confidence

Domain Search MCP MCP Servers average (778 agents)

Safety / Integrity50% OSSF Scorecard · 30% provenance · 20% signed commits
11.5 / 25
0.7 above avg 10.8
Identity / Provenance60% listing status · 40% build provenance
18.0 / 18
4.3 above avg 13.7
Transparency50% declared license · 50% OSSF Scorecard
11.2 / 17
1.1 below avg 12.3
Maintenance60% last-push freshness · 40% commit activity
13.3 / 20
1.1 above avg 12.2
AdoptionLog-scaled stars · package downloads
6.9 / 20
0.7 below avg 7.6

Quick Trust Read

What Would Improve It
Increase the share of verified signed commits for clearer maintainer identity.
Recent Changes
2026-11-10
Rank Moved
Rank dropped 52 spots (#477 → #529)
2026-11-09
Grade Changed
Trust grade C → B
2026-11-09
Rank Moved
Rank rose 181 spots (#658 → #477)
Maintainer Checklist
Raise Scorecard signals Current OSSF Scorecard is 3.2/10. Tighten the weakest checks to improve public safety evidence.
Increase signed commits Raise the share of verified-signed commits to make maintainer identity and release history easier to trust.
Compare with another agent
View MCP Servers Report missing data
46.7
Activity sub-score · out of 100
#304
In MCP Servers

How to read this: HVTrust (0–100) weighs supply-chain signals (provenance, OSSF Scorecard, signed commits, open license) alongside real-world adoption. Grade B 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 →

Signals refreshed 2026-11-10 04:07 UTC · Repo last pushed yesterday

Rank Trend

2026-09-29 2026-11-10

Activity & Reach

Stars
28
Forks
7
Last Push
2026-11-09
yesterday
Commits (4 wk)
4?
Downloads (7d)
377
npm
HN mentions (30d)
—
Open Issues
2
Rank Change
▼52
was #477

Analysis

Activity Inputs

46.7 / 100
StarsRepository reach
8.8 / 30
FreshnessLast push recency
24.9 / 25
ActivityRecent commits
8.7 / 25
CommunityFork signal
4.2 / 20

Common questions about Domain Search MCP

Domain Search MCP has a mixed signal profile. Some trust indicators are present, others are missing. Whether it is safe for your use case depends on which gaps matter to you — review the breakdown below before adopting in production.
Does Domain Search MCP publish package provenance?
Yes. Domain Search MCP's package releases carry build provenance attestations, which cryptographically link the published package back to its source repository and CI workflow.
Does Domain Search MCP have an OpenSSF Scorecard?
Domain Search MCP has an OpenSSF Scorecard score of 3.2/10. The Scorecard checks for branch protection, signed releases, dependency updates, fuzzing, code review, and other supply-chain hygiene items. See the full check breakdown on this page.
Is Domain Search MCP actively maintained?
Actively maintained. The repository was pushed to within the last 1 day(s).
What license does Domain Search MCP use?
Domain Search MCP ships under MIT. A declared, OSI-approved license is one of the transparency signals HVTrust scores.
Are Domain Search MCP's commits signed?
1% of the last 100 commits to Domain Search MCP are verified-signed (GPG, SSH, S/MIME, or GitHub's signing flow). Signed commits help confirm that code was authored by who the commit claims.

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
Scored in HVTrust

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 →

MCP Server Support
high confidence
Implemented
Domain Search MCP appears to expose MCP server capabilities.
Detailed evidence is not shown in the public view.
External Service Dependencies
high confidence
2 detected
Public provider/service dependencies detected.
Credential signal: API keys or service config markers documented.
Tool / Plugin Surface
high confidence
1 tags
Broad capability areas detected.
  • database
Detailed evidence is not shown in the public view.
Package Provenance Drift
high confidence
Match
Published package metadata matches the tracked repo
Detailed evidence is not shown in the public view.
  • MCP signal live
  • External deps live
  • Tool / plugin surface live
  • Package provenance drift live
How this surface has changed

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.

2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Postgres, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected

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.

Submit a correction → Add the trust badge

Reputation Timeline

Signal history
Rank 30Grade 8HVTrust 4Scorecard 1Delisted 1Listed 1Provenance 1MCP 1Surface 1Score 1
2026-11-10
Rank Moved
Rank dropped 52 spots (#477 → #529)
2026-11-09
Grade Changed
Trust grade C → B
2026-11-09
Rank Moved
Rank rose 181 spots (#658 → #477)
2026-11-09
HVTrust Changed
HVTrust up 5.2pts (61.4 → 66.6)
2026-11-09
Activity Score Changed
Activity score up 13pts (33 → 47)
2026-11-01
Rank Moved
Rank dropped 20 spots (#633 → #653)
2026-10-26
Rank Moved
Rank dropped 10 spots (#608 → #618)
2026-10-24
Rank Moved
Rank rose 15 spots (#627 → #612)
2026-10-21
Rank Moved
Rank dropped 71 spots (#557 → #628)
2026-10-19
Rank Moved
Rank dropped 37 spots (#518 → #555)
2026-10-18
Grade Changed
Trust grade B → C
2026-10-13
Grade Changed
Trust grade C → B
2026-10-13
Rank Moved
Rank rose 31 spots (#527 → #496)
2026-10-09
Rank Moved
Rank dropped 11 spots (#500 → #511)
2026-10-01
Grade Changed
Trust grade B → C
2026-09-30
Grade Changed
Trust grade C → B
2026-09-30
Rank Moved
Rank rose 41 spots (#520 → #479)
2026-09-23
Provider Added
Runtime surface grew — new detected provider dependencies: Postgres, Redis
2026-09-23
Mcp Status Changed
Detected MCP server support changed: none → implemented
2026-09-23
Provenance Added
Package provenance attestation detected
2026-09-23
Grade Changed
Trust grade D → C
2026-09-23
Rank Moved
Rank rose 589 spots (#1082 → #493)
2026-09-23
HVTrust Changed
HVTrust up 41.7pts (22.6 → 64.3)
2026-09-22
Newly Listed
First tracked at rank #1082
2026-09-21
Removed From Active Tracking
Removed from active tracking
2026-09-18
Rank Moved
Rank rose 10 spots (#482 → #472)
2026-09-13
Grade Changed
Trust grade B → C
2026-09-13
Rank Moved
Rank dropped 24 spots (#453 → #477)
2026-09-08
Rank Moved
Rank dropped 12 spots (#425 → #437)
2026-09-07
Grade Changed
Trust grade D → B
2026-09-07
Rank Moved
Rank rose 628 spots (#1053 → #425)
2026-09-07
HVTrust Changed
HVTrust up 22.7pts (42.5 → 65.2)
2026-09-06
Rank Moved
Rank dropped 16 spots (#1037 → #1053)
2026-09-05
Rank Moved
Rank dropped 39 spots (#998 → #1037)
2026-09-04
Rank Moved
Rank dropped 27 spots (#971 → #998)
2026-09-03
Rank Moved
Rank dropped 58 spots (#913 → #971)
2026-09-02
Rank Moved
Rank dropped 21 spots (#892 → #913)
2026-09-01
Rank Moved
Rank dropped 33 spots (#859 → #892)
2026-08-31
Rank Moved
Rank dropped 33 spots (#826 → #859)
2026-08-30
Scorecard Added
OSSF Scorecard: 3.9/10
2026-08-30
Rank Moved
Rank rose 68 spots (#894 → #826)
2026-08-30
HVTrust Changed
HVTrust up 5.4pts (36.3 → 41.7)
2026-08-29
Rank Moved
Rank dropped 45 spots (#849 → #894)
2026-08-28
Rank Moved
Rank dropped 41 spots (#808 → #849)
2026-08-27
Rank Moved
Rank dropped 31 spots (#777 → #808)
2026-08-26
Rank Moved
Rank dropped 100 spots (#677 → #777)
2026-08-22
Rank Moved
Rank dropped 12 spots (#661 → #673)
2026-08-21
Rank Moved
Rank dropped 16 spots (#645 → #661)
2026-08-16
Rank Moved
Rank dropped 11 spots (#627 → #638)
GitHub → npm: domain-search-mcp

Embed Badge Badge guide for maintainers →

For maintainers
HVTrust 65.1 Grade B
Markdown:
[![HVTrust](https://hvtracker.net/badge/domain-search-mcp.svg)](https://hvtracker.net/agents/domain-search-mcp)
HTML:
<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

Data sources
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.4 · Raw JSON