list_monitorsLABSCO 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. The README lists 17 tools: they read monitors, their events, uptime statistics and downtime, and they also create, edit, pause and delete monitors, post and resolve status-page incidents, and schedule maintenance.
What you get
- Every monitor on the account, listed
- One monitor fetched in detail, and monitors created, edited, paused, resumed or deleted
- A monitor's events — the up and down history behind the question
- A monitor's uptime statistics and total downtime for a period
- Status-page incidents opened, updated and resolved, and maintenance windows scheduled or deleted
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
Paste a URL with a key — add the endpoint to your client
USE CASES
01
Answering whether the site was actually down
Find the monitor, then read its event history for the window in question.
02
Checking what is being monitored at all
The monitor list, plus the detail on any one of them, before you trust an all-clear.
03
Reporting uptime for a period
Statistics for the monitor, rather than counting incidents by hand.
04
Investigating a monitor that keeps flapping
Events and statistics side by side show whether it is the site or the check.
17 tools
Listed in project docs. Your client may show a different list.
get_monitorget_monitor_statsget_monitor_eventsget_monitor_downtimecreate_monitorupdate_monitordelete_monitorpause_monitorresume_monitorlist_status_pageslist_incidentscreate_incidentupdate_incidentresolve_incidentcreate_maintenancedelete_maintenanceBEFORE YOU INSTALL
What to know first
Tools you get
17 tools named in the project's documentation.
Requires
- A Pulsetic account on a plan with API access (Business or Enterprise)
- A Pulsetic API key from Settings → API
- npx on PATH, for the Claude Desktop setup only (it bridges with mcp-remote)
INSTALLATION
Connect your client
Add the endpoint to your client.
Server setup
ENDPOINT URL
https://api.pulsetic.com/mcpMCP Clients
Claude Desktop
CLAUDE DESKTOP · JSON
{
"mcpServers": {
"pulsetic": {
"command": "npx",
"args": [
"-y",
"mcp-remote",
"https://api.pulsetic.com/mcp",
"--header",
"Authorization: Bearer <YOUR_API_KEY>"
]
}
}
}Claude Code
CLAUDE CODE · JSON
{
"mcpServers": {
"pulsetic": {
"type": "http",
"url": "https://api.pulsetic.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}Cursor
Settings
MCP Servers
Add Server — Type: streamableHttp; URL: https://api.pulsetic.com/mcp; Headers: Authorization: Bearer <YOUR_API_KEY>
Windsurf
WINDSURF · JSON
{
"mcpServers": {
"pulsetic": {
"serverUrl": "https://api.pulsetic.com/mcp",
"headers": {
"Authorization": "Bearer <YOUR_API_KEY>"
}
}
}
}The README points Windsurf at its Cursor settings: this endpoint over Streamable HTTP, with your Pulsetic API key (Settings → API) in the Authorization header.
ChatGPT
Enabled apps → Advanced settings
Developer mode, then Create app with MCP Server URL https://api.pulsetic.com/mcp and Authentication: OAuth (endpoints auto-discovered: /mcp/oauth/authorize, /mcp/oauth/token, /mcp/oauth/register)
