Skip to main content
Glama
dmayan-ss

mcp-ispkeeper

by dmayan-ss
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-ispkeeper

No user-submitted related servers found.

    Related Servers

    • sql-mcp

      teghoz
      F
      license
      A
      quality
      C
      maintenance
      A read-only MCP server for SQL Server and PostgreSQL that enables exploring and querying databases (schemas, tables, views, procedures, indexes, foreign keys) and running arbitrary SELECT queries.
      37
      -

    • avanpost-idm-6-mcp

      siertum
      -
      license
      Not graded
      quality
      Not graded
      maintenance
      Read-only MCP server for Avanpost IDM 6, enabling access to employees, roles, rights, organizational structure, AD groups, access matrices, and audit data via natural language.
      -

    • mcp-database

      AimanFadillah
      A
      license
      A
      quality
      C
      maintenance
      Read-only MySQL/MariaDB MCP server for running SELECT queries safely, with automatic read-only enforcement and query limits.
      3
      6 npm
      MIT

    • mcp-bd-readonly

      noemartinezoptima
      F
      license
      C
      quality
      B
      maintenance
      Provides read-only access to a MySQL inventory and invoicing database through MCP tools, enabling safe SQL queries, table inspection, and financial reporting without any write capabilities.
      13
      -

    • datagate-mcp

      hyamie
      A
      license
      B
      quality
      C
      maintenance
      MCP server for the DataGate billing platform API, providing read-only tools to manage customers, invoices, products, agreements, sites, and payments.
      13
      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.8/5.0

    Scored across 25 tools

    Disambiguation4/5

    Tools are generally distinct by domain (clients, invoices, tickets, connections, network). Some potential overlap between get_client_services and the connection-specific tools (list_internet_connections, etc.), but the descriptions explicitly clarify the boundaries. Overall, an agent can reliably pick the right tool.

    Naming Consistency4/5

    Predominantly uses a consistent verb_noun pattern (list_*, get_*, search_clients). Minor deviation with get_clients_summary (plural instead of singular) and list_fttx_infrastructure (FTTx not fttx_infrastructure), but the pattern is easily recognizable and predictable.

    Tool Count5/5

    25 tools is on the high side but still well within reason for a comprehensive ISP management system. Each tool has a clear purpose and covers distinct aspects (clients, invoices, collections, connections, tickets, network, infrastructure, reference data). No tool feels extraneous.

    Completeness5/5

    The tool set provides thorough coverage for an ISP management server: CRUD-like operations for clients, invoices, collections, internet/TV/phone connections, and support tickets. It also includes network status, infrastructure hierarchy tracing, and auxiliary reference data. I see no obvious missing operations for typical workflows.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources