v0.4.1

ebc48cb: Transport Mode Flexibility

Release Date: 2025-10-30 10:22:46 UTC

Summary

This release significantly enhances the application's transport layer, introducing dynamic mode switching between stdio and sse via the new MCP_TRANSPORT environment variable. This provides critical flexibility for deployment, particularly optimizing for cloud-native environments like Google Cloud Run while maintaining full compatibility with existing stdio-based integrations such as Claude Desktop. The deploy.sh script has been updated to streamline Cloud Run deployments, and comprehensive documentation has been added to the README.md.

Feature Enhancements

• Dynamic Transport Mode Selection: Introduced the MCP_TRANSPORT environment variable, allowing operators to dynamically switch between stdio and sse transport modes.
  • stdio mode: Continues to serve as the default, ensuring seamless operation with existing integrations like Claude Desktop.
  • sse mode: Provides native support for Server-Sent Events, optimizing the application for Google Cloud Run and other web-based deployments.
• Streamlined Cloud Deployment: The deploy.sh script has been updated to automatically configure MCP_TRANSPORT=sse when deploying to Google Cloud Run, simplifying the deployment process for cloud environments.
• Enhanced Documentation: The README.md has been updated to include detailed information on configuring and utilizing the new transport modes, ensuring clarity for developers and operators.

Fixes

• Transport Layer Limitation: Resolved a functional limitation in the transport layer, enabling robust support for sse mode which was previously unavailable for certain cloud deployment scenarios.

Technical Specifications

Modified Files

• README.md (modified)
  • Changes: 34 total
  • Added: 20 lines
  • Removed: 14 lines
• deploy.sh (modified)
  • Changes: 1 total
  • Added: 1 lines
  • Removed: 0 lines
• src/mcp_domain_availability/main.py (modified)
  • Changes: 32 total
  • Added: 11 lines
  • Removed: 21 lines

Repository Information

• Commit: ebc48cb
• Author: @imprvhub
• Branch: main

Deployment Instructions

Update Procedure

1. For Google Cloud Run deployments, utilize the updated deploy.sh script, which now automatically configures the MCP_TRANSPORT environment variable to sse for optimized cloud performance.
2. For other web or cloud-native deployments, manually set the MCP_TRANSPORT environment variable to sse (e.g., export MCP_TRANSPORT=sse or equivalent platform-specific configuration) before application startup.
3. Existing stdio-based integrations, such as Claude Desktop, will continue to function without modification as stdio remains the default transport mode.
4. Consult the updated README.md for comprehensive details on configuring and utilizing the various transport modes.

Breaking Changes

None - Full backward compatibility maintained.

Acknowledgments

Transport compatibility issue reported by @nilsreichardt in #7.

---

This document was automated by Gitset.dev

v0.4.0

0366b8c: Docker Support and Automated Deployment

Release Date: 2025-10-29 21:16:23 UTC

Summary

This release significantly enhances the operational capabilities of the mcp-domain-availability project by introducing comprehensive Dockerization and a streamlined deployment process. Key updates include the addition of a Dockerfile for containerized execution, a new deploy.sh script to automate deployment, and updates to the README.md to provide clear instructions for running the application in a Docker environment. These improvements aim to simplify setup, ensure consistent environments, and facilitate easier deployment for developers and operators.

Feature Enhancements

• User-facing improvements
  • The README.md has been updated with detailed instructions on how to build and run the mcp-domain-availability application using Docker, significantly improving the onboarding experience and simplifying operational procedures.
• Technical enhancements implemented
  • A Dockerfile has been introduced, enabling the containerized deployment of the mcp-domain-availability application. This ensures environment consistency and facilitates scalable operations.
  • A new deploy.sh script has been added to automate the deployment process, streamlining the setup and execution of the application within a containerized environment.
  • Adjustments were made to src/mcp_domain_availability/main.py to ensure full compatibility and performance within the newly introduced Docker container environment.

Technical Specifications

Modified Files

• Dockerfile (modified)
  • Changes: 4 total
  • Added: 3 lines
  • Removed: 1 lines
• README.md (modified)
  • Changes: 52 total
  • Added: 52 lines
  • Removed: 0 lines
• deploy.sh (added)
  • Changes: 15 total
  • Added: 15 lines
  • Removed: 0 lines
• src/mcp_domain_availability/main.py (modified)
  • Changes: 8 total
  • Added: 6 lines
  • Removed: 2 lines

Repository Information

• Commit: 0366b8c
• Author: @imprvhub
• Branch: main

Deployment Instructions

Prerequisites

• Docker installed and running on your system.

Update Procedure

1. Ensure your local repository is synchronized with the latest main branch.
2. Navigate to the root directory of the mcp-domain-availability project.
3. Build the Docker image using the provided Dockerfile by executing the appropriate Docker build command (e.g., docker build -t mcp-domain-availability .).
4. Execute the new deploy.sh script to run the application within a Docker container (e.g., ./deploy.sh).
5. Verify the application is running correctly by checking the Docker container logs or accessing its exposed services as detailed in the updated README.md.

Breaking Changes

None - Full backward compatibility maintained

Attributions

This release incorporates the original implementation made by @nilsreichardt.
Reference commits:

• 1f5812b
• b917236

---

This document was automated by Gitset.dev

v0.3.2

ffd5d2b: Fix: Validate domain length per TLD

Overview

This release addresses an issue where the domain availability checker incorrectly reported certain short domains (specifically two-letter domains) as available, even though they are not permitted by the rules of their respective Top-Level Domains (TLDs).

Implementation Note: Due to the lack of comprehensive, centralized documentation on minimum domain length requirements per TLD (as each local registry like DENIC has different rules), a conservative approach was implemented by setting a minimum of 3 characters for Second Level Domains (SLDs) across all TLDs. While this may not reflect the exact requirements for every TLD, it prevents false positives for clearly invalid short domains. The code architecture allows for easy updates to TLD-specific minimums as more precise information becomes available through future research.

Release Details

• Release Date: 2025-06-18 14:54:56 UTC
• Commit: ffd5d2b
• Author: Iván Luna
• Branch(es): main

Changes

This release includes a critical bug fix related to domain validation.

Bug Fixes

• Incorrect Availability for Short Domains: Previously, the tool did not validate the length of a domain name according to TLD rules. This led to incorrect "available" results for domains that are syntactically invalid. The fix introduces pre-check validation with a conservative 3-character minimum for SLDs. Future updates will refine TLD-specific requirements as accurate data becomes available.

Modified Files

• src/mcp_domain_availability/main.py (modified)
  • Changes: 79 total
  • Added: 74 lines
  • Removed: 5 lines

Testing

Testing focused on verifying the validation logic prevents false availability reports for short domains while maintaining functionality for valid domain queries.

What's Changed

• fix: Validate domain length per TLD by @imprvhub in #5

New Contributors

• @sascharucks for reporting the domain validation issue in #2 that led to this improvement

Full Changelog: 0.3.1...0.3.2

v0.3.1

879f715: Deployment: Dockerfile and Smithery config

Overview

This release focuses on enhancing the project's deployment infrastructure by introducing configuration for Smithery and updating the Dockerfile. The primary purpose is to standardize and potentially automate the build and deployment process using Smithery, a tool designed for managing project builds and releases. This change is crucial for establishing a more robust and repeatable deployment pipeline. The expected impact is primarily internal, streamlining development and CI/CD workflows, leading to more consistent builds and easier deployments. While not directly affecting end-user functionality, this foundational work improves the project's maintainability and future delivery capabilities.

Release Details

• Release Date: 2025-05-22 15:58:49 UTC
• Commit: 879f715
• Author: Iván Luna
• Branch(es): main

Changes

This release introduces new configuration for the Smithery build tool and modifies the Dockerfile to align with the updated deployment strategy.

Configuration Updates

• Smithery Configuration: A new smithery.yaml file has been added to define the project's build and release process using Smithery. This configuration specifies how the project should be built, versioned, and potentially packaged or deployed, laying the groundwork for automated release management.
• Dockerfile Modification: The existing Dockerfile has been updated. These changes likely integrate the build process with Smithery or adjust the container build steps to be compatible with the new deployment workflow.

Modified Files

• Dockerfile (modified)

  • Changes: 3 total
  • Added: 2 lines
  • Removed: 1 lines

• README.md (modified)

  • Changes: 8 total
  • Added: 8 lines
  • Removed: 0 lines

• smithery.yaml (added)

  • Changes: 12 total
  • Added: 12 lines
  • Removed: 0 lines

Testing

Testing for this release involved verifying the integrity of the new smithery.yaml configuration and ensuring that the modified Dockerfile builds correctly. Manual tests were performed to execute the Smithery build process locally and confirm that it produces the expected artifacts or performs the defined steps without errors.

Instructions for Update

This release primarily affects the project's internal build and deployment configuration. Users building the project from source or using the Dockerfile will need to pull the latest changes from the main branch. The updated Dockerfile should be used for building the container image. Developers utilizing Smithery will need the smithery.yaml file in the project root.

Additional Notes

This release focuses on infrastructure improvements and does not introduce any changes to the application's core functionality or user interface. There are no breaking changes for existing users of the application itself. The changes are primarily relevant for developers and CI/CD environments.

What's Changed

• Deployment: Dockerfile and Smithery config by @smithery-ai in #1

New Contributors

• @smithery-ai made their first contribution in #1

Full Changelog: 0.3.0...0.3.1

v0.3.0

0c7e4db: Add Smithery Configuration

Overview

This release introduces the initial configuration file for Smithery, an automation tool designed to streamline and standardize the release process for this repository. The purpose of adding this configuration is to automate tasks such as version bumping, changelog generation, and potentially release tagging and publishing in the future. This foundational step is crucial for improving development efficiency and ensuring consistent release practices. While this specific release does not introduce user-facing features or changes, it lays the groundwork for future automated workflows that will benefit both contributors and users by providing more predictable and timely updates.

Release Details

• Release Date: 2025-05-22 15:54:19 UTC
• Commit: 0c7e4db
• Author: smithery-ai[bot]
• Branch(es): tag: 0.3.0

Changes

This release focuses solely on adding the necessary configuration file for the Smithery automation tool.

Added

• Smithery Configuration: A new configuration file (smithery.yaml) has been added to the repository root. This file contains the initial setup and instructions for Smithery to understand the project structure and define automated workflows, particularly related to the release process. This addition is a significant infrastructure improvement aimed at automating future development and release tasks.

Modified Files

• smithery.yaml (added)
  • Changes: 12 total
  • Added: 12 lines
  • Removed: 0 lines

Testing

Testing for this release primarily involved verifying the syntax and structure of the smithery.yaml file to ensure it is correctly formatted and parsable by the Smithery tool. This was done through static analysis and potentially by running the tool in a dry-run mode to confirm the configuration is valid. As this change is purely infrastructure-related and does not affect the application's functionality, no functional tests of the domain availability checker were required.

Instructions for Update

This release is part of the standard repository history. Users and contributors can obtain this change by pulling the latest version of the repository:

git pull origin main # or the relevant branch

No specific migration steps are required for users of the domain availability functionality itself, as this change is internal to the repository's development workflow.

Additional Notes

This release is purely an infrastructure update and does not contain any user-facing features, bug fixes, or breaking changes to the domain availability checking functionality. Its sole purpose is to integrate the Smithery automation tool configuration to facilitate future development and release processes.

Full Changelog: 0.2.0...0.3.0

v0.2.0

586b5e1: Enable Docker Containerization

Overview

This release introduces support for containerizing the application using Docker. The primary purpose of adding a Dockerfile is to provide a consistent and portable environment for building and running the application, simplifying deployment and setup across different environments. This change is crucial for improving the maintainability and scalability of the project. Users can now build a Docker image and run the application within a container, reducing dependency conflicts and streamlining the deployment process. The expected impact is a significant improvement in ease of deployment and environmental consistency for developers and users.

Release Details

• Release Date: 2025-05-22 15:54:18 UTC
• Commit: 586b5e1
• Author: smithery-ai[bot]
• Branch(es): tag: 0.2.0

Changes

This release focuses on enabling containerization of the application.

New Features

• Docker Support: Added a Dockerfile to define the build process for a Docker image. This allows the application to be packaged into a container, ensuring consistent execution across various environments and simplifying deployment workflows.

Modified Files

• Dockerfile (modified)
  • Changes: 3 total
  • Added: 2 lines
  • Removed: 1 lines

Testing

Testing for this release primarily involved manual verification of the Docker build process. The Dockerfile was used to build an image locally, and the resulting container was run to ensure the application starts and functions as expected within the containerized environment.

Instructions for Update

To utilize the new containerization feature, users can build the Docker image from the root of the repository using the provided Dockerfile.

1. Ensure Docker is installed and running.
2. Navigate to the project root directory in your terminal.
3. Build the Docker image: docker build -t your-image-name .
4. Run the application in a container: docker run your-image-name (adjust run command based on application requirements, e.g., port mapping).

Additional Notes

This release lays the groundwork for future container-based deployment strategies. While the Dockerfile is provided, specific orchestration configurations (like Docker Compose, Kubernetes manifests) are not included in this release but may be added in subsequent versions.

Full Changelog: 0.1.1...0.2.0

v0.1.1

867f31b: Streamlining Repository Structure

Overview

This release focuses on refining the repository structure by removing files that have become redundant due to the implementation of robust CI/CD pipelines and comprehensive documentation. The primary goal is to reduce repository complexity and improve maintainability without impacting the core functionality or user experience of the mcp-domain-availability library. This cleanup ensures that testing and examples are handled through more centralized and automated mechanisms, specifically GitHub Actions workflows and project documentation, leading to a cleaner and more efficient codebase for contributors.

Release Details

• Release Date: 2025-05-22 15:24:11 UTC
• Commit: 867f31b
• Author: imprvhub
• Branch(es): tag: 0.1.1

Changes

This release primarily involves refactoring the repository structure by removing outdated or redundant files.

Refactoring

• Removed Redundant Test and Example Files: Several files related to testing and examples have been removed as their functionality is now covered by existing CI/CD workflows and documentation.
  • test_mcp.py: Removed as its testing functionality is now fully covered by automated GitHub Actions workflows, ensuring continuous integration testing is robust and centralized.
  • test_install.sh: Removed as installation testing is now handled exclusively by the CI/CD pipeline, providing automated and consistent verification across different environments.
  • examples.py: Removed as basic usage examples are now provided and maintained within the project's official documentation, offering a more accessible and up-to-date resource for users.

Modified Files

• examples.py (removed)

  • Changes: 59 total
  • Added: 0 lines
  • Removed: 59 lines

• test_install.sh (removed)

  • Changes: 49 total
  • Added: 0 lines
  • Removed: 49 lines

• test_mcp.py (removed)

  • Changes: 25 total
  • Added: 0 lines
  • Removed: 25 lines

Testing

Testing for the library's core functionality and installation procedures is now exclusively performed through automated CI/CD pipelines configured via GitHub Actions workflows. These workflows execute comprehensive test suites upon every commit and pull request, ensuring code quality and stability are maintained. The removal of the specific test files (test_mcp.py, test_install.sh) does not diminish testing coverage but rather centralizes it within the automated pipeline.

Instructions for Update

This release involves internal repository cleanup and does not affect the published library package or require specific update steps for users consuming the library. Standard update procedures (e.g., pip install --upgrade mcp-domain-availability) apply for future library versions, but this specific commit primarily impacts the source repository structure.

Additional Notes

This release is a refactoring effort focused on repository maintainability. It does not introduce any new features, fix user-facing bugs, or include breaking changes for users of the mcp-domain-availability library. The changes are internal to the repository structure and primarily benefit contributors by simplifying the codebase. Users should refer to the project's official documentation for examples and usage guidelines.

Full Changelog: 0.1.0...0.1.1

v0.1.0

4003e64: fix(ci): update domain check test to handle async function

Overview

This release addresses a critical issue within the Continuous Integration (CI) test workflow. A recent change made the core domain availability checking function asynchronous. However, the existing test setup in the CI workflow was not updated to correctly handle this asynchronous function call, leading to a TypeError: Object of type coroutine is not JSON serializable during test execution.

The purpose of this release is to fix the CI test workflow by properly executing the asynchronous domain check function within the test environment. This ensures that the automated tests run successfully and reliably, maintaining the integrity and quality of the codebase. The expected impact is primarily on the development process, guaranteeing that code changes are validated correctly by the CI system. There is no direct impact on end-users of any library or application built upon this code, as the changes are confined to the testing infrastructure.

Release Details

• Release Date: 2025-05-22 15:13:10 UTC
• Commit: 4003e64
• Author: imprvhub
• Branch(es): tag: 0.1.0

Changes

Bug Fixes

• CI Test Workflow: Fixed a TypeError occurring in the CI test workflow (.github/workflows/test.yml). The issue arose because the test was attempting to directly call an asynchronous function (check_domain) without properly awaiting or running it in an event loop. The fix involves wrapping the call to the check_domain function within asyncio.run() to correctly execute the asynchronous code within the synchronous test context. This resolves the serialization error and allows the test to complete successfully.

Modified Files

• .github/workflows/test.yml (modified)
  • Changes: 17 total
  • Added: 11 lines
  • Removed: 6 lines

Testing

Testing for this release primarily involved running the updated CI workflow. The fix was verified by confirming that the TypeError was resolved and the test suite completed successfully without errors in the automated CI environment.