Skip to main content
Glama
deenesjakoruzh
hesreallyhim

IsItDown MCP Server

by hesreallyhim
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

mcp 服务器关闭

MCP 服务器通过查询www.isitdownrightnow.com检查网站当前是否已关闭。

铁匠徽章

概述

该 MCP 服务器提供了一个简单的工具来检查网站是否正在经历停机，并可以提供有关最近停机事件的一些信息。

Related MCP server: stillonline-mcp

工具

实施了以下工具：

  • get_website_status ：检查网站当前是否关闭。

    • Input ： root_domain （字符串）：要检查的网站的根域（例如“example.com”）

    • Output ：一条字符串消息，指示网站是否正常运行，以及最后记录的停机信息

安装

通过 Smithery 安装

要通过Smithery自动为 Claude Desktop 安装 IsItDown 服务器：

npx -y @smithery/cli install @hesreallyhim/mcp-server-isitdown --client claude

注意：此软件包目前尚未发布到公共注册表。仅可从源代码安装。

来自源

# Clone the repository 
git clone https://github.com/yourusername/mcp-server-isitdown.git
cd mcp-server-isitdown

# Using uv (recommended)
uv pip install -e .

# Using pip
pip install -e .

Claude 桌面配置

将此配置添加到您的claude_desktop_config.json文件中：

"isitdown": {
  "command": "/path/to/uv",
  "args": [
    "--directory",
    "/path/to/cloned/repo/src",
    "run",
    "mcp_server_isitdown"
  ]
}

用法

作为独立的 MCP 服务器运行

# Using the installed script
mcp-server-isitdown

# Using the Python module
python -m mcp_server_isitdown

使用 Claude for Dekstop 的示例：

  • “维基百科现在瘫痪了吗？”

  • “Reddit 上次宕机是什么时候？”

用作图书馆

from mcp_server_isitdown.server import get_website_status

# Check if a website is down (async function)
async def check_website():
    result = await get_website_status("example.com")
    print(result)  # Prints status message with up/down status

发展

# Type checking
uvx mypy .

# Run all pre-commit hooks
uv pre-commit run --all-files

# Install in development mode
uv pip install -e ".[dev]"

# Run the Inspector
mcp dev src/mcp_server_isitdown/server.py

建造

# Build the package
uv build

# Install the built package
uv pip install dist/mcp_isitdown_service-*.whl

执照

麻省理工学院

Available Tools

1 tool
get_website_statusC
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.
ParametersJSON Schema
NameRequiredDescriptionDefault
root_domainYes

TDQS

C2.9/5.0
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.

Tool Schema Changelog

Recent tool additions, removals, and schema changes observed during successful MCP inspections.

  1. 1 tool updatev1.0.0
    • Addedget_website_status
Deploy Server
One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

TDQS

B3.1/5.0

Scored across 1 tool

Disambiguation5/5

With only one tool, there is no possibility of ambiguity or overlap between tools. The single tool 'get_website_status' has a clear, distinct purpose that cannot be confused with any other tool in this set.

Naming Consistency5/5

The naming follows a consistent verb_noun pattern ('get_website_status'), and with only one tool, there is no inconsistency to evaluate. The naming convention is clear and appropriate for the tool's function.

Tool Count2/5

A single tool is too few for most server purposes, as it limits functionality and can lead to dead ends. For a website status checking server, additional tools like checking multiple sites, monitoring history, or getting detailed status information would be expected to provide a more complete surface.

Completeness2/5

The tool set is severely incomplete for the domain of website status checking. While 'get_website_status' covers a basic check, there are significant gaps such as batch checking, historical data retrieval, or status monitoring over time, which agents might need for more complex workflows.

Maintenance

ActivityInactive
ResponsivenessNo issues

Resources

Related MCP Connectors

Related MCP Servers

  • downdetector-mcp

    domdomegg
    A
    license
    A
    quality
    B
    maintenance
    This server enables checking real-time service status and outage information from Downdetector for various services and regions.
    1
    27 npm
    2
    MIT

  • stillonline-mcp

    shenwell
    A
    license
    A
    quality
    D
    maintenance
    MCP server for StillOnline uptime monitoring, enabling management of projects, checks, incidents, and public status pages through natural language.
    10
    26 npm
    1
    MIT

  • @mnicole-dev/updown-mcp-server

    mnicole-dev
    A
    license
    A
    quality
    D
    maintenance
    An MCP server for Updown.io that enables managing website monitoring checks, viewing downtimes and metrics, configuring alert recipients, and controlling status pages through natural language.
    15
    4 npm
    MIT

Appeared in Searches