Skip to main content
Glama
Zfinix

fiberone-mcp

by Zfinix
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to fiberone-mcp

No user-submitted related servers found.

    Related Servers

    • isp2go

      jyswee
      A
      license
      Not graded
      quality
      C
      maintenance
      An MCP server for ISP management that enables agents to handle customer onboarding, billing, ticketing, network monitoring, and compliance (RICA/POPIA) via 20 tools.
      21 npm
      -

    • coolplatform-cs-agent

      rganesh2-Agent
      F
      license
      Not graded
      quality
      B
      maintenance
      Provides MCP tools that let an agent retrieve customer account, product usage, interaction, and support summaries, and create follow-up tasks after user approval.
      -

    • AI IT Helpdesk

      varma5359
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables IT helpdesk operations such as retrieving user and device information, checking device status, and creating, retrieving, and updating support tickets through MCP tools.
      -
    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 22 tools

    Disambiguation4/5

    Tool names clearly indicate distinct resources: account, usage, transactions, tickets, modem, pause, autorenew, plans, etc. A few related plan tools (get_plans, get_renewal_plan, get_upgrade_plans) could be confused, but descriptions clarify their scope.

    Naming Consistency4/5

    The set consistently uses lowercase snake_case, with get_ as the dominant read prefix and action verbs for the few writes (login, logout, create_outage_ticket). login/logout break the verb_noun pattern slightly, but the convention is predictable.

    Tool Count3/5

    At 22 tools, the server is on the heavy side and includes several peripheral getters (FAQs, experience centres, dashboard) that could be trimmed. The count is not unreasonable for a broad ISP self-service API, but it exceeds the ideal 3-15 range.

    Completeness2/5

    The surface is heavily read-only: it exposes status and history for pauses, auto-renew, pay4me, and upgrades, but no corresponding actions to pause, update auto-renew, create a pay4me request, or upgrade. With only create_outage_ticket as a mutating tool, agents will hit dead ends on common account-management tasks.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources