Scaffold Python projects from YAML presets, augment existing projects with CI/tests.
A meta-tool for scaffolding Python projects with configurable YAML presets. Supports Poetry, uv, and setuptools, generates CI workflows, testing scaffolds, type checking configs, and more. mcp-name: io.github.KaiErikNiermann/pypreset Preset-based project creation from YAML configs with single inheritance Augment existing projects with CI workflows, tests, Docker, documentation, and more Three…
Inferred from the transports this listing declares (stdio). A client not listed here hasn’t been ruled out — it just isn’t something Forge can confirm.
Verification confirms publisher identity (repo ownership), not code safety. The security scan covers known CVEs and suspicious install scripts.
Forge read 0 source files from the published package tarball and matched no MCP tool registrations. Extraction is pattern-based over shipped source: a server that builds its tool list at runtime, or that ships only bundled or minified code, registers nothing this can see. Treat it as “not detected”, not as “exposes none”.
A meta-tool for scaffolding Python projects with configurable YAML presets. Supports Poetry, uv, and setuptools, generates CI workflows, testing scaffolds, type checking configs, and more. mcp-name: io.github.KaiErikNiermann/pypreset Preset-based project creation from YAML configs with single inheritance Augment existing projects with CI workflows, tests, Docker, documentation, and more Three package managers: Poetry, uv (PEP 621 + hatchling), and setuptools (PEP 621 + setuptools.build_meta)…
Forge's dependency resolver reads npm metadata only, so this PyPI package has no resolved tree. That is a gap in coverage, not a clean bill of health.