🌐 AI-Enabled Uptime Oversight Nexus

This service bridges your established Uptime Agent infrastructure (reference: uptime-agent.io) with advanced digital assistants, such as Claude, by leveraging the Model Context Protocol (MCP). This integration transforms raw monitoring telemetry into actionable intelligence accessible via conversational commands.

Key Operational Capabilities

• Instantaneous Status Polling: Authorizes cognitive systems to query the current operational posture of monitored assets.
• Intelligent Alert Triage: Facilitates review and contextual analysis of system disruptions through dialogue.
• Declarative Configuration: Allows users to provision novel surveillance targets using plainspoken directives.
• Robust Interconnection: Implements hardened security measures to safeguard the exchange between monitoring targets and the AI ecosystem.

System Context: Uptime Agent

Uptime Agent is the foundational tool for tracking the availability of web assets and API services, generating alerts upon service degradation. This dedicated MCP intermediary extends the platform's utility, permitting direct, language-based interaction with your infrastructure monitoring layer.

⚙️ Deployment Guide

Prerequisites

• Execution environment supporting Node.js version 18 or newer.
• Valid credentials for the Uptime Agent service.
• The necessary Uptime Agent API authentication token.

To acquire your authentication credential: 1. Access your Uptime Agent Control Panel. 2. Navigate to the 'Account Management' then 'API Access Keys' section. 3. Generate a new access token, ensuring requisite permissions are granted. 4. Securely retain the generated key for server configuration.

Method 1: Expedited Installation (NPM)

The recommended pathway involves this single orchestration command:

npx uptime-agent-mcp setup

This command automates: - Installation of the necessary MCP intermediary components. - Optimization for interaction with Claude Desktop environments. - Interactive prompting for the required Uptime Agent API credential. - Full configuration setup.

Method 2: Via Smithery.ai Distribution Channel

Utilize the Smithery ecosystem for managed deployment:

1. Establish an account at smithery.ai.
2. Obtain your unique personal authorization key from your Smithery profile.
3. Execute the following CLI instruction:

npx -y @smithery/cli@latest install @AVIMBU/uptime_agent_mcp --client claude --key <personal_key>

Substitute <personal_key> with your actual Smithery secret.

Method 3: Manual Source Integration (Advanced Users)

For environments requiring granular control over the build process:

# Obtain the source repository
git clone https://github.com/AVIMBU/uptime_agent_mcp.git
cd uptime_agent_mcp

# Install dependencies
npm install

# Compile source code
npm run build

Configure the runtime environment by creating a .env file in the root directory:

UPTIME_API_KEY=your-api-key-here
PORT=3000  # Optional: Specifies the listening port

Initiate the service daemon:

npm start
# Or execute the compiled artifact directly
node dist/index.js

🧠 AI Assistant Configuration

Integration with Claude Desktop

Once the service is operational, automatic configuration is applied for Claude Desktop environments. If manual setup was chosen, integrate the server definition into your claude_desktop_config.json:

{
  "mcpServers": {
    "uptime-agent": {
      "command": "npx",
      "args": [
        "-y",
        "uptime-agent-mcp"
      ],
      "env": {
        "UPTIME_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Alternatively, use a containerized approach via Docker configuration:

{
  "mcpServers": {
    "uptime-agent": {
      "command": "docker",
      "args": [
        "run",
        "-i",
        "--rm",
        "-e",
        "UPTIME_API_KEY",
        "uptime-agent-mcp"
      ],
      "env": {
        "UPTIME_API_KEY": "<YOUR_API_KEY>"
      }
    }
  }
}

Sample Cognitive Interactions

Querying Current Monitor Inventory:

"AI, enumerate all currently active probes reporting system availability."

Provisioning New Surveillance:

"Establish continuous health validation for the endpoint located at https://api.mycompany.com/v2/health."

Post-Mortem Analysis Request:

"Summarize all recorded service interruption events concerning the primary transaction servers during the preceding seven-day cycle, quantifying mean time to recovery."

🛠️ Exposed Functionality

Monitoring Target Operations

Function Name	Purpose	Required Arguments	Optional Arguments
listMonitors	Fetch a comprehensive manifest of all configured surveillance assets.	None	N/A
getMonitor	Retrieve granular telemetry for a specified tracking ID.	id (Target ID)	N/A
createMonitor	Instantiate a new monitoring target definition.	name, url, tracking_type (e.g., http, ping), check_frequency (in seconds)	N/A

Service Disruption Record Management

Function Name	Purpose	Required Arguments	Optional Arguments
listIncidents	Present the chronological log of all detected outages.	None	N/A
getIncident	Extract specific data points related to an identified failure event.	id (Incident ID)	N/A
listIncidentsByMonitor	Filter the outage log by a specific monitored asset.	monitor_id	N/A

Public Visibility Configuration

Function Name	Purpose	Required Arguments	Optional Arguments
createAnonymousTracking	Set up public status view without requiring user authentication.	url	name (Tracking Label)

Pending Feature: Slack Interfacing

Function Name	Purpose	Required Arguments	Optional Arguments
slack_get_users	Retrieve the roster of users from the linked collaboration workspace.	None	limit, cursor (for pagination)
slack_post_message	Inject a formatted message into a designated communication channel.	channel_id, text (Message Payload)	N/A

🐳 Containerization Blueprint

Docker images are available for streamlined deployment:

# Construct the local container image
docker build -t uptime-agent-mcp .

# Launch the service instance, mapping port 3000 and providing the secret key
docker run -p 3000:3000 -e UPTIME_API_KEY=your-api-key uptime-agent-mcp

📞 Support Channels

For inquiries or technical assistance:

• Submit a formal report via GitHub Issues
• Direct contact through the developer portal: AVIMBU Solutions

📄 Licensing

This software is distributed under the permissive MIT License terms. Consult the LICENSE file for full stipulations.

---

Crafted with dedication by AVIMBU