Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

Caliper

REMOTE · CALIPER.FIT · SCANNED SEP 20

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

Available components

remote · caliper.fit 81
0 this week 81 Trust /100
Trust breakdown (7 categories)

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. How we score → Why this is hard to score →

Endpoint Security63
Transport & Reachability100
Schema Quality & AI Usability75
  • 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
  • AI-judged instruction clarity (excellent).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management100
  • No destabilizing schema changes in the last 30 days.Pass
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 10 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 11 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
Install

How do I install the Caliper MCP server?

Caliper is a hosted endpoint at https://caliper.fit/mcp/, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

remote · caliper.fit

# add to Claude Code
claude mcp add --transport http fit-caliper-caliper 'https://caliper.fit/mcp/'
// .cursor/mcp.json
{
  "mcpServers": {
    "fit-caliper-caliper": {
      "url": "https://caliper.fit/mcp/"
    }
  }
}
// .vscode/mcp.json
{
  "servers": {
    "fit-caliper-caliper": {
      "type": "http",
      "url": "https://caliper.fit/mcp/"
    }
  }
}
# ~/.codex/config.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
    }
  }
}
# add to OpenClaw
openclaw mcp add fit-caliper-caliper --url 'https://caliper.fit/mcp/' --transport streamable-http
# ~/.hermes/config.yaml
mcp_servers:
  fit-caliper-caliper:
    url: "https://caliper.fit/mcp/"
// ~/.netclaw/config/netclaw.json
{
  "McpServers": {
    "fit-caliper-caliper": {
      "Transport": "http",
      "Url": "https://caliper.fit/mcp/"
    }
  }
}
# add to Vellum
assistant mcp add fit-caliper-caliper -t streamable-http -u 'https://caliper.fit/mcp/'
// mcp.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 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.

  • 26 Aug 26 +1
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 25 Aug 26 0
    • Stability: 0.97 → pass security
  • 24 Aug 26 +1

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

  • 11 Aug 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 7 Aug 26 0
    • The server no longer declares the “experimental” capability functional
  • 31 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 30 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Jul 26 0
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
Diagnostics

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 20 Sept 2026 · Probed https://caliper.fit/mcp/

TLS valid

Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=caliper.fit CN=YE2,O=Let's Encrypt,C=US 24 Jul 2026 22 Oct 2026 ECDSA 256 ECDSA-SHA384 540b60ca63150ccf19d6cfd8816b8ba4170
SANs: caliper.fit
CN=YE2,O=Let's Encrypt,C=US (CA) CN=Root YE,O=ISRG,C=US 3 Sept 2025 2 Sept 2028 ECDSA 384 ECDSA-SHA384 4df3b15dd6c0784c507cd37b58e6f115
CN=Root YE,O=ISRG,C=US (CA) CN=ISRG Root X2,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 ECDSA-SHA384 872165fc34b6e5fba8add5b3705fb53a
CN=ISRG Root X2,O=Internet Security Research Group,C=US (CA) CN=ISRG Root X1,O=Internet Security Research Group,C=US 13 May 2026 2 Sept 2032 ECDSA 384 SHA256-RSA 6c8f1dc727c7117f7baf853ac980f9cd

Background: What to check on a remote MCP endpoint →

DNSSEC insecure

Validation of caliper.fit. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
fit. present 61939 8 Verified
caliper.fit. absent Unsigned (proven) parent-signed NSEC/NSEC3 proves an unsigned delegation
Authentication No authorisation required

The endpoint answered without asking for a token. Anyone who knows the URL can reach it.

Result No authorisation required
HTTP status 200
Header Value
strict-transport-security max-age=63072000; includeSubDomains
content-security-policy default-src 'none'; style-src 'unsafe-inline'; img-src 'self'; frame-ancestors 'none'
x-content-type-options nosniff
x-frame-options DENY
referrer-policy no-referrer
permissions-policy geolocation=(), camera=(), microphone=()

Background: How OAuth 2.1 works in the 2026 MCP spec →

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://caliper.fit/mcp/ Verified 200
http (plaintext) http://caliper.fit/mcp/ HTTPS enforced 308 https://caliper.fit/mcp/
MCP tools · 10 exposed · ~3,117 tokens

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 →

Tool Tokens
feature_request ~127

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

NameTypeReqDescription
descriptionstringyesA 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.

No output schema declared.

No examples provided.

format_auto ~501

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

format_batch ~311

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

NameTypeReqDescription
filesstringyesJSON 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…

No output schema declared.

No examples provided.

format_detect ~83

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

NameTypeReqDescription
filenamestringyesFilename or URL to check. The format is detected from the file extension.

No output schema declared.

No examples provided.

format_gltf ~351

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

format_las ~349

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

format_obj ~339

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

format_pcd ~343

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

format_ply ~345

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

format_stl ~368

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

NameTypeReqDescription
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…

No output schema declared.

No examples provided.

Common questions

What is the Caliper MCP server?

Caliper is an MCP server listed in the public MCP registry as fit.caliper/caliper. Geometry and CAD file metadata extraction for STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB. This page covers its hosted endpoint (https://caliper.fit/mcp/).

Is the Caliper MCP server safe to use?

Caliper scores 81 out of 100 on VerifyMCP. 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 Caliper MCP server expose?

Caliper exposes 10 tools: format_detect, feature_request, format_auto, format_stl, format_obj, and 5 more. Their descriptions and schemas cost roughly 3,117 tokens of context every time the server is loaded.

Does the Caliper MCP server require authentication?

No. We connected to Caliper without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

Is the Caliper MCP server still maintained?

Caliper is still listed as active in the MCP registry. We last reached this channel on 20 September 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.