Skip to main content
Glama
Labs64

Labs64/NetLicensing-MCP

by Labs64
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Hybrid

Related Servers

Alternatives to Labs64/NetLicensing-MCP

No user-submitted related servers found.

    Related Servers

    • mcp-n8n

      backsoul
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for integrating with n8n, enabling workflow automation and management through natural language.
      221 npm
      1
      MIT

    • amazon-mcp

      coaxon
      A
      license
      Not graded
      quality
      D
      maintenance
      MCP server for Amazon Selling Partner API and Advertising API, enabling access to orders, inventory, pricing, ads, and reports via natural language.
      1
      MIT

    • hcloud-mcp

      Xodus-CO
      A
      license
      C
      quality
      D
      maintenance
      A Model Context Protocol server for the Hetzner Cloud API that enables natural language management of cloud infrastructure. Users can list, create, and modify servers, networks, volumes, and load balancers through MCP-compatible clients.
      67
      36 npm
      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.5/5.0

    Scored across 48 tools

    Disambiguation5/5

    Each tool clearly targets a specific entity and action (e.g., create/update/delete/list for products, modules, templates, licenses, licensees, bundles, transactions, payment methods, tokens). No two tools have overlapping responsibilities; even similar ones like create_license and obtain_bundle differ in scope and intent.

    Naming Consistency5/5

    All tools follow a strict 'netlicensing_verb_noun' pattern with consistent snake_case. Verbs are clear and consistently used (create, get, list, update, delete, obtain, transfer, validate), and resource nouns are unambiguous. No mixed conventions or vague verbs.

    Tool Count3/5

    At 48 tools, this is a large surface, but it mirrors the full CRUD and operational scope of a licensing management platform (products, modules, templates, licenses, licensees, bundles, transactions, tokens, payment methods, and metadata lookups). While heavy, every tool serves a distinct purpose and is justifiable for the domain.

    Completeness5/5

    The tool set covers the entire lifecycle for all core entities: create, read, update, delete, plus specialized operations like validation, license transfer, shop token generation, and bundle obtaining. It also includes necessary metadata endpoints (countries, license types, licensing models) and seems to have no missing critical operations for the stated purpose.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive

    Resources