Pack local or remote codebases into AI-friendly files that LLMs and coding agents can read or search
Nothing to run from here
MAX+plus II MCP / Digital Circuit AI Tool 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.
93/100
trust score
21
tools declared
local
runs on your machine
28
downloads
What it does
MAX+plus II / MaxPlus2 MCP: GDF/SYM/SCF, compile/simulation. Schematic, waveform, compilation simulation and Windows automation.
Quickstart
This one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Publishernot claimed
HAAll 1 server
Hachimeder1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
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 MAX+plus II MCP / Digital Circuit AI Tool 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 one is not published to a package registry, so there is no one-line install: it is built and started the way its own source says.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
Return precise routes and runtime requirements for authoring, compilation, simulation and native GUI-only workflows. Distinguishes implemented entry points from operations verified on this machine and physical programming requirements.
No parameter schema on file.
Compose an evidence-driven MAX+plus II task using files, CLI and native GUI.
No parameter schema on file.
User-authorized design task.
No parameter schema on file.
Locate the MAX+PLUS II installation (maxplus2.exe / setacf.exe), report version info from maxplus2.ini, available device families, and additional bundled tools. Read-only.
No parameter schema on file.
Recursively find .acf projects under a root directory and list the artifacts already compiled for each. Read-only.
No parameter schema on file.
Summarize one project: .acf sections, CHIP blocks, device, pin count, compiled artifacts with timestamps, and the cleanliness of the last .rpt. Read-only.
No parameter schema on file.
Read the .acf as structured sections/entries with line numbers. Use to discover which section holds a setting before writing. Read-only.
No parameter schema on file.
Extract device and pin assignments from the .acf CHIP block, and cross-check them against the compiler-generated .pin report when present. Read-only.
No parameter schema on file.
Build the exact setacf.exe argument vector for a change WITHOUT executing it. Always call this first: setacf edits the .acf in place and has no dry-run mode.
No parameter schema on file.
Execute a setacf change. Backs the .acf up first and returns a line diff. Requires confirm:true. Prefer calling setacf_plan first.
No parameter schema on file.
Build the exact maxplus2.exe command line for compile / timing analysis / simulation / object conversion, WITHOUT running it.
No parameter schema on file.
Execute maxplus2.exe (compile / simulate / timing / convert) with a hard timeout, then report which artifacts changed and the parsed report summary. Beware: this starts a 2002-era Win32 process that can block on modal dialogs.
No parameter schema on file.
Statically validate an .acf for defects that block compilation, notably the bare "CHIP " header that setacf itself creates when no CHIP section exists yet (MAX+PLUS II then fails with "Missing identifier after section keyword"). Read-only.
No parameter schema on file.
Rewrite malformed CHIP headers (bare "CHIP " or shell-escaped names) into canonical "CHIP <name>" form. setacf is append-only and cannot fix these itself. Preview-first; requires confirm:true to write and backs the file up.
No parameter schema on file.
Run maxplus2 -v (or -h) to verify the 2002-era binary actually starts and returns on this host. Read-only and project-independent. Run this before trusting any headless compile loop: MAX+PLUS II can block forever on a modal dialog.
No parameter schema on file.
Run the Simulator headless and return the parsed result table, then optionally check expected output values. This is how simulation verification is automated: MAX+PLUS II writes a plain-text .tbl containing the simulated outputs, so a design can be checked without a human reading a waveform. Note…
No parameter schema on file.
Parse an existing MAX+PLUS II Simulator result table (.tbl) into a time-indexed trace of inputs, outputs and buried nodes, with optional expected-value checking. Read-only.
No parameter schema on file.
Parse a MAX+PLUS II .rpt / .summary / .pin file into structured severity counts, statuses, device, and diagnostics. Read-only.
No parameter schema on file.
Read a strictly validated GDF/SYM schematic summary: labels, fonts, title fields and geometry counts. gdf_geometry provides paginated original coordinates, definitions, instances and world pin positions; gdf_edit supports existing v6 geometry. Electrical connectivity requires netlist_export.…
No parameter schema on file.
Poll a background job started with async:true. Returns running/done/failed/cancelled, how long it has been going, how many child processes are live, and the full result once it settles. This exists because a client timeout is wall-clock and does NOT stop the work: polling is the only way to keep a…
No parameter schema on file.
Terminate a running background job by killing its child process. Use this rather than abandoning a job: an abandoned job keeps running and keeps holding the project directory. Build artifacts already written are left in place — this stops work, it does not undo it.
No parameter schema on file.
Free
$0 forever
- 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 MAX+plus II MCP / Digital Circuit AI Tool or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 93 / 100
Release 0.10.3 · scanned 14 Oct 2026
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.
Threat score100
Client score93
Findings10 threat · 0 capability
Capabilityhigh
Coveragesource
Verificationrepo
Surface digest04b44d2817c1327a581e9c95006b2d41eb199aed47aecbb15f205dd3f543f469
Score vectorthreat 100 → client 93
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
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.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (19 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>".
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 |
|---|---|---|
| installation_status | no tags | |
| list_projects | no tags | |
| project_inspect | no tags | |
| acf_read_sections | no tags | |
| acf_read_pins | no tags | |
| setacf_plan | no tags | |
| setacf_apply | state-write | state-write: declares readOnlyHint: false |
| maxplus2_plan | no tags | |
| maxplus2_run | state-write | state-write: declares readOnlyHint: false |
| acf_validate | no tags | |
| acf_repair_chip_headers | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| probe_executable | state-write | state-write: declares readOnlyHint: false |
| simulate_and_verify | state-write | state-write: declares readOnlyHint: false |
| parse_tbl | no tags | |
| parse_report | no tags | |
| gdf_inspect | no tags | |
| job_status | no tags | |
| job_cancel | state-write | state-write: declares readOnlyHint: false, destructiveHint: true |
| capability_matrix | 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
Integrityfirst-seen
Surface digest04b44d2817c1327a
Scanned2026-10-14
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
It installs from its repository rather than from a versioned package, so the command cannot be pinned to a release. The history below is for reading; the current release on file is 0.10.3.
0.10.3
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
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.
Sign in to write one
Any signed-in account that does not publish MAX+plus II MCP / Digital Circuit AI Tool can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
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.