Pulsetic Mcp Server

Created By
Pulsetic3 months ago
The Pulsetic MCP Server connects Pulsetic monitoring with AI agents and MCP-compatible tools, enabling direct access to uptime data, cron monitoring results, incident management workflows, and status page information through the Model Context Protocol (MCP). It allows teams to securely expose operational monitoring data in a structured format, making it easy to build AI-driven automation, monitoring assistants, and intelligent operational workflows without custom middleware. Core Capabilities Uptime Monitoring Access real-time and historical uptime data through AI systems. Query monitor health, availability metrics, and performance status directly from AI agents or automation workflows. Cron Monitoring Track scheduled jobs and background tasks with cron monitoring insights. Detect missed executions, delays, or failures and integrate alerts into AI-powered operational processes. Incident Management Retrieve incident history, status updates, and timelines programmatically. Automate incident analysis, reporting, and response workflows using AI tools. Status Pages Integrate public or internal status page data into AI environments. Automatically surface service status, ongoing incidents, and maintenance updates for improved transparency and communication. Use Cases AI-powered uptime and reliability monitoring Automated incident response and reporting Intelligent cron job supervision Status page automation and operational visibility Internal AI assistants for DevOps and SRE teams The Pulsetic MCP Server brings uptime monitoring and operational intelligence directly into modern AI ecosystems, enabling smarter automation, faster troubleshooting, and improved service reliability.
Overview

Pulsetic MCP Server Connect AI assistants to your Pulsetic monitoring platform using the Model Context Protocol (MCP).

Project Info
Created At
3 months ago
Updated At
3 months ago
Author Name
Pulsetic
Star
-
Language
-
License
-
Category

Recommend Servers

View All
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.

8 hours ago