Porkbun Domain Availability MCP Server
Related Servers
Alternatives to Porkbun Domain Availability MCP Server
No user-submitted related servers found.
Related Servers
- FlicenseNot gradedqualityDmaintenanceEnables checking domain name availability using WHOIS lookups and DNS resolution. Supports both single and batch domain checking with detailed availability analysis.-
- FlicenseNot gradedqualityDmaintenanceEnables checking domain availability using WHOIS and DNS resolution, with support for single and batch queries.28-
- AlicenseAqualityDmaintenanceEnables checking domain name availability for single or multiple domains using WHOIS and DNS verification.121MIT
- AlicenseNot gradedqualityDmaintenanceEnables bulk domain registration status checking for over 200 TLDs using WHOIS and DNS fallback.6 npmMIT
- AlicenseAqualityCmaintenanceEnables fast, token-efficient bulk domain name search for AI agents, checking up to 1,000 domains per request to see availability statuses.1Apache 2.0
- FlicenseNot gradedqualityDmaintenanceEnables domain availability checking through dual verification using WHOIS lookups and DNS resolution. Supports both single and batch processing to provide detailed analysis on whether domains are likely available or already registered.4-
TDQS
Scored across 2 tools
The two tools have clearly distinct purposes: one handles bulk checks for up to 10 domains with consolidated results, while the other checks a single domain with pricing details. There is no overlap or ambiguity between them, as each serves a specific use case within the domain availability domain.
Both tools follow a consistent verb_noun pattern with snake_case naming: 'bulk_check_domains_availability' and 'check_domain_availability'. The naming is predictable and readable, clearly indicating the action (check) and the target (domain availability), with 'bulk' appropriately modifying the first tool.
With only 2 tools, the server feels thin for a domain availability service, as it lacks operations like domain registration, management, or search. However, given the specific focus on availability checks and API rate limits, the count is borderline but reasonable for a minimal, focused implementation.
The tool surface is significantly incomplete for a domain availability server, as it only provides check operations without any ability to register, update, or manage domains. This creates dead ends for agents trying to perform full domain lifecycle tasks, limiting the server to read-only functionality.