MCP server for jPOS and ISO 8583. Deterministic payment protocol tools for AI agents.
mcp-name: io.github.mohisyed/jpos-mcp-server The first open-source MCP server for jPOS and ISO 8583. Claude validating a real ISO 8583 financial transaction request using deterministic tools. No guessing — every answer comes from verified data. An MCP server that gives AI agents (Claude, Cursor, VS Code Copilot) deterministic, verified access to ISO 8583 field specs, MTI decoding, jPOS packager…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
mcp-name: io.github.mohisyed/jpos-mcp-server The first open-source MCP server for jPOS and ISO 8583. Claude validating a real ISO 8583 financial transaction request using deterministic tools. No guessing — every answer comes from verified data. An MCP server that gives AI agents (Claude, Cursor, VS Code Copilot) deterministic, verified access to ISO 8583 field specs, MTI decoding, jPOS packager XML generation, deploy descriptor validation, message building, and jPOS documentation search. No…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.