Skip to main content
Glama
Sign In
exit1-mcp

exit1-mcp

by Mopra
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to exit1-mcp

No user-submitted related servers found.

    Related Servers

    • uptrack-mcp

      uptrack-mcpofficial

      Uptrack-App
      A
      license
      Not graded
      quality
      C
      maintenance
      MCP server for Uptrack uptime monitoring. Manage monitors and incidents from AI agents like Claude, ChatGPT, and Cursor.
      13 npm
      MIT
    • Drumbeats MCP

      Drumbeats MCPofficial

      drumbeats-io
      A
      license
      A
      quality
      B
      maintenance
      MCP server for Drumbeats monitoring. Enables creating monitors, triaging incidents, and running HTTP/SSL/DNS checks using natural language from any AI client.
      19
      108 npm
      2
      Apache 2.0

    • mcp-uptime-kuma

      DavidFuchs
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Uptime Kuma that enables monitoring and management of uptime monitors, heartbeats, notifications, tags, and maintenance windows via natural language.
      35
      619 npm
      64
      MIT
    • uptimepage

      uptimepageofficial

      uptimepage
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server for Uptimepage uptime monitoring. An LLM client can read your monitors and incidents, run a check on demand, and post incident updates. Writes need an OAuth login and a scoped token, and each one is logged.
      54
      AGPL 3.0

    • stillonline-mcp

      shenwell
      A
      license
      A
      quality
      D
      maintenance
      MCP server for StillOnline uptime monitoring, enabling management of projects, checks, incidents, and public status pages through natural language.
      10
      58 npm
      1
      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/5.0

    Scored across 15 tools

    Disambiguation4/5

    Most tools target a distinct resource+action, and descriptions explicitly steer between look-alikes (toggle_check vs delete_check, send_test_alert vs alert config). The one fuzzy cluster is the three read tools on a single check (get_check, get_check_history, get_check_stats), whose boundaries are clarified only by description text rather than by name.

    Naming Consistency5/5

    Every tool follows the same snake_case verb_noun pattern (create_check, get_check_stats, toggle_check, add_webhook_alert). Verb variety (get/set/add/send/toggle) is semantically meaningful rather than arbitrary.

    Tool Count5/5

    15 tools is well within a healthy range for a monitoring service, and each maps to a real task: account setup, check CRUD, alert channel configuration, and read/investigation queries. No obvious filler or duplicate tooling.

    Completeness3/5

    Core lifecycle is covered for checks (create/update/toggle/delete/read), which is the heart of the domain. But there are notable gaps: webhooks can be added but never listed or removed, status pages are read-only (no create/update), folders are referenced in list_checks/create_check but have no management tools, and maintenance mode is exposed in get_check yet cannot be set.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues

    Resources