Skip to main content
Glama
ssservicios

mcp-ispkeeper

by ssservicios
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
      3 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

    B3.4/5.0

    Scored across 32 tools

    Disambiguation4/5

    Tools are largely distinct by entity and action (subscriptions, tickets, invoices, connections, suppliers), and the list/get/search pairing is clear. Some overlap exists among reference-data tools like list_subscription_catalog, list_plans, list_auxiliary_data, and get_network_element, but their descriptions provide enough context to disambiguate.

    Naming Consistency5/5

    Almost every tool follows a predictable list_<plural> / get_<singular> / search_<noun> pattern, with consistent pairing across domains. Minor exceptions like get_clients_summary and get_fttx_trace do not undermine the overall convention.

    Tool Count3/5

    32 tools is heavy for an MCP server, but the broad ISP domain (clients, billing, network, tickets, suppliers) justifies most of them. The surface is larger than ideal and some reference-data tools could be consolidated.

    Completeness3/5

    As a read-only query surface it covers most core entities well, including clients, services, billing, tickets, network infrastructure, and suppliers. However, there is no way to enumerate some network elements like nodes/VLANs despite get_network_element existing, and no write or lifecycle operations are available, limiting end-to-end workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources