Skip to main content
Glama

Related Servers

Alternatives to legacy2mcp

No user-submitted related servers found.

    Related Servers

    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to call any SOAP/WSDL web service as MCP tools, automatically converting each WSDL operation into a callable tool with authentication and security controls.
      AGPL 3.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      Exposes SOAP web services as Model Context Protocol (MCP) servers, allowing AI models to interact with legacy SOAP services through automatic method discovery and type mapping.
      MIT
    • A
      license
      C
      quality
      D
      maintenance
      Exposes SOAP-based web services as MCP servers by parsing WSDL files. Enables AI assistants to interact with legacy SOAP/WS-\* web services through the Model Context Protocol.
      21
      4
      MIT
    • F
      license
      C
      quality
      D
      maintenance
      Wraps a legacy SOAP + stored-procedure backend with governed MCP tools, including a semantic data dictionary, compensation for transactionless writes, and load protection, enabling AI agents to safely operate on enterprise systems.
      10
      -
    • A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI agents to discover and invoke backend tools over MCP JSON-RPC while enforcing 3-legged OAuth 2.0 identity propagation, role-based access control, and protocol transcoding to REST APIs.
      1
      Apache 2.0
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to securely discover, invoke, and manage tools through a hardened MCP endpoint with protections like injection detection, circuit breakers, retry backoff, response caching, context-window limiting, and state snapshots.
      7 npm
      MIT

    TDQS

    C2.3/5.0

    Scored across 3 tools

    Disambiguation4/5

    GetOrder and ListOrders clearly target order retrieval differently, and GetInventory targets a separate resource. Minor overlap in the 'Get' prefix does not meaningfully confuse selection.

    Naming Consistency4/5

    All tools follow a consistent adapter-prefixed PascalCase SOAP operation pattern: orders_GetOrder, orders_ListOrders, orders_GetInventory. The mixed Get/List verbs are minor and reflect the underlying SOAP operation names.

    Tool Count3/5

    Three tools is borderline thin for an orders service, though it may accurately reflect the exposed legacy SOAP operations. It feels scoped but limited.

    Completeness2/5

    The surface only supports reading orders and inventory, with no create, update, cancel, or other lifecycle operations. For an order management domain this is a significant gap that would block common agent workflows.

    Maintenance

    ActivityMaintained
    ResponsivenessResponsive