mcp-server-isitdown

Created By
MCP-Mirrora year ago
Mirror of
Overview

what is mcp-server-isitdown?

The mcp-server-isitdown is a server that checks if a website is currently down by querying www.isitdownrightnow.com, providing users with real-time website status updates.

how to use mcp-server-isitdown?

To use the mcp-server-isitdown, you can run it as a standalone server or use it as a library in your Python projects. Simply input the root domain of the website you want to check, and it will return the current status along with any recent downtime information.

key features of mcp-server-isitdown?

  • Checks if a website is currently down or up.
  • Provides information about recent downtime events.
  • Can be used as a standalone server or integrated into other applications.

use cases of mcp-server-isitdown?

  1. Monitoring the uptime of critical business websites.
  2. Integrating into applications that require website status checks.
  3. Providing alerts for website downtime to users or administrators.

FAQ from mcp-server-isitdown?

  • How do I install mcp-server-isitdown?

You can install it from source by cloning the repository and using pip to install it.

  • Can I use it as a library?

Yes! You can import the get_website_status function and use it in your Python code.

  • Is there any support for configuration?

Yes, you can configure it for use with Claude Desktop by adding specific commands to your configuration file.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
MCP-Mirror
Star
0
Language
Python
License
MIT license

Recommend Servers

View All
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago