Skip to main content
Glama
paging-mcp

paging-mcp

Related Servers

Alternatives to paging-mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      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
    • A
      license
      C
      quality
      D
      maintenance
      MCP server for sending notifications to ntfy.sh or self-hosted ntfy instances.
      2
      16 npm
      MIT
    • A
      license
      B
      quality
      B
      maintenance
      A lightweight MCP server that lets AI agents send real-time alerts, operational notifications, and webhook messages through Telegram bots and Discord webhooks without exposing primary API keys or relying on heavy middleware. It provides tools for delivering Markdown-formatted Telegram messages and rich Discord embed cards, plus a channel status/health check.
      3
      MIT
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables sending notifications through an Apprise API server — fanning a message out to one configured tag or all configured services, firing one-off sends at raw Apprise URL schemas, and checking upstream health or authenticated status — all via a single action-based tool. Offers a stdio MCP server alongside a matching CLI.
      307 npm
      MIT
    • A
      license
      Not graded
      quality
      D
      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.
      1,996 PyPI
      MIT
    • A
      license
      B
      quality
      D
      maintenance
      MCP server for sending Gotify push notifications to your devices.
      1
      MIT

    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

    ActivitySlowing
    ResponsivenessNo recent community issues