FastDomainCheck MCP Server (Python)

Created By
bingala year ago
MCP Server for checking domain name availability using WHOIS and DNS via stdio.
Overview

what is FastDomainCheck MCP Server?

FastDomainCheck MCP Server is a Python-based server that checks the availability of domain names using WHOIS and DNS protocols. It allows users to verify if single or multiple domain names are already registered.

how to use FastDomainCheck MCP Server?

To use the FastDomainCheck MCP Server, send a JSON request containing an array of domain names to check. The server will respond with the registration status of each domain.

key features of FastDomainCheck MCP Server?

  • Bulk domain registration status checking
  • Dual verification using WHOIS and DNS
  • Support for Internationalized Domain Names (IDN)
  • Concise output format
  • Built-in input validation and error handling

use cases of FastDomainCheck MCP Server?

  1. Checking the availability of multiple domain names for a new website.
  2. Verifying domain registration status for business purposes.
  3. Assisting developers in domain management tasks.

FAQ from FastDomainCheck MCP Server?

  • How many domains can I check at once?

You can check up to 50 domains in a single request.

  • What happens if I send an empty domain list?

The server will return an error indicating that the domains list cannot be empty.

  • Is there a limit on the length of domain names?

Yes, each domain name can be a maximum of 255 characters.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
bingal
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
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)

a day ago