🚀 Uptime Agent MCP Server

Created By
AVIMBUa year ago
Connect your Uptime Agent monitoring system directly to AI assistants like Claude through the Model Context Protocol (MCP).
Overview

What is Uptime Agent MCP?

Uptime Agent MCP is a server that connects your Uptime Agent monitoring system directly to AI assistants like Claude through the Model Context Protocol (MCP). It enhances the monitoring experience by allowing users to interact with their monitoring systems using natural language.

How to use Uptime Agent MCP?

To use Uptime Agent MCP, you need to install it on your server, set up your Uptime Agent API key, and configure it to connect with AI assistants. You can interact with the system through voice or text commands to manage your monitoring endpoints.

Key features of Uptime Agent MCP?

  • Real-time monitoring access for uptime status checks
  • Incident management through natural conversation
  • Easy setup of new monitoring endpoints
  • Secure integration with enterprise-grade security

Use cases of Uptime Agent MCP?

  1. Checking the status of active uptime monitors.
  2. Creating new monitors for API endpoints.
  3. Analyzing downtime incidents through conversational queries.

FAQ from Uptime Agent MCP?

  • Can I use Uptime Agent MCP without an Uptime Agent account?

No, you need an active Uptime Agent account to use this service.

  • Is there a cost associated with using Uptime Agent MCP?

The Uptime Agent service may have associated costs depending on your usage and plan.

  • What programming language is Uptime Agent MCP built with?

Uptime Agent MCP is built with TypeScript.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
AVIMBU
Star
0
Language
JavaScript
License
-
Category
monitoring

Recommend Servers

View All
Payai X402 Tools

6 hours ago
AI Work Market — USDC settlement rails for AI labor on Base Mainnet)
@Dario (DME)

AI Work Market is a USDC escrow protocol on Base Mainnet, designed for autonomous AI agents to find work, post jobs, and settle payments without humans in the loop. This MCP server exposes 10 tools: **Escrow lifecycle** - `create_intent_quote` — get calldata + gas estimate for funding a new escrow intent - `submit_proof_quote` — get calldata for the seller to submit a proof URI - `release_funds_quote` — get calldata for the buyer to release payment (or claim/refund) **x402 single-call binding** - `x402_consume` — replaces the 5-step x402 flow with one HMAC-signed POST that returns a delivery URL **Onboarding & discovery** - `agent_onboard` — generate a signed agent card with marketplace attestation - `agent_search` — tf-idf search over the live agent catalog - `agent_reputation` — server-side reputation from on-chain Released/Refunded/Disputed events **Live state** - `system_status` — live on-chain state (nextIntentId, accumulatedFees, contract balance, owner) - `escrow_rules` — contract semantics, lifecycle, call guides, failure modes - `events_subscribe` — SSE stream of new on-chain intent events All endpoints are serverless (Vercel) and return their schema on GET. No browser, no wallet UI required for an agent to integrate. The protocol takes a 1% commission on every settlement; the rest goes to the seller. The full AgentCard is at `/.well-known/agent-card.json` (A2A-compatible). The OpenAPI 3.0.3 spec is at `/.well-known/openapi.json` with `components.securitySchemes` (none, hmacX402). `robots.txt` allows GPTBot, ClaudeBot, anthropic-ai, PerplexityBot, Google-Extended, Applebot-Extended, CCBot, Amazonbot.

a day ago