cics-bridge-mcp

Purpose: Turning CICS mainframe records into structured evidence for SOX, PCI-DSS, and DORA compliance.

Inferred · not functionally tested

Audience: mainframe engineers, compliance teams, and AI-governance practitioners

Inferred · not functionally tested

Functions: data_extraction

Inferred · not functionally tested

Interfaces: API: indicated (inferred, not tested) · MCP: indicated (inferred, not tested) · CLI: indicated (inferred, not tested) · Self-hosting: indicated (inferred, not tested)

Recorded constraints: pricing: open_source · license: Open Source · platforms: CLI, WEB · deployment: browser, cli, self_hosted, api_only

Constraint provenance is unknown; confirm requirements with the publisher.

Record sources: github.com. These links do not verify the individual claims.

In the Frameworks & runtimes space, cics-bridge-mcp takes a focused approach. Inferred · not functionally tested: It focuses on turning CICS mainframe records into structured evidence for SOX, PCI-DSS, and DORA compliance. Inferred · not functionally tested: It is built as an open-source project for mainframe engineers, compliance teams, and AI-governance practitioners. Basis unknown · not verified: cics-bridge-mcp is open source under the Open Source license. Basis unknown · not verified: cics-bridge-mcp is available on the web, the command line, and API, and it can be self-hosted.

It is developed by CSOAI-ORG. Inferred · not functionally tested: Among its 6 catalogued features are CICS record mapping, AI-governance evidence, and SOX evidence. Inferred · not functionally tested: Catalogued interfaces include an MCP server.

Summary written by a language model from the project’s public pages.