3.0

3.0.4-funcrel

Note

  • Requires CAST Imaging 3.6.0-funcrel or later - see the documentation.

Feature Improvements

Summary Details
Support for Column-Level Dependency Analysis in Imaging MCP Server Added support for Column-Level Dependency Analysis for Imaging MCP Server. This must be explicitly enabled/disabled in the CAST Imaging admin settings via the Table Columns icon, see the documentation.
CAST Imaging MCP Tool confirmation improvements Added MCP tool annotations to identify read-only tools. Compatible clients such as Gemini Enterprise can now run safe read-only queries without repeated confirmation prompts from the user, while write actions still require user confirmation.

Resolved Issues

Customer Ticket Id Details
58256 Fixes an issue where bulk tagging was not working as expected for some operators like equals or start with/ends with.

Bug Fixes

Details
Resolved a high-severity security vulnerability (GHSA-f4xh-w4cj-qxq8) in the langsmith dependency. Fixed by upgrading langsmith from 0.8.15 to 0.8.18.

3.0.3-funcrel

Note

  • Requires CAST Imaging 3.6.0-funcrel or later - see the documentation.

Other Updates

Internal Id Details
IMAGMCP-353 Resolved multiple high-severity CVEs detected in previous release. Dependencies and components have been updated to eliminate known vulnerabilities, improving the overall security posture of the platform.

Bug Fixes

Details
Fixed an issue where the authorization token sent by the client was not correctly passed through to CAST Imaging, which could cause requests to fail with authentication errors even when valid credentials were provided. The MCP server now reliably forwards client credentials regardless of the environment. No action is required, authentication continues to work as before for all existing configurations.

3.0.2-funcrel

Note

  • Requires CAST Imaging 3.6.0-funcrel or later - see the documentation.

New Features

Summary Details
Meta-Tool architecture mode A new tool-exposure mode for the Imaging MCP Server. The full toolset can now be replaced by two general-purpose meta-tools, reducing the working-memory footprint consumed by tool definitions in connected AI assistants. The mode is controlled by the new MCP_TOOL_SURFACE_PROFILE setting in app.config. Default value is full (classic behaviour, unchanged); setting it to intents activates the meta-tool surface. In intents mode the assistant sees 2 tools, plus an on-demand catalogue of the underlying capabilities. The capabilities themselves are unchanged. Specific capabilities can be hidden in intents mode via MCP_INTENTS_HIDDEN_FUNCTIONS. The setting applies to the entire server instance and to every connected assistant. See the documentation.

Resolved Issues

Customer Ticket Id Details
57653 Users running CAST Imaging behind HTTPS with a private or self-signed CA were facing an issue where the MCP server was blocking the requests to Imaging APIs. This issue has been fixed now. Users can now supply the certificate chain to the MCP Server through the new SSL_CA_BUNDLE setting in app.config. The setting accepts an absolute path to a Base-64 PEM-encoded certificate chain. See the documentation.

3.0.1-funcrel

Note

New Features

Summary Details
CAST Imaging MCP Server compatibility check with APIs This release adds a compatibility check for the CAST Imaging MCP Server and CAST Imaging APIs service. Users can now quickly check their current MCP Server version, the connected Imaging API version, and the recommended Imaging API version for the MCP server they are using by querying the MCP server.

Resolved Issues

Customer Ticket Id Details
57997 An issue observed where the MCP server was not working with Gemini models. This issue has been fixed.
57860 An issue was found where the formatted responses from the MCP server were in json string format that contained newline characters. This made it difficult to read for the users. It has been in fixed. All the responses are now in clean json format.
57998 An issue was found where the MCP server was not able to filter objects on the basis of the object search type(external or internal). This has been added in the release

3.0.0-funcrel

Note

New Features

Summary Details
A new bulk object tagging tool has been added, making it easier to tag or untag large groups of objects. The new bulk tagging tool lets users apply tags to groups of objects selected by criteria such as object name/full name, object type, transactions, or data graphs. Existing tagging by explicit object IDs remains available for cases where the exact target objects are already known.

Resolved Issues

Customer Ticket Id Details
57216 Support for creating custom aggregations via tags has been added. Previously, users could create tags for objects but were unable to use those tags to build custom views with grouped nodes. With this fix, it is now possible to create custom views that aggregate objects based on their associated tags (e.g., grouping objects under nodes like TG_TABLES or TG_VIEWS).
57254 An issue was identified where source file paths were truncated when retrieving object details using object tools, particularly for cases involving long file paths. This has been resolved, and full source file paths are now returned without truncation.
57324 An issue was identified where the objects endpoint did not differentiate between standard COBOL Programs and COBOL Transactional Programs, returning all such objects under a single type ("Cobol Program"). This also prevented accurate filtering for transactional programs, despite their distinction in the architectural graph. This has been enhanced by introducing support for multiple filtering operators, including equals, starts with, and ends with, in addition to the default contains operator, enabling more precise and flexible queries.
57236 An issue was identified where callers and callees of an object were partially returned due to a pagination limitation, restricting results to the first 100 entries. This led to incomplete dependency information when using MCP tools, even though the full dataset was available via the API. This has been fixed by improving pagination handling, ensuring that all callers and callees are now fully retrieved without truncation.
56956 A discrepancy was observed between the transaction counts returned by MCP and those displayed in Imaging. This was due to the Imaging APIs service counting only transactions that have both a start point and an end point, while the UI displays all transactions, including those without endpoints. This difference in logic led to mismatched counts. A fix has been introduced to align the API behavior with the UI by including all transactions in the count, ensuring consistency across both.
57276 An issue was identified where relationships between nodes could not be extracted for static custom views when using MCP tools, resulting in incomplete or missing data when querying such views. This has been resolved, and MCP now correctly retrieves and returns the relationships between nodes within static custom views, enabling accurate analysis and reporting.
57421 An issue was identified where quality insights retrieved via the MCP tool application_quality_insights were truncated, returning only a subset of results (e.g., 20 patterns out of 50) due to limitations in nested pagination handling. This has been resolved by improving the nested pagination logic, ensuring that all available quality insight patterns are now fully retrieved and returned in the response.
57577 An issue was identified where the tags tool that lists the tags available in an application was truncating the tags list after the first 20 tags. The issue has been fixed and the entire tags list is now displayed
57561 An issue was identified where the source_file_details was returning only the first 10 elements per type when called with the nature: "inventory". This issue has been fixed.
57186 The Imaging MCP Server was previously unable to retrieve its correct version when queried by the user. This has now been fixed.