Skip to main content
Glama
VisualSentinel

Visual Sentinel MCP Server

Official
by VisualSentinel
OverviewSchemaSourceRelated ServersDiscussions(2)Admin
TypeScript
Remote

Related Servers

Alternatives to Visual Sentinel MCP Server

No user-submitted related servers found.

    Related Servers

    • uptybots-mcp-server by uptybots

      uptybots-mcp-serverofficial

      uptybots
      A
      license
      A
      quality
      B
      maintenance
      Uptime monitoring for websites, APIs, SSL certificates, domain expiry, ping and TCP/UDP ports. 15 tools to list, create, pause and delete monitors, pull incident timelines with error codes, and read hourly or daily uptime and response-time statistics.
      15
      60 npm
      1
      MIT

    • nslookup.io MCP Server

      NsLookup-io
      A
      license
      A
      quality
      D
      maintenance
      Provides comprehensive tools for real-time DNS queries across 53 record types, global propagation checks, and SSL certificate analysis. It also enables domain security scans for SPF/DKIM/DMARC configurations and HTTP uptime monitoring.
      8
      47 npm
      23
      Apache 2.0

    • merlonix-mcp

      cmhenry79
      A
      license
      Not graded
      quality
      C
      maintenance
      Provides live infrastructure monitoring for AI agents, including domain health checks, MCP server security posture, email blacklists, broken-link scans, and cloud vendor status. No signup or API key needed for public tools.
      MIT
    • Hyperping by hyperping

      Hyperpingofficial

      hyperping
      A
      license
      Not graded
      quality
      C
      maintenance
      Official Hyperping MCP server for uptime, API, cron and server monitoring. 26 tools covering monitors, outages and timelines, uptime, response time, MTTR and MTTA, on-call schedules and escalation policies, over a remote Streamable HTTP endpoint with Bearer token auth and no install.
      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

    A3.7/5.0

    Scored across 16 tools

    Disambiguation5/5

    Each tool targets a distinct resource or action: alerts, incidents, monitors, servers, status pages, and public checks (DNS, SSL, speed, health). Even similar tools like vs_website_check and vs_speed_test have clearly differentiated scopes (quick health vs. detailed performance).

    Naming Consistency4/5

    Tools follow a consistent vs_{resource}_{action} pattern (e.g., vs_alerts_list, vs_monitors_create) with snake_case. Slight inconsistencies: vs_health is just a noun, and vs_monitors_uptime uses a noun instead of a verb, but overall pattern is clear and predictable.

    Tool Count5/5

    16 tools is well within the expected range for a monitoring service. Each tool serves a distinct purpose covering alerts, incidents, monitors, servers, status pages, and public utilities. No tool feels extraneous or redundant.

    Completeness3/5

    The tool set covers core monitoring workflows (list, get, create monitors; list and get incidents; list and acknowledge alerts) but lacks update and delete operations for monitors and incidents. The surface feels slightly incomplete for full lifecycle management.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources