MCP Server Monitoring

Add your own MCP server and get alerts when it breaks.

AlertsDown can monitor MCP endpoints your agents depend on. Add your own or vendor MCP server, define the tools, resources, prompts, and safe probe that must keep working, then receive alerts through your existing downtime notification channels when the MCP contract changes or fails.

Create MCP Monitor View Hosted MCP

What connects: AlertsDown connects to your MCP endpoint on a schedule.
What fails the monitor: Initialization errors, missing expected capabilities, or failed safe probes.
Alert channels: Email, SMS, Telegram, WhatsApp, webhook, and the channels available on your plan.

The difference

Hosted MCP is access. MCP alerts are monitoring.

The AlertsDown hosted MCP page is for connecting AI clients to AlertsDown. Your assistant uses that endpoint to create monitors, inspect status, and work with uptime data.

This page is the other direction: AlertsDown connects to MCP servers you add. It verifies the server still speaks MCP, still advertises the capabilities your agents need, and can still answer one safe read-only tool call if you choose to configure a probe.

What the monitor checks

Monitors verify the MCP contract agents depend on

Initialize the MCP server

AlertsDown connects to the endpoint with the selected transport and verifies that the server can complete the MCP initialization flow.

Discover capabilities

The monitor reads the tools, resources, and prompts the server advertises so missing capabilities are caught before agents rely on them.

Match expected names

Add exact tool, resource, or prompt names. AlertsDown alerts when a deploy removes or renames something your agents need.

Run an optional safe probe

Configure one read-only tool call, such as ping, health, or list_status, to verify that the tool is still callable end to end.

How MCP alerts work

From endpoint to notification

An MCP monitor stores the endpoint, transport, authentication, expected capabilities, optional probe details, and notification channels. On each scheduled check, AlertsDown validates the MCP server from outside your app. Failed initialization, missing expected capabilities, and failed probe calls are treated as monitor failures and routed to the contacts you selected.

Endpoint https://your-app.com/mcp

Capabilities tools, resources, prompts

Probe safe read-only tool call

Alerts Email, SMS, Telegram, WhatsApp, webhooks

Setup in AlertsDown

Create an MCP Server Monitor

MCP Server Monitoring is available on Indie Builders and above. Use it for your own MCP services, internal agent tools, or vendor endpoints where uptime alone is not enough.

Open Add URL

Enter the MCP endpoint

Paste the Streamable HTTP or SSE endpoint agents use, choose the transport type, timeout, and check interval.

Add authentication

Select no auth, bearer token, or custom header depending on how your MCP server protects the endpoint.

Define expected capabilities

List important tools, resources, and prompts by exact name, then enable alerts for missing capabilities.

Add a safe probe

Optionally call one non-destructive read-only tool with JSON arguments and alert if the probe fails.

Choose notification channels

Route failures through your AlertsDown contacts, including email, SMS, Telegram, WhatsApp, or webhook channels available on your plan.

Example monitor setup

Name: Production MCP Server. Endpoint: https://app.example.com/api/mcp. Transport: Streamable HTTP. Auth: bearer token or custom header. Expected tools: search_docs, create_ticket, list_incidents. Probe: health_check with {"verbose":false}.

Use cases

Where MCP alerts help

Agent tool reliability

Get alerted when the MCP server behind your internal coding, search, database, or deployment tools stops initializing correctly.

Capability regression alerts

Catch deploys that rename or remove a required MCP tool, resource, or prompt before your agents start failing user tasks.

Vendor MCP monitoring

Track third-party MCP endpoints your team depends on and route failures to the same notification channels as website outages.

Release verification

After deploys, migrations, auth changes, or dependency updates, verify that the MCP endpoint and safe probe still work.

Internal platform checks

Monitor MCP wrappers around databases, docs, ticketing, deployment systems, analytics, and incident tools.

Reliability documentation

Turn MCP monitor failures, recovery timing, and probe details into postmortem notes, customer updates, and follow-up tasks.

How to use it

Checks to configure first

Monitor the production MCP endpoint and alert if initialization fails.

Alert if required tools like search_docs, list_incidents, or create_ticket disappear.

Add a safe probe for health_check and alert if it fails after deployment.

Send MCP monitor failures to the same on-call contacts as API and website downtime.

Access and security

Keep monitor secrets scoped and probes safe

MCP monitor authentication

Use bearer tokens or custom headers for private MCP endpoints. Store only the secret needed for the monitor to initialize and run safe checks.

Safe probes only

Probe calls should be read-only and non-destructive. Use health, list, status, or ping-style tools rather than write or mutation tools.

Plan-gated monitoring

MCP Server Monitoring is available on Indie Builders and above, separate from the hosted AlertsDown MCP setup for AI clients.

Monitor the MCP servers your agents depend on.

Add your endpoint, pin the capabilities that matter, choose a safe probe, and route failures to your AlertsDown alert channels.

Create MCP Monitor View Pricing

MCP Alerts FAQ

What are MCP alerts?

MCP alerts are AlertsDown monitors for your own or vendor Model Context Protocol servers. They notify you when an MCP endpoint stops initializing, loses expected capabilities, or fails a configured safe probe.

How is this different from AlertsDown hosted MCP?

MCP alerts check MCP servers you add to AlertsDown. Hosted MCP is AlertsDowns own MCP endpoint that AI tools connect to when they need to manage your AlertsDown monitors.

What does an MCP monitor check?

It checks endpoint connectivity, MCP initialization, advertised tools, resources, prompts, expected capability names, and optional safe read-only probe calls.

Which transports are supported?

MCP Server Monitoring supports Streamable HTTP and SSE transports in the AlertsDown monitor setup flow.

Which plan includes MCP Server Monitoring?

MCP Server Monitoring is available on the Indie Builders plan and above.