An MCP server that connects to Vercel API
Zcrafter Bridge is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
What it does
IBM z/OS mainframe tools for AI agents. Every change needs a person's approval.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user zcrafter-bridge-mcp '--' uvx zcrafter-bridge
# 2 — ask your agent for something these tools do
# start_request, record_clarification, draft_spec and 7 more
Zcrafter Bridge costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts Zcrafter Bridge as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user zcrafter-bridge-mcp '--' uvx zcrafter-bridgeReconnect, or start a new session, and the tools appear in the model’s tool list.
Nothing is required, but it can take MAINFRAME_WORKFLOW_ZOWE_PROFILE (Zowe z/OSMF profile to use. Defaults to the profile named default.), ZOWE_OPT_HOST (z/OSMF host, when not using a Zowe profile.), ZOWE_OPT_USER (Mainframe user ID, when not using a Zowe profile.), ZOWE_OPT_PASSWORD (Mainframe password, when not using a Zowe profile.), MAINFRAME_WORKFLOW_READ_ONLY (Set to true to offer no tool that changes anything.), MAINFRAME_WORKFLOW_PROTECTED_DATASETS (Comma-separated dataset patterns nothing may write to, e.g. SYS1.**,*.PROD.**) if you want to set them.
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
10 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
Begin a new mainframe request. Phase starts at CLARIFYING.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| raw_request | string | yes | — |
Log one clarifying question/answer pair against an active request.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| question | string | yes | — |
| answer | string | yes | — |
Write a new spec revision. Editing an already-approved spec un-approves it (and any approved plan).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| content | string | yes | — |
Ask the person to approve the latest spec revision. The server shows them the spec and waits for their answer; this call cannot approve anything by itself. If it returns WAITING_FOR_PERSON, tell the person an approval is waiting and call it again.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
Write a new plan revision. Requires an approved spec. Editing an approved plan un-approves it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| content | string | yes | — |
| steps | array | no | — |
Ask the person to approve the latest plan revision and its steps. The server shows them the plan and waits for their answer; this call cannot approve anything by itself. Once approved, the mutating tools run for this request, but only the steps the plan lists. If it returns WAITING_FOR_PERSON,…
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
Abandon an active request from any phase. Fails if the request is already ABANDONED or COMPLETED.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
| reason | string | yes | — |
Mark a request completed once its work is done. Requires an approved plan.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
Return full detail for a request: phase, status, clarifications, spec/plan text, the plan's steps and which are left, approvals, recent actions.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| request_id | string | yes | — |
List requests filtered by status (default ACTIVE).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| status | string | no | — |
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install Zcrafter Bridge or to call it, at any volume.
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tools were statically extracted from the published source (10 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
The source has registrations with unknown names: the tools registered at mainframe_workflow_mcp/proxy.py:125 get their names only at run time (a loop over a list the code builds, a name it computes), so they are not in this surface and were not analysed. To see them, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| start_request | no tags | |
| record_clarification | no tags | |
| draft_spec | no tags | |
| approve_spec | no tags | |
| draft_plan | no tags | |
| approve_plan | no tags | |
| cancel_request | no tags | |
| complete_request | no tags | |
| get_request_status | no tags | |
| list_requests | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.3.1. Pin a release below and the command asks for exactly that one.
No release note was published with this version.
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Any signed-in account that does not publish Zcrafter Bridge can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.