> ## Documentation Index
> Fetch the complete documentation index at: https://docs.getmcpulse.com/llms.txt
> Use this file to discover all available pages before exploring further.

# List Alerts

> Every alert rule on this MCP, with the sentence it reads as, when it last fired and how often.

A rule narrows by tool and by client — the same two dimensions `tool_hours` is keyed by — so it can express any scope the dashboard filter can and nothing more. That is where the value is: "first-call on `search_orders`, for Cursor, below 60%" fires on a real 23% where a server-wide rule at 70% stays silent, because the average across clients is 80%.



## OpenAPI

````yaml https://api.getmcpulse.com/docs/openapi.json get /v1/mcps/{id}/alerts
openapi: 3.1.0
info:
  title: MCPulse API
  version: 1.0.0
  description: >-
    Analytics for MCP servers.


    The API is the product — the dashboard is one client and an MCP server will
    be another. Every number here is computed server-side so that both get the
    same answer.


    **Two kinds of auth.** Ingest uses an MCP API key (`mp_live_…`). Everything
    else uses a Supabase access token from the browser session.
servers:
  - url: https://mcpulse-production.up.railway.app
    description: MCPulse API
security: []
tags:
  - name: ingest
    description: What the customer's server sends
  - name: mcps
    description: MCPs and ownership
  - name: metrics
    description: Everything the dashboard reads
  - name: keys
    description: Ingest API keys
  - name: account
    description: Account, team and usage
paths:
  /v1/mcps/{id}/alerts:
    get:
      tags:
        - alerts
      summary: List Alerts
      description: >-
        Every alert rule on this MCP, with the sentence it reads as, when it
        last fired and how often.


        A rule narrows by tool and by client — the same two dimensions
        `tool_hours` is keyed by — so it can express any scope the dashboard
        filter can and nothing more. That is where the value is: "first-call on
        `search_orders`, for Cursor, below 60%" fires on a real 23% where a
        server-wide rule at 70% stays silent, because the average across clients
        is 80%.
      parameters:
        - schema:
            type: string
            format: uuid
          required: true
          name: id
          in: path
      responses:
        '200':
          description: OK
          content:
            application/json:
              schema:
                nullable: true
        '401':
          description: Invalid or missing token
        '404':
          description: Not found, or not yours

````