Skip to main content
Glama
jamesbrink

mcp-deadmansnitch

by jamesbrink
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to mcp-deadmansnitch

No user-submitted related servers found.

    Related Servers

    • croncron

      itsnotrwanman
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server that lets AI agents manage cron jobs through natural language — adding, listing, pausing, removing, running, and viewing logs of scheduled jobs with plain-English schedule parsing, automatic log capture, missed-run detection, and failure alerts.
      MIT

    • cronalert-mcp

      jaredhobbs
      A
      license
      A
      quality
      C
      maintenance
      MCP server for CronAlert uptime monitoring — manage monitors, check results, and incidents from any MCP-compatible AI client.
      9
      62 npm
      MIT

    • claude-cron

      frr149
      A
      license
      Not graded
      quality
      F
      maintenance
      MCP server that allows AI coding assistants to schedule deferred tasks such as reminders, shell commands, and AI prompts, executing them as an OS daemon.
      2 npm
      MIT

    • exit1-mcp

      Mopra
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Exit1 uptime monitoring. Enables AI assistants to create and manage uptime checks, configure alerts, and query status via natural language.
      32 npm
      MIT
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    A4.3/5.0

    Scored across 1 tool

    Disambiguation5/5

    There is only one tool, so there is no possibility of confusing separate tools. The actions within the tool (list, get, create, etc.) are distinct and clearly named, eliminating any ambiguity.

    Naming Consistency5/5

    The single tool name 'snitch' is a noun representing the resource, and all actions follow a consistent verb style (list, get, create, update, delete, pause, unpause). The naming pattern is uniform and predictable, making it easy to understand the available operations.

    Tool Count4/5

    While the tool count is only 1, it effectively acts as a subcommand interface covering all core operations. This is slightly unusual but remains well-scoped given the narrow domain of Dead Man's Snitch monitoring, so the count is reasonable.

    Completeness5/5

    The actions provide full CRUD coverage plus monitoring-specific operations (pause, unpause, check_in) and tag management. No obvious gaps exist for the stated purpose, and the optional parameters cover additional needs like alert types and notes.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources