About this integration
Turn a legacy SOAP/WSDL service into a safe, typed, schema-validated, audit-logged MCP server
- Transport
- stdio
- Authentication
- unknown
- Initial setup
- credentials
- Runtime
- unattended
- Evidence
- documented
- Version
- 0.1.0
- Package
- legacy2mcp
- Last compatibility test
- Not independently tested
Connect your agent
legacy2mcpPublisher README and manifest reviewed offline; package, WSDL, and SOAP endpoints were not executed. The README states that the MCP server itself has no auth/authz in v0.1, so it must remain a trusted local stdio process.
Capabilities: Discover WSDL operations, Generate typed MCP tools, Validate operation arguments, Invoke allowed SOAP operations, Audit tool calls
Connected profiles
Additional details
io.github.bvenkata/legacy2mcp
Source ↗ · Checked 2026-09-170.1.0
Source ↗ · Checked 2026-09-17CC0-1.0; package licenses are separate
Source ↗ · Checked 2026-09-17pypi
Source ↗ · Checked 2026-09-17legacy2mcp
Source ↗ · Checked 2026-09-180.1.0
Source ↗ · Checked 2026-09-18The documented run command starts a stdio MCP server and can operate as a long-running sidecar launched by a client.
Source ↗ · Checked 2026-09-18SOAP endpoints may be anonymous or use HTTP Basic credentials read from an environment variable. HTTP Basic is outside the native authentication taxonomy.
Source ↗ · Checked 2026-09-18Launch legacy2mcp run with an absolute path to the operator-reviewed YAML configuration.
Source ↗ · Checked 2026-09-18Publisher documentation reviewed; package and integration endpoint not executed or independently security-audited.
Source ↗ · Checked 2026-09-18