MainframeKit
NPM · MAINFRAMEKIT-MCP
Mainframe help, no mainframe needed: check JCL and DFSORT, explain abends, lay out copybooks.
Available components
Last scanned (4 hours ago)
Scores higher than 34% of npm servers
Category Developer Tools
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security100
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency6
- Repository check failed: no source repository is declared. See how to fix → View diagnostics → Fail
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Licence could not be checked: the licence is shipped as a file inside the package, not declared as a standard (SPDX) licence identifier, so we cannot tell whether it is OSI-approved.Unverified
- Actively maintained (last published 3 days ago).Pass
- Security-disclosure policy not yet verified: we couldn't inspect the source repository.Unverified
Schema Quality & AI Usability86
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 413 tokens (~103/item across 4 items; 4 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management20
- Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 4 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 5 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 3 Nov 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 10 to 13. That category is still filling its 30-day observation window: 3 days of observed history at the previous scan, 4 at this one. The score rises as the window fills, whether or not the server changes.
- 1 Nov 26 +16
- Stability: 0.03 → unverified ▼ security
- Tool safety: pass → unverified ▼ security
- Malware scan: unverified → pass ▲ security
- Capabilities: pass → unverified ▼ functional
- Tool coverage: 100 → unverified ▼ functional
- Schema quality: 100 → unverified ▼ functional
- Package version: 0.1.2 → 0.1.3 functional
- 31 Oct 26 0
- Malware scan: unverified → pass ▲ security
- Stability: unverified → 0.03 ▲ functional
- Package version: 0.1.1 → 0.1.2 functional
- 30 Oct 26 50
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 5 Nov 2026 · Analysed npm/mainframekit-mcp@0.1.3
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 0 packages
| Packages resolved | 0 |
|---|---|
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
check_jcl Check JCL ~74
Check z/OS JCL for common mistakes (columns, continuations, DISP, SPACE, DCB, names, PARM length) and explain every JOB, EXEC and DD statement in plain English. Use before submitting or suggesting JCL.
| Name | Type | Req | Description |
|---|---|---|---|
| jcl | string | yes | The JCL, one card per line |
No output schema declared.
No examples provided.
copybook_layout COBOL copybook layout ~78
Lay out a COBOL copybook: every field's start position (1-based), length and storage type (packed, binary, zoned, text), and the record length. Handles PIC, USAGE, OCCURS, REDEFINES.
| Name | Type | Req | Description |
|---|---|---|---|
| copybook | string | yes | The copybook source (01-level record and its fields) |
No output schema declared.
No examples provided.
explain_dfsort Explain DFSORT statements ~65
Explain DFSORT / ICETOOL-style control statements (SORT, MERGE, INCLUDE/OMIT COND, INREC/OUTREC BUILD, SUM) in plain English and flag problems.
| Name | Type | Req | Description |
|---|---|---|---|
| statements | string | yes | DFSORT control statements, as in SYSIN |
No output schema declared.
No examples provided.
lookup_code Look up a mainframe error code ~119
Explain a z/OS abend (S0C7, SB37, U4038…), Db2 SQLCODE (-805, -911…), CICS abend or RESP code (ASRA, AEY9, NOTFND…) or IBM MQ reason code (2035, 2085…): meaning, causes, fixes, IBM sources and links.
| Name | Type | Req | Description |
|---|---|---|---|
| code | string | yes | The code, e.g. S0C7, 0C4, -805, SQL0805N, ASRA, 2035 |
No output schema declared.
No examples provided.
How do I install the MainframeKit MCP server?
MainframeKit runs locally as an npm package, launched with npx -y mainframekit-mcp. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · mainframekit-mcp
claude mcp add vidyutsaha1210-mainframekit -- npx -y mainframekit-mcp
What is the MainframeKit MCP server?
MainframeKit is an MCP server listed in the public MCP registry as io.github.vidyutsaha1210/mainframekit. Mainframe help, no mainframe needed: check JCL and DFSORT, explain abends, lay out copybooks. This page covers its npm package (mainframekit-mcp).
Is the MainframeKit MCP server safe to use?
MainframeKit scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 5 November 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the MainframeKit MCP server expose?
MainframeKit exposes 4 tools: check_jcl, explain_dfsort, lookup_code, copybook_layout. Their descriptions and schemas cost roughly 336 tokens of context every time the server is loaded.
Is the MainframeKit MCP server still maintained?
MainframeKit is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.