Lcf Strain Life MCP Server
lcf-strain-life
PyPI
v0.2.0
Published by dfieser — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.
Material-agnostic Low Cycle Fatigue (LCF) strain-life analysis: core library + MCP server.
The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.
1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:
The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.
2. Client adoption risk — 100 − 1 = 99. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:
| Points | Adoption-risk factor |
|---|---|
| −1 | publisher verification (public source) — no provenance, but the source is public and inspectable |
Capability observations and info notes are shown under Findings but never scored.
Open any row's finding below for the file, line and evidence behind a deduction.
Findings 1
low Shell/command execution in packaging/dev tooling (scripts/build_gui_app.py)MTC-SRC-002
In a packaging/dev/install script (shipped, but not the server runtime) (`scripts/build_gui_app.py:108`): Spawning a shell/process is command-execution capability; with unsanitized tool input it is command injection / RCE. This is read from the code itself — not from the tool description — so a poisoned server cannot hide it behind honest-looking metadata.
Evidence: ".join(cmd)) return subprocess.call(cmd, cwd=ROOT) if __name__ == "__main__": raise SystemExit(main())
Fix: Review this call path: confirm it never receives unsanitized tool input, constrain it, or remove it. Treat a server whose code reaches these sinks as high-capability regardless of what its tools claim.
Location: server scripts/build_gui_app.py
Tools 41
Each tool and what it can reach — statically extracted from the published source.
analyze_staircaseno sensitive capabilityanalyze_test_csvno sensitive capabilityanalyze_test_seriesno sensitive capabilityanalyze_test_timeseriesno sensitive capabilitycompute_basis_valueno sensitive capabilitycompute_creep_fatigueno sensitive capabilitycompute_damageno sensitive capabilitycompute_frequency_modified_lifeno sensitive capabilitycompute_multiaxial_parameterno sensitive capabilitycompute_notch_localno sensitive capability
Show 31 more tools ↓
compute_roughness_factorno sensitive capabilitycompute_size_factorno sensitive capabilitycompute_sn_lifeno sensitive capabilitycompute_spectrum_lifeno sensitive capabilitycount_level_crossingsno sensitive capabilitycount_peaksno sensitive capabilitycount_rainflowno sensitive capabilityestimate_strain_life_constantsno sensitive capabilityexport_materialno sensitive capabilityfit_design_curveno sensitive capabilityfit_mean_stress_relaxationno sensitive capabilityfit_random_fatigue_limitno sensitive capabilityfit_ratcheting_lawno sensitive capabilityfit_strain_lifeno sensitive capabilityfit_strain_life_mlno sensitive capabilityflag_outliersno sensitive capabilitygenerate_reportno sensitive capabilityget_citationsno sensitive capabilityimport_materialno sensitive capabilitylist_resultsno sensitive capabilitymean_stress_equivalent_stressno sensitive capabilitypredict_lifeno sensitive capabilitypreview_lab_fileno sensitive capabilityratcheting_penalized_lifeno sensitive capabilityrecall_resultno sensitive capabilityrender_plotno sensitive capabilitysearch_critical_planeno sensitive capabilitysearch_critical_plane_tensorno sensitive capabilitysimulate_variable_amplitudeno sensitive capabilitysummarize_collectionno sensitive capabilityvalidate_interchangeno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (41 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>".
Versions 2
Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v0.2.0 latest |
A 99/100 | 1 | 1.13.0 | 2026-08-25 |
v0.1.1 |
A 99/100 | 0 | 1.9.0 | 2026-07-23 |
Embed this score
Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.
Verify this score yourself
The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.
npx mcptrustchecker scan lcf-strain-life --online --registry pypiMore in Learning & Documentation
stdio compatibility bridge for the hosted AgentMail MCP server
MCP server for Alfa documentation retrieval
MCP server providing Alpine.js documentation and reference
Search the official Astro framework documentation.
MCP server providing ATAG 2.0 (Authoring Tool Accessibility Guidelines) guidance for authoring tool developers
Aurais Research Reader as an MCP server — paste a paper or article, get a structured read with verbatim-verified quotes + a signed Vorion proof chain (via @vorionsys/aurais-core).