Name: SCAPS-1D
Author: asiff00

SCAPS-1D MCP

Design, simulate, fit and sanity-check thin-film solar cells with SCAPS-1D on your own installation.

Grade A Local · stdio No auth needed 16 tools v0.1.0 MIT

No reviews yet by asiff00PyPI 412 Runs on your machine, nothing hosted

93/100

trust score

downloads a day

local

runs on your machine

downloads in 30d

What it does

Design, simulate, fit and sanity-check thin-film solar cells with SCAPS-1D on your own installation.

Quickstart

# 1 — add it to Claude Code
claude mcp add --scope user scaps-1d-mcp '--' uvx scaps-mcp

# 2 — ask your agent for something these tools do
#   scaps_status, scaps_list_files, scaps_script_reference and 13 more

SCAPS-1D costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.

Publishernot claimed

asiff001 server

1 category

All 1 server

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 SCAPS-1D 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.

Claude Codedeclared by this listing

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 scaps-1d-mcp '--' uvx scaps-mcp

Reconnect, or start a new session, and the tools appear in the model’s tool list.

Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.

What it asks of you

Nothing is required, but it can take SCAPS_HOME (SCAPS installation folder, the one that contains scapsXXXX.exe; found automatically in the usual locations when unset), SCAPS_TIMEOUT (Seconds allowed per SCAPS run), SCAPS_RUNS_DIR (Folder that keeps run inputs and results; defaults to the user cache folder) if you want to set them.

What it writes

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.

What you approve

16 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.

Only tools that write or reach the network

Read from its source code. A server that builds its tool list when it starts can list more tools than this.

Report the SCAPS installation in use and how it was found, other installations, run folder and jobs.

Takes no parameters.

List files in a SCAPS data folder: definitions, spectra, absorption, grading, generation and more.

Parameter	Type	Required	Notes
kind		no	SCAPS data folder to list.
contains	string	no	Case-insensitive substring filter.
limit	integer	no	—
offset	integer	no	—

Search the command list of the installed SCAPS version.

Parameter	Type	Required	Notes
query	string	yes	Words to match, e.g. 'defect Ntotal' or 'action qe'.
limit	integer	no	—

Read a .def file: layers, bulk defects, interfaces with band offsets, contacts and realism checks.

Parameter	Type	Required	Notes
definition		yes	—

Change a device and save it as a .def file: parameters, layers, defects, materials and solver settings.

Parameter	Type	Required	Notes
base	string	yes	Existing definition to start from.
save_as	string	yes	New definition name, saved in SCAPS def/.
operations	object	no	Ordered set commands, including structural ones: 'layer2.duplicate', 'layer3.remove', 'layer1.defect1.duplicate', 'layer1.defect2.gauss', 'interface1.2_default_IFdefects', 'layer1.Eg.file': 'profile.g
materials	object	no	Load .material files into layers before the operations, e.g. {1: 'CIGSe.material'}.
numerics		no	—
overwrite	boolean	no	Replace an existing file of that name.

Build a new device from scratch and save it as a .def file.

Parameter	Type	Required	Notes
name	string	yes	New definition name, saved in SCAPS def/.
layers	array	yes	Layers from the left (back) contact. Each maps set-command suffixes to values, e.g. {'name': 'absorber', 'thickness': 0.5, 'Eg': 1.55, 'chi': 3.9, 'epsilon': 10, 'NC': 2.2e18, 'NV': 1.8e19, 'mun': 2,
interfaces	object	no	Interface defects by interface number (1 lies between layers 1 and 2), up to 3 each, e.g. {1: [{'Ntotal': 1e10, 'singledonor': null}]}.
left_contact	object	no	e.g. {'workfunction': 5.1, 'Sn': 1e5, 'Sp': 1e7}; a work function switches flat band off.
right_contact	object	no	As left_contact.
options	object	no	Other set commands, e.g. {'illumination.fromleft': null, 'numerical.Shockley-Queisser_limit.always': null}.
numerics		no	—
overwrite	boolean	no	—

Simulate a device: J-V metrics, QE, C-V, C-f and spatial profiles, with analysis and realism checks.

Parameter	Type	Required	Notes
definition		yes	—
measurements		no	—
profiles		no	—
parameters		no	—
actions		no	—
illumination		no	—
temperature_k		no	—
voltage_v		no	—
frequency_hz		no	—
spectrum		no	—
response_format	string	no	detailed adds the key columns of each curve.
wait_seconds		no	—

Run one SCAPS session over many parameter values and tabulate the J-V metrics of every point.

Parameter	Type	Required	Notes
definition		yes	—
variables	object	yes	Set or action keys and their values, e.g. {'layer1.thickness': [0.3, 0.5, 1]} or {'workingpoint.temperature': [280, 300, 320], 'intensity.ND': [0, 1, 2]}.
mode	string	no	grid runs every combination; zip pairs the lists element-wise.
measurements		no	—
profiles		no	—
parameters		no	—
actions		no	—
illumination		no	—
temperature_k		no	—
spectrum		no	—
wait_seconds		no	—

List recent runs, or get, wait for or cancel one. A finished job includes its full result.

Parameter	Type	Required	Notes
action	string	no	What to do.
job_id	string	no	Job (run) id for status, wait and cancel.
wait_seconds		no	—
limit	integer	no	—

Return one table of a result file: J-V, QE, C-V, C-f curves or band, generation and AC profiles.

Parameter	Type	Required	Notes
run_id	string	yes	Run id from scaps_simulate, scaps_batch or scaps_run_script.
file	string	no	Result file of the run; omit to list the files.
table	string	no	Table title ('bulk', 'interface') or index; default the main table.
columns	array	no	Columns to keep; default all.
offset	integer	no	—
max_rows	integer	no	—
step	integer	no	Keep every n-th row to thin long profiles.

Render result curves as a PNG image. Requires the optional 'plot' extra.

Parameter	Type	Required	Notes
run_id	string	yes	Run id.
files	array	yes	Result files of the run to overlay.
x	string	no	X column; default the natural axis of the file type.
y	array	no	Y columns; default the key column of the file type.
table	string	no	Table title or index, as in scaps_results.
log_x	boolean	no	—
log_y	boolean	no	—
title	string	no	—
width_px	integer	no	—

Run a SCAPS script for workflows beyond the other tools: recorder, curve fitting, math, loops, tandem.

Parameter	Type	Required	Notes
script	string	yes	SCAPS script text, one command per line.
validate_only	boolean	no	Only check the script and report problems.
timeout_s	number	no	Override SCAPS_TIMEOUT.
wait_seconds		no	—

Detailed-balance Jsc, Voc, FF and efficiency limits for given band gaps under a SCAPS spectrum.

Parameter	Type	Required	Notes
band_gaps_ev	array	yes	Band gaps in eV.
temperature_k	number	no	—
spectrum		no	—

Add a SCAPS file someone shared (device .def, .material, .abs, spectrum, measurement...) to the installation.

Parameter	Type	Required	Notes
kind		yes	File type; decides the SCAPS folder.
name	string	yes	File name with its SCAPS extension, e.g. 'perovskite cell.def'.
content	string	yes	Full text of the file.
overwrite	boolean	no	—

Write numeric data as a SCAPS input file with the right format and units.

Parameter	Type	Required	Notes
kind	string	yes	Input file type.
name	string	yes	File name; the SCAPS extension is added if missing.
x	array	yes	absorption: wavelength or photon energy (x_unit); spectrum, filter: wavelength nm; generation: position um; grading: position um, relative position or composition; measurement: V (iv, cv), Hz (cf) or
y	array	yes	absorption: alpha or k (see quantity); spectrum: W/m2/nm or W/m2 per point; generation: G; filter: % transmission or reflection; grading: property in script units; measurement: mA, nF or QE %.
quantity	string	no	absorption: alpha_per_cm (default), alpha_per_m or k; spectrum: irradiance_w_m2_nm (default) or power_w_m2; generation: per_cm3_s (default) or per_m3_s; grading: the property, e.g. composition, Eg, NA
x_unit	string	no	absorption only: unit of x, wavelength or photon energy.
extra	array	no	measurement only: conductance G in S.
position	string	no	grading only.
interpolation	string	no	grading only.
shared	boolean	no	grading only: one profile over adjacent layers.
normalise_w_m2	number	no	spectrum only: scale total power.
area_cm2	number	no	measurement only.
temperature_k	number	no	measurement only.
bias_v	number	no	measurement only.
frequency_hz	number	no	measurement only.
pin_mw_cm2	number	no	measurement only.
dark	boolean	no	measurement only.
note	string	no	Source or description, written as comment lines.
overwrite	boolean	no	—

Fit device parameters to measured curves, or optimise efficiency, Voc, Jsc or FF, by bounded Nelder-Mead.

Parameter	Type	Required	Notes
definition		yes	—
variables	object	yes	Set or action keys to vary with bounds, e.g. {'layer1.defect1.Ntotal': {'min': 1e12, 'max': 1e16, 'log': true}, 'layer2.thickness': {'min': 0.03, 'max': 0.12, 'start': 0.05}}.
goal	string	yes	fit measured curves, maximise or minimise a J-V metric, or reach a target value.
metric	string	no	Metric for maximize, minimize and target.
target	number	no	Target value of the metric for goal 'target'.
measured	array	no	For fit: curves to match together, e.g. [{'kind': 'iv', 'file': 'Numos Ex 1 light.iv'}, {'kind': 'iv', 'x': [...], 'y': [...], 'illumination': 'dark', 'log': true, 'weight': 1}]. Files come from SCAPS
parameters		no	—
actions		no	—
temperature_k		no	—
spectrum		no	—
max_evaluations	integer	no	—
wait_seconds		no	—

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

Nothing here is billable: mcprush charges nothing to install SCAPS-1D or to call it, at any volume.

ATrust score 93 / 100

Release 0.1.0 · scanned 28 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

Findings3 threat · 4 capability

Capabilityhigh

Coveragesource

Verificationrepo

Surface digeste73e12d06c3eb863882637dcbc572c3e0a0009a45d48d8175e424799c918aedb

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 (16 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
scaps_status	no tags
scaps_list_files	sensitive-source	sensitive-source: keyword "list_files"
scaps_script_reference	no tags
scaps_describe_device	no tags
scaps_edit_device	no tags
scaps_create_device	no tags
scaps_simulate	no tags
scaps_batch	no tags
scaps_jobs	no tags
scaps_results	no tags
scaps_plot	no tags
scaps_run_script	code-exec	code-exec: keyword "run_script" in tool name, parameter "script"
scaps_sq_limit	no tags
scaps_import_file	no tags
scaps_write_data	no tags
scaps_optimize	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.

scaps_list_files → scaps_run_script

A sensitive-source → external-sink chain exists: scaps_list_files → scaps_run_script.

Supply chain and provenance

Integrityfirst-seen

Surface digeste73e12d06c3eb863

Scanned2026-10-28

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.