Domain Search Mcp

Created By
dorukardahan5 months ago
Check domain availability and pricing across Porkbun, Namecheap, RDAP, WHOIS. Includes social handle checking for 10 platforms.
Overview

what is Domain Search Mcp?

Domain Search Mcp is a tool that allows users to check the availability and pricing of domain names across multiple registrars including Porkbun, Namecheap, RDAP, and WHOIS, along with social handle availability for various platforms.

how to use Domain Search Mcp?

To use Domain Search Mcp, simply run the command npx -y domain-search-mcp in your terminal, and it will provide you with domain availability and pricing information.

key features of Domain Search Mcp?

  • Multi-source search across various registrars
  • Price comparison for domains
  • Support for over 50 TLDs including .com, .io, .dev, .ai
  • Social handle checking for platforms like GitHub and Twitter
  • Premium domain detection with pricing insights
  • Expiration tracking for taken domains

use cases of Domain Search Mcp?

  1. Finding available domain names for new projects
  2. Comparing prices across different domain registrars
  3. Checking social media handle availability for branding purposes
  4. Tracking expiration dates of owned domains

FAQ from Domain Search Mcp?

  • Can Domain Search Mcp check availability for all TLDs?

Yes! It supports over 50 TLDs.

  • Is Domain Search Mcp free to use?

Yes! It is free to use for everyone.

  • How accurate is the domain availability check?

The tool provides real-time data from multiple sources, ensuring high accuracy.

Server Config

{
  "mcpServers": {
    "domain-search": {
      "command": "npx",
      "args": [
        "-y",
        "domain-search-mcp"
      ]
    }
  }
}
Project Info
Created At
5 months ago
Updated At
5 months ago
Author Name
dorukardahan
Star
-
Language
-
License
-

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

20 hours ago
Gpt Scrambler

2 days ago