Skip to main content
Glama
adelaidasofia

paging-mcp

by adelaidasofia
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to paging-mcp

No user-submitted related servers found.

    Related Servers

    • apprise-rmcp

      dinglebear-ai
      A
      license
      Not graded
      quality
      A
      maintenance
      MCP server that enables agents to send tagged notifications through Apprise, run one-off URL sends, and check upstream health via stdio or streamable HTTP.
      2
      AGPL 3.0

    • ntfy-mcp

      Edqe14
      A
      license
      C
      quality
      D
      maintenance
      MCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.
      2
      12 npm
      MIT

    • mcp-server-splunk-oncall

      arnstarn
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for the Splunk On-Call (VictorOps) API providing comprehensive incident management, on-call schedules, team administration, and alert reporting through natural language.
      MIT

    • mcp-gotify

      fastmcp-me
      A
      license
      B
      quality
      D
      maintenance
      MCP server for sending Gotify push notifications to your devices.
      1
      MIT

    • incidentrelay-mcp

      NikGariel
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for IncidentRelay, exposing its entire REST API (279 operations) through gateway and curated tools for on-call scheduling, alert routing, and incident management.
      MIT

    • Simple Ntfy MCP Server

      Aaryan-Kapoor
      A
      license
      B
      quality
      D
      maintenance
      A lightweight MCP server for sending push notifications via ntfy.sh, supporting customizable titles, priorities, tags, and action buttons.
      1
      6 npm
      7
      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

    A3.9/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: health_check for server status, list_configured_channels for viewing channels, notify for broadcasting, notify_one for sending to a single URL, and dry_run for previewing. No overlap in functionality.

    Naming Consistency4/5

    Names are consistent in using lowercase with underscores, and most follow a verb_noun pattern (list_configured_channels, notify, notify_one, dry_run). health_check is a compound noun but still clear. Minor deviation in verb usage (health_check vs. notify) keeps it from a perfect score.

    Tool Count5/5

    With 5 tools, the server is well-scoped for a paging/notification service. Each tool addresses a necessary operation (health, listing, sending, sending to one, dry run) without redundancy or excessive count.

    Completeness4/5

    Covers core functionality: health check, channel listing, broadcasting, single notification, and preview. Lacks a tool to manage persistent channels or retrieve notification history, but these are minor gaps given the server's focus on dispatching notifications.

    Maintenance

    ActivityActive
    ResponsivenessNo issues

    Resources