Caliper MCP server
fit.caliper/calipercaliper.fitstreamable-httpv0.1.1Scanned
Geometry and CAD file metadata extraction for STL, OBJ, PLY, PCD, LAS/LAZ, glTF/GLB.
10 tools: 9 change things and 1 only read.
- Reads private data · 1
- Reads text others write · 8
- Can send data out · 0
- 8 findings
Tools listed without sign-in. Remote posture
With Anlyon
9 tools here change things. Govern them.
- Anlyon lists the tools and adopts none.
- Each tool you adopt gets approvals and receipts.
- Your agent never holds the key.
A tool your agent calls directly is not routed through Anlyon and is not governed by it. Anlyon Radar only lists and labels, and these labels are the same either way.
What the Caliper MCP server can do
The Caliper MCP server is published by caliper.fit, a domain the MCP Registry verified. It has 10 tools. It can create or change data (9 tools: format_detect, feature_request, format_auto, format_stl and 5 more), but cannot delete data. 1 tool only reads.
1 tool reads private data (format_batch); 8 tools bring in text other people can write (format_auto, format_stl, format_obj and 5 more).
The fixed checks matched 8 findings (credentials-mention). Each one comes with the text it matched.
Its remote endpoint lists its tools without sign-in.
Last scanned Nov 15, 2026, version 0.1.1.
Tools
Grouped by what each tool does, most consequential first. Open one for its reasons and full description; descriptions are the publisher's own words.
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.Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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.Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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.Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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.Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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.Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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).Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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).Reads text others write1 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.
What it can reach
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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 1Show 1 read-only tool
format_batchAnalyze multiple geometry files in a single batch request.Reads private dataReads text others write1 finding
Why it is in this group
- The description's first verb is "analyze": a word for reading.
What it can reach
- private-dataThe description's first sentence says "analyze" and "file": it reads files.
- private-dataThe input names a file (input.files), and the tool reads: it reads files.
- untrusted-inputThe server marks it openWorldHint: true: it reaches things outside the server's own data.
Findings
- Info
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
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.
Exfil surface
Which tools read private data, which read text someone else can write, and which can send data out. One of each is a path a prompt injection can use.
No private-data, untrusted-input, outbound path in this server alone: no tool is tagged outbound.
- Reads private data1
- Reads files, mail, messages, databases, secrets, calendars or repositories.
- Reads text others write8
- Brings in text someone else can write: web pages, inbound email, messages, issues and comments.
- Can send data out0
- Can carry data to people or systems: it sends, posts or publishes, or takes a recipient, channel or URL.
Other servers in the same agent add their own tools to these paths. Audit your whole setup to see them together.
Remote posture
What anyone on the internet sees at the remote endpoint: an anonymous initialize and tools/list, and the public OAuth metadata.
Looked at Nov 20, 2026, 18:54 UTC, unchanged since Oct 22, 2026. No credentials were sent and no tool was called. What is looked at.
- Reachable
- yes
- HTTP status of an anonymous initialize
- 200
- tools/list served without credentials
- yes
- Tools that change things, listed without credentials
- 9
- Protocol version
- 2025-06-18
- WWW-Authenticate on 401
- not observed
- resource_metadata in WWW-Authenticate
- not observed
- RFC 9728 protected resource metadata
- not observed
- Authorization servers
- not observed
- Legacy HTTP+SSE transport
- no
- Dynamic client registration
- not observed
- Client ID metadata documents
- not observed
- WarnThe whole server
The endpoint served tools/list without credentials, and the list has 9 tools that change things (9 write). Whether a call also works without credentials was not tested: tools are never called.
What this check looks forMatched text
https://caliper.fit/mcp/: tools/list returned 10 tools to an anonymous client, including format_detect (write), feature_request (write), format_auto (write), format_stl (write), format_obj (write) and 4 more
Findings
Matches of fixed checks, with the text they matched.
- Infoformat_auto
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
- Infoformat_stl
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
- Infoformat_obj
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
- Infoformat_ply
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
- Infoformat_pcd
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
- Infoformat_las
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
Show 2 more findingsShow fewer
- Infoformat_gltf
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
- Infoformat_batch
The input schema at properties.payment.description mentions "credential".
What this check looks forMatched text
inputSchema.properties.payment.description: "...and 'payload' from the org.paymentauth/credential flow. Default: null (omit on first call..."
History
Changes to its tool definitions and to its remote endpoint, newest first.
No change seen yet. Its tools are rescanned every day, and a remote endpoint is looked at once a week.
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/claude mcp add --transport http caliper https://caliper.fit/mcp/Run in a terminal.
Claude Code permissions
Allow the reads, ask before a change or a way out, deny the deletes. Paste into .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. A read that can send data out (it takes a URL, say) asks first too. It assumes the server is installed as caliper. Review it before you use it.
Capability tags behind 8 rules
- mcp__caliper__format_auto untrusted-input
- mcp__caliper__format_stl untrusted-input
- mcp__caliper__format_obj untrusted-input
- mcp__caliper__format_ply untrusted-input
- mcp__caliper__format_pcd untrusted-input
- mcp__caliper__format_las untrusted-input
- mcp__caliper__format_gltf untrusted-input
- mcp__caliper__format_batch private-data, untrusted-input
Pin
Keep the decision: fail CI when the tools change, follow every change, or show a badge.
Pin in CI
Fail a build when the tools you reviewed are not the tools the server serves today.
curl -s "https://radar.anlyon.com/api/v1/servers/fit.caliper/caliper/verify?hash=77168dc0937eeb09b727da0d3c4ac0ae9deec8ee172b93ce0e2bfda26ed3800a" | jq -e '.changed == false'Pinned hash 77168dc0937e, from Nov 15, 2026, 09:17 UTC.
Watch
Get told when its tools change: a new tool, a new description, a new class.
https://radar.anlyon.com/servers/fit.caliper/caliper/changes.xmlAn Atom feed. Works in any feed reader or Slack's RSS app.
Badge
[](https://radar.anlyon.com/servers/fit.caliper/caliper)Source: MCP Registry. Synced Oct 21, 2026, 18:12 UTC.
Caliper MCP server: questions and answers
Answered from the scan above, not from the publisher's description.
Is the Caliper MCP server safe?
- No scan can promise that. What its definitions show: 10 tools, 9 of which can change, send or delete something, and 8 findings from fixed checks. Allow the reads, ask before each change, and deny the deletes; the permissions block on this page does that.
Can the Caliper MCP server delete data?
- No tool is classed as destructive: going by their definitions, none of them deletes, cancels or revokes anything.
Can the Caliper MCP server do things that cannot be undone?
- No tool is classed as irreversible: none of them sends, pays, publishes or merges, going by their definitions.
What tools does the Caliper MCP server have?
- 10 tools: 9 write, 1 read. format_detect, feature_request, format_auto, format_stl, format_obj, format_ply, format_pcd, format_las and 2 more.
Does the Caliper MCP server need sign-in or OAuth?
- Its remote endpoint listed its tools to an anonymous client, without sign-in.
Does the Caliper MCP server send data to outside services?
- None of its tools sends, posts or publishes, or takes a recipient, channel or URL.
Has the Caliper MCP server changed its tools?
- Not since Anlyon Radar started tracking it. Last scanned Nov 15, 2026.