Skip to content

Caliper

by caliper.fit · remote · no sign-in to list tools · v0.1.1 · published by fit.caliper

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

Changes · 9

10 tools: 9 change things and 1 only read.

Scanned Oct 21, 2026

8 checks matched something in the tool definitions. No finding is not a safety guarantee. How the checks work.

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

Findings

Matches of fixed checks, with the text they matched.

8 info
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
Show 2 more findings
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for
  • The input schema at properties.payment.description mentions "credential".

    Matched text

    inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

    What this check looks for

Tools

Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.

10 tools

Changes things 9Claude Code: ask
  • feature_requestRequest a feature or format that Caliper doesn't support yet.No findings

    Why it is in this group

    • The name "feature_request" says "request": a word for a change.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: false
    • destructiveHint: false
    • idempotentHint: false
    • openWorldHint: false
  • format_autoAuto-detect geometry file format and extract metadata statistics.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • format_detectDetect the geometry file format from a filename or URL.No findings

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: false
  • format_gltfExtract metadata from a glTF or GLB file.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • format_lasExtract metadata from a LAS or LAZ point cloud file.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • format_objExtract metadata from an OBJ file.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • format_pcdExtract metadata from a PCD point cloud file.1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • format_plyExtract metadata from a PLY file (ASCII or binary).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
  • format_stlExtract metadata from an STL file (ASCII or binary).1 finding

    Why it is in this group

    • Nothing in its name or description says what it does, so it is counted as a write.
    • The server marks it read-only (readOnlyHint: true), but an annotation never lowers a class.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true
Only reads 1Claude Code: allow
  • format_batchAnalyze multiple geometry files in a single batch request.1 finding

    Why it is in this group

    • The description's first verb is "analyze": a word for reading.

    Findings

    • Info

      The input schema at properties.payment.description mentions "credential".

      Matched text

      inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."

      What this check looks for
    Description, as the server wrote it
    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

    Annotations the server declares

    • readOnlyHint: true
    • idempotentHint: true
    • openWorldHint: true

This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.

Install

Pinned to version 0.1.1. Values in angle brackets are yours to fill in.

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

Run in a terminal.

Claude Code permissions

Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.

.claude/settings.json
{
  "permissions": {
    "allow": [
      "mcp__caliper__format_batch"
    ],
    "ask": [
      "mcp__caliper__format_detect",
      "mcp__caliper__feature_request",
      "mcp__caliper__format_auto",
      "mcp__caliper__format_stl",
      "mcp__caliper__format_obj",
      "mcp__caliper__format_ply",
      "mcp__caliper__format_pcd",
      "mcp__caliper__format_las",
      "mcp__caliper__format_gltf"
    ],
    "deny": []
  }
}

Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as caliper. Review it before you use it.