io.github.bikemeardsley/thicken
NPM · THICKEN
Photos in: a 3D model at the object's real size and its metadata as JSON, for any kind of object.
Available components
Last scanned (3 hours ago)
Scores higher than 39% of npm servers
Category Design and Media
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security99
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 36 of 153 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 2 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (good).Pass
- Context-footprint check failed: tool/resource definitions use about 596 tokens (~298/item across 2 items; 2 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 2 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 2 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
Unverified: 1 category
A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.
Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 15 Oct 26 +30
- Injection markers: unverified → pass ▲ security
- First check of Judged manipulation: pass security
- Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
- Tool coverage: unverified → 100 ▲ functional
- MCP protocol: unverified → pass ▲ functional
- First check of Schema quality: fail functional
- First check of Destructive annotations: pass functional
- First check of Schema quality: fail functional
- First check of Schema quality: good functional
- First check of Tool coverage: 100 functional
- 14 Oct 26 39
First indexed and scored.
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 17 Oct 2026 · Analysed npm/thicken@0.1.0
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 153 packages
| Packages resolved | 153 |
|---|---|
| Stale | 36 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
thicken_make Make a 3D model with thicken ~522
Turns photos of one real object (or artwork, or words, or a book's ISBN) into two files that belong together: a GLB model at the object's real size, in millimeters, and its metadata as JSON, read off it by vision models and looked up in public catalogs (thicken_profiles lists each kind of object and the metadata it records). Writes both files and returns their paths and the main facts. Photos need not be cropped when a vision roster is set up (THICKEN_VISION_URL, THICKEN_VISION_MODELS); without one, give straight-on photos cropped to the object, and name the profile. One object a call: for several, call once each.
| Name | Type | Req | Description |
|---|---|---|---|
| depth_mm | number | – | A badge's or lettering's thickness in millimeters |
| holder | string | – | A graded slab's holder: psa, psa-thick, psa-tall, bgs, cgc, cgc-tall, sgc or tag |
| inputs | array | – | Absolute paths of the photos (JPEG, PNG, HEIC, WebP, AVIF, GIF, TIFF, SVG), scanner PDFs or videos (MOV, MP4) of one object, in any order and named anything. For the lettering profile, the words inst… |
| isbn | string | – | A book's ISBN, 10 or 13 digits: its size and catalog record are looked up |
| out | string | – | Where to write the GLB (an absolute path ending in .glb); the sidecar goes beside it as .json, never over a .json that isn't a thicken sidecar. Default: beside the first picture, named after it |
| preview | boolean | – | Also draw <name>.preview.png, both sides of the model (needs Chrome or Edge installed) |
| profile | string | – | The kind of object, if known; else thicken works it out from a code on it (an ISBN barcode, a grader's QR code) or the vision models. thicken_profiles lists them |
| pt | number | – | A thick trading card's thickness in points (thousandths of an inch: 55, 75, 100, 130, 180) |
| size_mm | object | – | The object's real size in millimeters, any part of it, where measured: it outranks every lookup and estimate |
| width_mm | number | – | A badge's or lettering's width in millimeters |
No output schema declared.
No examples provided.
thicken_profiles The kinds of object thicken makes ~74
Lists thicken's profiles: each kind of object it can make into a 3D model at its real size, what it is made from, what it makes, and what the vision models read off it. Call it to choose a profile for thicken_make, or to tell the user what thicken can make.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
How do I install the io.github.bikemeardsley/thicken MCP server?
io.github.bikemeardsley/thicken runs locally as an npm package, launched with npx -y thicken. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · thicken
claude mcp add bikemeardsley-thicken -- npx -y thicken
What is the io.github.bikemeardsley/thicken MCP server?
io.github.bikemeardsley/thicken is an MCP server listed in the public MCP registry as io.github.bikemeardsley/thicken. Photos in: a 3D model at the object's real size and its metadata as JSON, for any kind of object. This page covers its npm package (thicken).
Is the io.github.bikemeardsley/thicken MCP server safe to use?
io.github.bikemeardsley/thicken scores 69 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the io.github.bikemeardsley/thicken MCP server expose?
io.github.bikemeardsley/thicken exposes 2 tools: thicken_profiles, thicken_make. Their descriptions and schemas cost roughly 596 tokens of context every time the server is loaded.
Is the io.github.bikemeardsley/thicken MCP server still maintained?
io.github.bikemeardsley/thicken is still listed as active in the MCP registry. We last reached this channel on 17 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the io.github.bikemeardsley/thicken MCP server under?
io.github.bikemeardsley/thicken declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.