Servidor MCP de Stackpulse

Qué servidores del registro oficial de MCP son de Stackpulse, si responden y qué ofrecen. Un programa comprobó cada dato; nada está copiado de la página del producto.

leído el 2026-10-18

← Volver a Stackpulse

De quién es el servidor

Nombre en el registroapp.stackpulse/mcpverificado en el registro MCP

El nombre en el registro está bajo stackpulse.app. El registro solo permite usar ese espacio de nombres a quien demuestra control del dominio por DNS o HTTP.

Cuando le preguntamoscomprobado el 2026-10-18

Estadorespondecomprobado el 2026-10-18
Herramientas16
El servidor se llamastackpulse
Versión del servidor1.0.0
Versión del protocolo2025-06-18

El 2026-10-18 el servidor respondió a initialize y tools/list sin iniciar sesión. Primera respuesta en 187 ms.

Herramientas que ofrece16 herramientas · leído el 2026-10-18

search_services
Finds services in the catalog of 9,700+ status pages by name, with their status now. Use it to find a service’s slug.
get_service
One service’s status from its official status page: what’s wrong, the components with a problem, 90 days of history and recent incidents.
list_outages
Services reporting a problem right now, the newest first: the 25 best-known, unless all is true or a limit is given.
list_dashboards
The account’s dashboards (the ones this connection can see), with how many services and URL monitors each has and its worst status now.
get_stack_status
What’s going on now on a dashboard: a summary, then every service and URL monitor with a problem, with when the problem began and when its current status did. A URL monitor that’s down lists what started around then. Without a dashboard…
get_incident_history
Incidents on a dashboard in a window: the ones that started in it (with what else started at the same time) and the ones already going on. As far back as the plan’s history goes.
get_monitor
One of the account’s URL monitors: its status, its uptime over the last 30 days (or since it started) with the failed checks apart, response times, its certificate and its latest checks.
get_reliability
How reliable a dashboard’s services and URL monitors were over 7, 30 or 90 days: the least reliable first, with the share of time without a reported problem (minor issues count, so one long minor issue makes it low), time in each…
create_dashboard
Makes a dashboard with a name and, optionally, services by slug (search_services finds them), within the plan’s dashboards and services. Answers with its address.
rename_dashboard
Renames a dashboard. Its status page shares the name.
add_services
Adds services to a dashboard by slug (search_services finds them), within the plan’s limit.
remove_services
Takes services off a dashboard. Their history stays; adding one back shows it again.
add_monitor
Watches a website or API endpoint on a dashboard: checks the address once first, and refuses what the app refuses (private addresses, other ports, past the plan). Without a name, the page’s title names it. Headers and request bodies stay…
check_monitor
Checks one of the account’s URL monitors now, as Check now does in the app, and says what it got.
pause_monitor
Pauses a URL monitor, e.g. during a deploy: an open incident ends, and no alerts go out until it’s resumed.
resume_monitor
Resumes a paused URL monitor: it’s checked at once and starts fresh.

Cómo conectar

Añade el servidor a la configuración de tu cliente MCP. Claude Desktop, Cursor y la mayoría de los demás clientes leen este formato:

{
  "mcpServers": {
    "stackpulse": {
      "type": "http",
      "url": "https://stackpulse.app/mcp"
    }
  }
}

Cada línea es algo que un programa encontró al buscar: la entrada del registro, la respuesta del propio servidor, una especificación que se puede leer. Si falta una línea, es que no la encontramos, no que no exista.