mttrly MCP Server

by mttrly Your server? Claim it

answering

mttrly is answering right now. Last checked 2 min ago.

AI-powered incident management and server monitoring via MCP.

Uptime history 91 days of history · worst day 92%

91 days agonow

100.0%

Uptime 24h

92 of 92 checks

—

Tools

hidden behind auth

279 ms

Response time

average over 24h

OAuth sign-in

Access

streamable-http

Nothing serious here today

Today is the operative word: we check mttrly every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 2 min ago.

Claude Code Claude Desktop Codex Cursor VS Code

run in your terminal

claude mcp add mcp --transport http https://api.mttrly.com/mcp

Settings → Connectors → Add custom connector, then paste this address

https://api.mttrly.com/mcp

~/.codex/config.toml

[mcp_servers.mcp]
url = "https://api.mttrly.com/mcp"

.cursor/mcp.json

{
  "mcpServers": {
    "mcp": {
      "url": "https://api.mttrly.com/mcp"
    }
  }
}

.vscode/mcp.json

{
  "servers": {
    "mcp": {
      "type": "http",
      "url": "https://api.mttrly.com/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URL	Transport	State	Latency	Checked
https://api.mttrly.com/mcp	streamable-http	sign-in	150 ms	2 min ago

Alternatives to mttrly

same job, measured the same way

Omniwatchguard

by omniwatchguard

AI-powered website change monitoring - manage monitors and alerts via MCP.

7 tools answering

Runframe MCP Server

by runframe

MCP server for Runframe incident management covering incidents, on-call, postmortems, and more.

55 installs/wk local only

Vantaj

by vantaj

Vantaj uptime monitoring via MCP - manage monitors, heartbeats, incidents, and status pages.

13 tools answering

Fleet MCP

by simplyminimal

An MCP server that provides tools for managing and monitoring your Fleet Device Management instance.

245 installs/wk local only

Ironscales

by wyre-ai

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

local only

Ironscales

by wyre-technology

MCP server for Ironscales phishing incident management — incidents, mailboxes, and reporting.

local only

Ninjaone

by lungshot

MCP server for NinjaONE RMM with device management, monitoring, and automation

local only

DevHelm MCP Server

by devhelmhq

Monitor uptime, manage incidents, configure alerting, and query dependency status via DevHelm

177 installs/wk local only

mttrly — questions

Answers built from our own checks of this server.

Why is there no tool list for mttrly?

The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 100.0% of checks in the last 24 hours got a reply.

Is mttrly working right now?

We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 279 ms. The bar chart above shows every period we have measured.

How do I connect mttrly?

Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.

How do you sign in to mttrly?

No API key is involved. mttrly answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.

How fast is mttrly?

It answers our handshake in 279 ms on average, which is faster than 51% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.