VoxelSieve MCP server
io.github.yoshi5534/voxelsieve·v0.5.0·1 starsAnalyse industrial CT scans locally: porosity, CAD comparison and inspection reports
1 stars
Reviews
Write oneNobody has reviewed VoxelSieve yet.
If you have run it, two minutes of your experience saves the next person an afternoon.
VoxelSieve tools
No tool declarations could be read from the package source. They show once the server is installed.
Public scan report
scanner v0.1.10 · 2026-10-28 · same rubric, same numbers if you re-run it
- –Code scanpackage could not be scannedn/a
- –Live reliabilityno gateway calls yet and no remote to proben/a
- –Tool poisoningtools not inspected (local package is not executed); not countedn/a
- Auth qualitylocal package, no credentials required12/15
- Maintenancelast push 2 days ago15/15
- Maintainer identityregistry namespace matches repository owner; GitHub account older than a year8/10
How VoxelSieve compares
Against every graded MCP server, from our own scans and uptime checks. Updated after each scan run.
- Safety score
- 88/100
- higher than 75% of 48,255 servers
- GitHub stars
- 1
- more than 65% of 28,688 servers
Install VoxelSieve in Claude Code, Cursor or VS Code
The registry entry has no remote endpoint or installable package.
What the publisher says
From the VoxelSieve repository's README, as published. We do not edit it. Read it on GitHub
VoxelSieve
Open-source tooling for industrial CT volumes, built on OpenVDB.
Reconstructed CT volumes are large, uncompressed raw files in which most voxels are air. VoxelSieve separates the surrounding air from the part, keeps internal voids such as pores, and stores the result as a sparse, bricked VDB dataset that works for scans larger than memory. On top of it, it finds pores and loosened microstructure and writes an inspection report.
All images of the porosity analysis come from one synthetic scan of the sample bell housing, 765 × 765 × 380 voxels of 0.1 mm (445 MB), with the shrinkage cavities and loosened zones where a casting solidifies last: vs-synth --part bellhousing --voxel-size 0.1 --hot-spots --lunker 12 --lunker-radius 0.9 --lunker-spread 0.6 --loosening 3 --loosening-radius 1.5 --noise 500 --cupping 0.08 --blur 0.07 --seed 12. Every lunker volume is found within 2 % of the ground truth (the smallest, 0.06 mm³, within 4 %), the zones deep in the flanges within 2 % and those just below the surface within 10 %, and the part volume within 0.02 %.
Status: early development, latest release 0.3.1 (see CHANGELOG.md). New here? The quickstart takes you from download to a porosity report with an AI assistant, using sample data. The tools:
Build
Dependencies come from vcpkg, pinned in vcpkg.json. On Ubuntu 24.04:
sudo apt-get install cmake ninja-build g++ git curl zip unzip tar autoconf automake libtool pkg-config
tools/setup-vcpkg.sh && export VCPKG_ROOT=~/vcpkg
cmake --preset release && cmake --build --preset release && ctest --preset release
./build/release/apps/vs-phantom/vs-phantom --out phantom --dims 256Shortened. The full README is on GitHub.
Nothing above is checked by us. What we check is on the safety report.
VoxelSieve: common questions
- Is VoxelSieve MCP server safe?
- Yes, by our scan: it is graded A (88/100). Read the VoxelSieve safety report
- Does VoxelSieve need an API key?
- Not as far as the registry entry and our scan can tell: no credentials are declared or required.
- Is VoxelSieve maintained?
- The last commit was 10 days ago (2026-10-25). The latest release is v0.5.0.
- How does VoxelSieve compare with other MCP servers?
- safety score 88/100 (higher than 75% of 48,255 servers); github stars 1 (more than 65% of 28,688 servers). Full comparison.