Skip to main content
Glama
hesreallyhim

IsItDown MCP Server

get_website_status

Check if a website is currently accessible by verifying its operational status through a domain request. This tool determines whether a site is up or down for users.

Instructions

Check the status of a website.

This function takes a root domain as input and checks whether the website is up or down
by making a request to isitdownrightnow.com

Args:
    root_domain (str): The root domain of the website to check.

Returns:
    str: A message indicating whether the website is up or down, or if the status could not be determined.

Input Schema

TableJSON Schema
NameRequiredDescriptionDefault
root_domainYes

Implementation Reference

  • The main handler function for the 'get_website_status' tool. It uses httpx to fetch status from isitdownrightnow.com, parses with BeautifulSoup, determines up/down status, extracts last down time using helpers, and returns a status message.
    @mcp.tool()
    async def get_website_status(root_domain: str) -> str:
        """
        Check the status of a website.
    
        This function takes a root domain as input and checks whether the website is up or down
        by making a request to isitdownrightnow.com
    
        Args:
            root_domain (str): The root domain of the website to check.
    
        Returns:
            str: A message indicating whether the website is up or down, or if the status could not be determined.
        """
        last_down_time = "Could not determine information about the last down time."
        try:
            async with httpx.AsyncClient() as client:
                response = await client.get(
                    f"{ISITDOWN_BASE_URL}{root_domain}",
                    headers={"User-Agent": USER_AGENT},
                    timeout=10.0,
                )
                response.raise_for_status()
        except httpx.HTTPError:
            return "Could not determine the status of the website."
    
        soup = bs(response.text, "html.parser")
        is_up = soup.find("span", class_="upicon")
        is_down = soup.find("span", class_="downicon")
        tabletrsimple_divs = soup.find_all("div", class_="tabletrsimple")
    
        if len(tabletrsimple_divs) >= 2:
            last_down_row = tabletrsimple_divs[
                1
            ]  # NOTE: Brittle - makes assumptions about HTML structure
            if isinstance(last_down_row, Tag):
                last_down_time = get_last_down(last_down_row)
    
        return get_response_msg(bool(is_down), bool(is_up), last_down_time)
  • Helper function to parse and extract the last down time from the 'isitdownrightnow.com' HTML table row.
    def get_last_down(last_down_row: Tag) -> str:
        """
        Extract the last down time from the HTML row.
    
        Args:
            last_down_row (bs4.Tag): The HTML row containing the last checked time.
    
        Returns:
            str: The last time the server found the website to be down.
        """
        last_down_time = last_down_row.find_next("span", class_="tab")
        if last_down_time is None:
            return "Last down time not found."
        else:
            return f"Last down time is: {last_down_time.text.strip()}"
  • Helper function to format the final response message based on the detected status (up/down) and last down time.
    def get_response_msg(is_down: bool, is_up: bool, last_down_time: str) -> str:
        """
        Format the response message based on website status.
    
        Args:
            is_down (bool): Whether the website is down.
            is_up (bool): Whether the website is up.
            last_down_time (str): The last time the website was down.
    
        Returns:
            str: Formatted status message.
        """
        if is_down:
            return f"The website is down. {last_down_time}"
        elif is_up:
            return f"The website is up. {last_down_time}"
        else:
            return "Could not determine the status of the website."
Behavior2/5

Does the description disclose side effects, auth requirements, rate limits, or destructive behavior?

No annotations are provided, so the description carries the full burden. It mentions making a request to an external service but doesn't disclose behavioral traits like rate limits, network dependencies, error handling, or what 'could not be determined' means. The description is minimal and lacks operational context.

Agents need to know what a tool does to the world before calling it. Descriptions should go beyond structured annotations to explain consequences.

Conciseness4/5

Is the description appropriately sized, front-loaded, and free of redundancy?

The description is appropriately sized and front-loaded, starting with the core purpose. The Args and Returns sections are structured but could be more integrated; overall, it's efficient with minimal waste.

Shorter descriptions cost fewer tokens and are easier for agents to parse. Every sentence should earn its place.

Completeness2/5

Given the tool's complexity, does the description cover enough for an agent to succeed on first attempt?

Given no annotations, 0% schema coverage, and no output schema, the description is incomplete. It lacks details on return format, error conditions, performance, or dependencies, making it inadequate for a tool that interacts with an external service.

Complex tools with many parameters or behaviors need more documentation. Simple tools need less. This dimension scales expectations accordingly.

Parameters3/5

Does the description clarify parameter syntax, constraints, interactions, or defaults beyond what the schema provides?

Schema description coverage is 0%, so the description must compensate. It explains that 'root_domain' is the root domain of the website to check, adding basic meaning. However, it doesn't clarify format (e.g., with or without protocol) or provide examples, leaving gaps in parameter understanding.

Input schemas describe structure but not intent. Descriptions should explain non-obvious parameter relationships and valid value ranges.

Purpose4/5

Does the description clearly state what the tool does and how it differs from similar tools?

The description clearly states the tool's purpose: 'Check the status of a website' with the specific action of making a request to isitdownrightnow.com. It distinguishes the tool by specifying the external service used, though there are no sibling tools to differentiate from.

Agents choose between tools based on descriptions. A clear purpose with a specific verb and resource helps agents select the right tool.

Usage Guidelines2/5

Does the description explain when to use this tool, when not to, or what alternatives exist?

The description provides no guidance on when to use this tool versus alternatives, prerequisites, or limitations. It simply states what the tool does without context about appropriate scenarios or constraints.

Agents often have multiple tools that could apply. Explicit usage guidance like "use X instead of Y when Z" prevents misuse.

Install Server

Other Tools

Latest Blog Posts

MCP directory API

We provide all the information about MCP servers via our MCP API.

curl -X GET 'https://glama.ai/api/mcp/v1/servers/hesreallyhim/mcp-server-isitdown'

If you have feedback or need assistance with the MCP directory API, please join our Discord server