mcp-service-url-availability-probe

This infrastructure monitoring component queries the external service located at www.isitdownrightnow.com to gauge the real-time availability of a given Uniform Resource Locator (URL).

Core Functionality

This MCP service furnishes a straightforward mechanism to ascertain if a target website is experiencing an outage, alongside providing retrospective data concerning prior service disruptions.

Exposed Endpoints

The following programmatic interfaces are available:

• verify_site_health: Assesses the current operational state (up or down) of a web resource.
• Parameters: target_hostname (text): The primary domain name of the site under scrutiny (e.g., "google.com").
• Returns: A textual notification detailing the immediate up/down status, incorporating the most recent recorded downtime incident.

Deployment Instructions

Integration via Smithery

To integrate the URL Availability Probe into Claude Desktop automatically using Smithery:

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

Caveat: This package is presently unavailable via public registries. Installation is restricted to deployment directly from the source code.

From Source Repository

bash

Repository cloning

git clone https://github.com/yourusername/mcp-server-isitdown.git cd mcp-server-isitdown

Recommended installation method using uv

uv pip install -e .

Standard installation using pip

pip install -e .

Configuration for Claude Desktop Environment

Integrate the following block into your claude_desktop_config.json file:

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

Execution Examples

Running as a Standalone Service

bash

Invoking via the installed executable

mcp-server-isitdown

Invoking via the Python module interface

python -m mcp_server_isitdown

Example Prompts for Claude Desktop:

• "Is google.com presently inaccessible?"
• "Report on the last known service interruption for twitter.com."

Utilizing as a Programming Library

python from mcp_server_isitdown.server import get_website_status as verify_site_health

Probe a website's availability (asynchronous operation)

async def examine_host_status(): status_report = await verify_site_health("example.com") print(status_report) # Output will be the status message detailing up/down state

Development Workflow

bash

Static analysis and type checking

uvx mypy .

Executing all pre-commit validation routines

uv pre-commit run --all-files

Installing dependencies for development context

uv pip install -e ".[dev]"

Launching the Inspector utility

mcp dev src/mcp_server_isitdown/server.py

Packaging

bash

Building the distributable package artifact

uv build

Installing the freshly built artifact

uv pip install dist/mcp_isitdown_service-*.whl

Licensing

MIT

WIKIPEDIA: XMLHttpRequest (XHR) is an API in the form of a JavaScript object whose methods transmit HTTP requests from a web browser to a web server. The methods allow a browser-based application to send requests to the server after page loading is complete, and receive information back. XMLHttpRequest is a component of Ajax programming. Prior to Ajax, hyperlinks and form submissions were the primary mechanisms for interacting with the server, often replacing the current page with another one.

== History == The concept behind XMLHttpRequest was conceived in 2000 by the developers of Microsoft Outlook. The concept was then implemented within the Internet Explorer 5 browser (1999). However, the original syntax did not use the XMLHttpRequest identifier. Instead, the developers used the identifiers ActiveXObject("Msxml2.XMLHTTP") and ActiveXObject("Microsoft.XMLHTTP"). As of Internet Explorer 7 (2006), all browsers support the XMLHttpRequest identifier. The XMLHttpRequest identifier is now the de facto standard in all the major browsers, including Mozilla's Gecko layout engine (2002), Safari 1.2 (2004) and Opera 8.0 (2005).

=== Standards === The World Wide Web Consortium (W3C) published a Working Draft specification for the XMLHttpRequest object on April 5, 2006. On February 25, 2008, the W3C published the Working Draft Level 2 specification. Level 2 added methods to monitor event progress, allow cross-site requests, and handle byte streams. At the end of 2011, the Level 2 specification was absorbed into the original specification. At the end of 2012, the WHATWG took over development and maintains a living document using Web IDL.

== Usage == Generally, sending a request with XMLHttpRequest has several programming steps.

Create an XMLHttpRequest object by calling a constructor: Call the "open" method to specify the request type, identify the relevant resource, and select synchronous or asynchronous operation: For an asynchronous request, set a listener that will be notified when the request's state changes: Initiate the request by calling the "send" method: Respond to state changes in the event listener. If the server sends response data, by default it is captured in the "responseText" property. When the object stops processing the response, it changes to state 4, the "done" state. Aside from these general steps, XMLHttpRequest has many options to control how the request is sent and how the response is processed. Custom header fields can be added to the request to indicate how the server should fulfill it, and data can be uploaded to the server by providing it in the "send" call. The response can be parsed from the JSON format into a readily usable JavaScript object, or processed gradually as it arrives rather than waiting for the entire text. The request can be aborted prematurely or set to fail if not completed in a specified amount of time.

== Cross-domain requests ==

In the early development of the World Wide Web, it was found possible to brea