Labsco
MCP SERVER

Pulsetic MCP Server

by designmodo

Answer whether the site was down last night, from Pulsetic's own monitor history.

Observability, Monitoring & Incident Response
Summary
Uptime answers where the question gets asked.

When someone asks whether the site was down at 3am, the answer is a monitor's event history — this puts that and the statistics around it in the window the conversation is already in.

What it is

A remote MCP server for Pulsetic uptime monitoring, at https://api.pulsetic.com/mcp over Streamable HTTP. Its tools list the monitors on the account, fetch one in detail, and read that monitor's events and statistics.

What you get
  • Every monitor on the account, listed
  • One monitor fetched in detail
  • A monitor's events — the up and down history behind the question
  • A monitor's statistics
Requirements

A Pulsetic account on a plan with API access, which is Business or Enterprise, and an API key from Settings then API. Claude Code, Cursor and Windsurf connect straight to https://api.pulsetic.com/mcp with an Authorization header; Claude Desktop bridges to it with npx mcp-remote; ChatGPT connects over OAuth with Developer Mode enabled.

Setup effort

One command plus a key — npx -y mcp-remote https://api.pulsetic.com/mcp --header Authorization: Bearer YOUR_API_KEY, then supply credentials