Caliper
fit.caliper/caliper · 0.1.1
Geometry and CAD file metadata extraction for STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB.
Nobody here has read this server's code, because it publishes none. The description above is the maker's own, from the registry. A connection test shows whether it answers and what tools it says it has; it never calls a tool, so it cannot show what one does with your data.
Where it sits in the directory's order
What can be seen from outside, weighed as the directory publishes.
Observable signals: 30 of 100 points (at most 60 here)
| Input | Points | What was seen |
|---|---|---|
| Source published | held at 0 | No entry here publishes source: that is what puts it in this directory. |
| Licence stated | held at 0 | With no files, there is nothing for a licence to be stated in or held against. |
| Advisory state | held at 0 | Advisory databases index packages, and these entries publish none, so there is nothing to look up. |
| Auth declared | 0 of 15 | The registry entry declares no key. That is what it declares, not a finding that it has no protection. |
| Latest connection test reached it | 20 of 20 |
Where it answers
https://caliper.fit/mcp/streamable-http
Connection test
The MCP handshake, then a request for the tool list, with no key and no data of yours. Run nightly, and by anyone, at most once every ten minutes per server.
It completed the handshake and listed 10 tools.
- Protocol
- 2025-06-18
- Calls itself
- Caliper 0.1.0
- Handshake time
- 179 ms
- HTTP status
- 200
The tools it lists (10, as of 2 days ago)
The tool-description rules found nothing in these descriptions. They look for instructions aimed at a model and for hidden characters; they cannot see what a tool does when it runs.
format_detectDetect the geometry file format from a filename or URL. Returns the detected format name and whether it is currently supported. Use this to check format support before making a paid analysis call. No payment required. Privacy policy: https://caliper.fit/privacy
feature_requestRequest a feature or format that Caliper doesn't support yet. Free, no payment required. Use this when you need a capability that Caliper doesn't currently offer — especially unsupported file formats (STEP, IGES) or analysis features not yet available. Requests are logged and used to prioritize development. Privacy policy: https://caliper.fit/privacy
format_autoAuto-detect geometry file format and extract metadata statistics. Accepts a 3D geometry file via URL or base64 and returns structured metadata: bounding boxes, triangle counts, manifold analysis, point cloud statistics, and more. This is a read-only analysis tool — it does not perform mesh repair, format conversion, or boolean operations. Supported formats: STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB. STEP and IGES support is planned. Provide either file_url (preferred for large files) or file_b64 (for files under 200KB). Include filename for format detection if
format_stlExtract metadata from an STL file (ASCII or binary). Returns triangle count, bounding box, surface area, volume, manifold analysis (watertight, open edges, non-manifold edges), triangle quality metrics, vertex deduplication count, mean edge length, minimum bounding sphere, and a noise estimate derived from planar region fitting. Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto for payment flow details. Privacy policy: https://caliper.fit/privacy
format_objExtract metadata from an OBJ file. Returns vertex/normal/texcoord/face counts, triangle/quad/polygon breakdown, material and group counts, bounding box, surface area, and triangulation status. Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto for payment flow details. Privacy policy: https://caliper.fit/privacy
How this entry becomes a listing
For the maker. The catalogue lists what it can read, and this server publishes nothing to read yet. There are two routes, and only the first is open today.
Publish the source Open today
- Put the server's source in a public repository on github.com, with a licence.
- Keep a server.json in that repository naming this server,
fit.caliper/caliper, and declare the repository in it:"repository": { "url": "https://github.com/owner/repo", "source": "github" }, adding"subfolder"when the server lives in a folder. - Publish that version to the official MCP registry.
- The nightly registry sweep records the declaration. This page stays, dated, and says the source is declared but not yet read.
- The catalogue reads declared repositories at a pinned commit, in batches run by hand, and lists the servers that meet the batch's rules (among them a server.json at that commit naming the server, an https endpoint and a licence). When it lists this server, this page links to the listing. There is no schedule, so no date can be promised.
List it through the maker studio Not open yet
From the official MCP registry, last updated there 193 days ago. The registry entry · caliper.fit