# Caliper (remote · caliper.fit)

Geometry and CAD file metadata extraction for STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB.

- Trust score: 69/100 (medium)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `caliper.fit`: 69/100 (this document), [markdown](https://verifymcp.io/servers/fit-caliper-caliper/caliper.md), [page](https://verifymcp.io/servers/fit-caliper-caliper/caliper)

## Channel facts

- Endpoint: `https://caliper.fit/mcp/`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.1`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, and we only credit what we can confirm. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 63/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - Authorisation not fully verified: no authorisation is required to call this server, and 9 tool(s) never declared a destructiveHint. The MCP spec treats an absent hint as destructive by default, so we cannot call this surface safe.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC check failed: this domain isn't protected by DNSSEC.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 73/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 3130 tokens (~284/item across 11 items; 10 tools + 1 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 27/100
  - Stability observed for 8 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

```bash
claude mcp add --transport http fit-caliper-caliper https://caliper.fit/mcp/
```

### Codex

```toml
[mcp_servers.fit-caliper-caliper]
url = "https://caliper.fit/mcp/"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "fit-caliper-caliper": {
      "type": "remote",
      "url": "https://caliper.fit/mcp/",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add fit-caliper-caliper --url https://caliper.fit/mcp/ --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  fit-caliper-caliper:
    url: "https://caliper.fit/mcp/"
```

### Other

```json
{
  "mcpServers": {
    "fit-caliper-caliper": {
      "type": "http",
      "url": "https://caliper.fit/mcp/"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 69, +1)

No change was recorded against any check on this day. Stability & Change Management went from 23 to 27. That category is still filling its 30-day observation window: 7 days of observed history at the previous scan, 8 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 68, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-31 (score 67, 0)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 67, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 66, +1)

No change was recorded against any check on this day. Stability & Change Management went from 7 to 10. That category is still filling its 30-day observation window: 2 days of observed history at the previous scan, 3 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-07-27 (score 65, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-26 (score 64)

First indexed and scored.

## MCP tools (10)

### `format_detect` (~83 tokens)

Detect File Format

Detect 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

Input parameters:

- `filename` (string, required): Filename or URL to check. The format is detected from the file extension.

### `feature_request` (~127 tokens)

Request a Feature

Request 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

Input parameters:

- `description` (string, required): A short description of the feature or format you need. Examples: 'STEP file support', 'volume comparison between two files', 'export to USD format'. This helps prioritize development.

### `format_auto` (~501 tokens)

Auto-Detect and Analyze

Auto-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
    using file_b64. When using file_url, the format is detected from
    the URL path extension; filename is not required.

    Files under 150KB are free. Larger files cost $0.02/MB via x402
    (USDC on Base) or card via MPP (Stripe; adds $0.35 surcharge).
    If payment is required, the response includes payment details.
    Retry with the payment argument containing the payment proof.
    Privacy policy: https://caliper.fit/privacy

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_stl` (~368 tokens)

STL Analysis

Extract 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

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_obj` (~339 tokens)

OBJ Analysis

Extract 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

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_ply` (~345 tokens)

PLY Analysis

Extract metadata from a PLY file (ASCII or binary).

    Returns vertex/face counts, element properties, feature detection
    (normals, colors, texcoords, intensity, curvature), bounding box,
    centroid, and point cloud identification.

    Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto
    for payment flow details. Privacy policy: https://caliper.fit/privacy

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_pcd` (~343 tokens)

PCD Analysis

Extract metadata from a PCD point cloud file.

    Returns point count, field definitions, data format, organization,
    viewpoint, feature flags (RGB, intensity, normals, curvature),
    bounding box, centroid, and point density estimate.

    Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto
    for payment flow details. Privacy policy: https://caliper.fit/privacy

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_las` (~349 tokens)

LAS/LAZ Analysis

Extract metadata from a LAS or LAZ point cloud file.

    Returns LAS version, point format, point count, scale factors,
    offsets, bounding box, classification counts, feature flags
    (RGB, intensity, GPS time, waveform), and VLR information.

    Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto
    for payment flow details. Privacy policy: https://caliper.fit/privacy

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_gltf` (~351 tokens)

glTF/GLB Analysis

Extract metadata from a glTF or GLB file.

    Returns asset info, scene graph structure, mesh/material/texture
    counts, vertex and index totals, feature flags (normals, tangents,
    texcoords, colors, joints), primitive modes, and extensions.

    Payment via x402 (USDC on Base) or card via MPP (Stripe). See format_auto
    for payment flow details. Privacy policy: https://caliper.fit/privacy

Input parameters:

- `file_b64`: Base64-encoded file content. Max 200KB decoded. Use file_url for larger files to avoid consuming model context window budget. Default: null (omit if providing file_url instead).
- `file_url`: HTTP/HTTPS URL of the geometry file to analyze. Preferred for large files (over 200KB). The file format is detected from the URL path extension, so the filename parameter is not needed when using fil…
- `filename`: Original filename with extension (e.g. 'model.stl'). Required for format detection when using file_b64. Not needed when using file_url (format is detected from the URL path). Default: null.
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

### `format_batch` (~311 tokens)

Batch Analysis

Analyze multiple geometry files in a single batch request.

    Submit up to 10 files, receive a single quote, pay once, and get
    structured metadata for all files. Supports mixed formats. Read-only
    analysis — does not modify, convert, or repair files.

    Payment is required via x402 (USDC on Base) or card via MPP (Stripe). If no payment is provided,
    the response includes the total price and per-file breakdown. Retry
    with the payment argument containing "transaction", "network", and
    "priceToken".

    Partial success: if some files fail processing, you still receive
    results for the files that succeeded.
    Privacy policy: https://caliper.fit/privacy

Input parameters:

- `files` (string, required): JSON array of file descriptors. Each object has optional keys: "file_url" (HTTP/S URL), "file_b64" (base64 string), "filename" (for format detection). Provide either file_url or file_b64 per file. Ma…
- `payment`: Payment proof as a JSON string. Set this when retrying after a payment_required response. For x402: must contain 'transaction' (on-chain tx hash), 'network', and 'priceToken' from the payment_require…

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/fit-caliper-caliper/caliper#diagnostics

## Score history

- 2026-08-03: 69
- 2026-08-02: 68
- 2026-08-01: 68
- 2026-07-31: 67
- 2026-07-30: 67
- 2026-07-29: 66
- 2026-07-28: 65
- 2026-07-27: 65
- 2026-07-26: 64

## Links

- Remote endpoint: https://caliper.fit/mcp/
- Website: https://caliper.fit/
- Changelog RSS feed: https://verifymcp.io/servers/fit-caliper-caliper/caliper/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/fit-caliper-caliper/caliper/changelog.json
- HTML version of this page: https://verifymcp.io/servers/fit-caliper-caliper/caliper