Skip to main content
Glama
snickery

aussiebb-mcp

by snickery
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to aussiebb-mcp

No user-submitted related servers found.

    Related Servers

    • Australian Business

      arbazex
      F
      license
      A
      quality
      D
      maintenance
      An MCP server that provides tools to look up and verify Australian businesses using the Australian Business Register API, enabling AI agents to retrieve business details via ABN, ACN, or name search.
      3
      -

    • domotz-mcp

      WYRE-AI
      A
      license
      A
      quality
      A
      maintenance
      MCP server for Domotz network monitoring and management. Enables AI assistants to query network devices, alerts, and topology via the Domotz API.
      2
      18 npm
      Apache 2.0

    • NetPulse

      hind77
      A
      license
      A
      quality
      D
      maintenance
      An MCP server that exposes live network monitoring data as Resources and diagnostic capabilities as Tools, letting AI assistants query network health conversationally.
      6
      MIT
    • tickiti-mcp by tickiti

      tickiti-mcpofficial

      tickiti
      A
      license
      B
      quality
      B
      maintenance
      An MCP server that exposes the Tickiti helpdesk API to AI assistants, enabling ticket management and helpdesk operations via natural language.
      11
      MIT

    • threatlocker-mcp-server

      BigfootBytes
      A
      license
      A
      quality
      A
      maintenance
      MCP server for interacting with the ThreatLocker Portal API, enabling querying of computers, applications, policies, audit logs, and more through AI assistants.
      18
      1
      GPL 3.0
    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 13 tools

    Disambiguation5/5

    Each tool has a distinct purpose: listing services, listing diagnostics, running specific tests, fetching results, checking history, outages, speed tests, faults, and destructive actions. Even similar diagnostics (check_connection, ntd_status, loopback_test) are clearly differentiated by their descriptions, and run_diagnostic serves as an explicit escape hatch.

    Naming Consistency4/5

    Most tools follow a verb_noun pattern (list_services, check_connection, run_diagnostic), but some are noun-first test names (ntd_status, loopback_test, speed_test_results). The naming is readable and generally predictable, though not perfectly uniform.

    Tool Count5/5

    13 tools is well-scoped for an ISP diagnostics and management server. Each tool covers a real need (service listing, connectivity checks, test execution, result retrieval, outages, faults, destructive actions), and the count is not excessive.

    Completeness4/5

    The server provides comprehensive diagnostic coverage, including running tests, fetching results, and viewing history, plus outages and service info. Minor gaps exist like lack of fault creation, but the presence of run_diagnostic as a catch-all and the account-wide focus mitigate these.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources