Skip to main content
Glama
harsha-moparthy

legacy-mcp

by harsha-moparthy
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to legacy-mcp

No user-submitted related servers found.

    Related Servers

    • foral by foral-dev

      foralofficial

      foral-dev
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents to access internal systems without public APIs as typed, governed MCP tools, with human-approved writes and fail-closed contract updates.
      Apache 2.0

    • AnythingMCP

      bricefpv-lab
      F
      license
      Not graded
      quality
      B
      maintenance
      A self-hosted MCP gateway that turns REST, SOAP, GraphQL, and SQL endpoints into MCP tools, enabling AI clients like Claude and ChatGPT to interact with legacy and modern APIs without code changes.
      -

    • varco_mcp

      williamselmo1993
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables MCP-compatible AI agents to safely act on business backends by enforcing per-agent permissions, autonomy thresholds, human approval with review-and-edit, and full audit trails.
      MIT

    • iMCP

      Duvaragesh
      F
      license
      Not graded
      quality
      D
      maintenance
      A universal bridge that turns legacy backend services and modern APIs into AI-accessible tools without requiring code rewrites. It dynamically generates tool definitions from WSDL, OpenAPI, or custom JSON specs to enable AI assistants to interact with systems like SAP, IBMi, and SOAP services.
      -

    • SOAP MCP Server

      mayankgupta7673
      A
      license
      Not graded
      quality
      B
      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
    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

    C2.9/5.0

    Scored across 10 tools

    Disambiguation5/5

    Each tool has a clear, distinct purpose: customer lookup, credit, hold, status; order lifecycle (get, list, place, cancel); item availability; and cleanup. No overlapping functionality.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., get_order_status, lookup_customer), making them predictable and easy to understand.

    Tool Count5/5

    10 tools cover the core operations of a legacy order/customer system without being excessive or too sparse.

    Completeness4/5

    Covers customer management, order lifecycle, inventory check, and cleanup. Missing update/modify order tool, but otherwise well-scoped for the domain.

    Maintenance

    ActivitySlowing
    ResponsivenessNo issues

    Resources