# MVisionPro Engineering Tools (remote · mvisionpro.com)

Read-only machine-vision calculations for optics, interfaces, line scan, sensors, and models.

- Trust score: 70/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-28

## Components

- remote · `mvisionpro.com`: 70/100 (this document), [markdown](https://verifymcp.io/servers/com-mvisionpro-tools/tools-mcp.md), [page](https://verifymcp.io/servers/com-mvisionpro-tools/tools-mcp)

## Channel facts

- Endpoint: `https://mvisionpro.com/tools/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.0.0`

## 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-09-28.

- **Endpoint Security**: 74/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - 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**: 64/100
  - AI-judged instruction clarity (good).
  - Context-footprint check failed: tool/resource definitions use about 1219 tokens (~203/item across 6 items; 6 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 17/100
  - Stability observed for 5 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.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 6 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 60/100
  - Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28.

## Install

### How do I install the MVisionPro Engineering Tools MCP server?

MVisionPro Engineering Tools is a hosted endpoint at https://mvisionpro.com/tools/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.

### Claude

```bash
claude mcp add --transport http com-mvisionpro-tools 'https://mvisionpro.com/tools/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-mvisionpro-tools": {
      "url": "https://mvisionpro.com/tools/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-mvisionpro-tools": {
      "type": "http",
      "url": "https://mvisionpro.com/tools/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-mvisionpro-tools]
url = "https://mvisionpro.com/tools/mcp"
```

### opencode

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

### OpenClaw

```bash
openclaw mcp add com-mvisionpro-tools --url 'https://mvisionpro.com/tools/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-mvisionpro-tools:
    url: "https://mvisionpro.com/tools/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-mvisionpro-tools": {
      "Transport": "http",
      "Url": "https://mvisionpro.com/tools/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-mvisionpro-tools -t streamable-http -u 'https://mvisionpro.com/tools/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-mvisionpro-tools": {
      "type": "http",
      "url": "https://mvisionpro.com/tools/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-09-28 (score 70, +7)

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

### 2026-09-27 (score 63, +1)

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

### 2026-09-25 (score 62, +1)

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

### 2026-09-24 (score 61, 0)

- [functional improvement] Stability: unverified → 0.03

### 2026-09-23 (score 61)

First indexed and scored.

## MCP tools (6)

### `optics` (~361 tokens)

Optics calculation

Calculate camera geometry, object sampling, exposure and depth of field. Provide exactly one sensor source: camera, sensor, or both manual sensor axes. Camera cannot be combined with manual passport fields. fovMm and wdMm are always required.

Input parameters:

- `blurPx` (number): Allowed motion blur in pixels.
- `camera` (string): Catalog camera model; exclusive with sensor or manual sensor axes.
- `defectMm` (number): Feature size in millimetres.
- `fNumber` (number): Lens F-number.
- `fovHeightMm` (number): Optional field-of-view height in millimetres.
- `fovMm` (number, required): Field-of-view width in millimetres.
- `lang` (string): Presentation language.
- `motionAxis` (string): Motion axis.
- `nPx` (number): Pixels required across a feature.
- `pixelSizeXUm` (number): Manual horizontal pixel size in micrometres; use with pixelSizeYUm.
- `pixelSizeYUm` (number): Manual vertical pixel size in micrometres; use with pixelSizeXUm.
- `resolutionHeightPx` (integer): Manual vertical resolution; use with resolutionWidthPx.
- `resolutionWidthPx` (integer): Manual horizontal resolution; use with resolutionHeightPx.
- `sensor` (string): Optical format; exclusive with camera or manual sensor axes.
- `sensorHeightMm` (number): Manual active sensor height in millimetres; use with sensorWidthMm.
- `sensorWidthMm` (number): Manual active sensor width in millimetres; use with sensorHeightMm.
- `speedMmS` (number): Object speed in millimetres per second.
- `wdMm` (number, required): Working distance in millimetres.

### `interface` (~264 tokens)

Interface bandwidth

Calculate stream bandwidth and evaluate interface options. Provide either camera or the complete manual stream set widthPx, heightPx, fps, bits, streamType and packed; do not combine the two modes. width and height are independent aliases for widthPx and heightPx, so mixed alias pairs are accepted, but do not send both aliases for one axis. The discovery alternatives describe complete sets; execution also rejects partial manual sets and every camera/manual mixture, for example camera with widthPx.

Input parameters:

- `bits` (integer): Logical bit depth.
- `cableLengthM` (number): Cable length in metres.
- `camera` (string): Catalog camera model; exclusive with manual stream fields.
- `cameras` (integer): Camera count.
- `fps` (number): Frame rate.
- `height` (integer): Alias for heightPx; do not send both.
- `heightPx` (integer): Manual frame height in pixels.
- `interface` (string): Optional interface family to evaluate.
- `lang` (string): Presentation language.
- `packed` (boolean): Whether a greater-than-eight-bit stream is packed.
- `streamType` (string): Stream type.
- `width` (integer): Alias for widthPx; do not send both.
- `widthPx` (integer): Manual frame width in pixels.

### `linescan` (~333 tokens)

Line-scan calculation

Calculate line width, line rate, exposure and confirmed camera modes. widthMm is required. Provide exactly one speed field (speedMmS or speedMMin) and exactly one calculation set (defectMm+nPx or accuracyMm+kPx); mode is inferred when omitted. samplingMode defaults to xy, or to width when longitudinalStepMm is present.

Input parameters:

- `accuracyMm` (number): Allowed error for measure-v2 mode.
- `camera` (string): Optional line-scan camera model.
- `defectMm` (number): Minimum defect for detect mode.
- `dutyCycle` (number): Fraction of a line period available for exposure.
- `interface` (string): Optional interface family filter.
- `kPx` (integer): Sampling coefficient for measure-v2 mode.
- `lang` (string): Presentation language.
- `longitudinalStepMm` (number): Required when samplingMode is width.
- `marginPct` (number): Line-rate reserve percentage.
- `mode` (string): Calculation mode; inferred from the exclusive defect or accuracy input set when omitted.
- `nPx` (number): Pixels per defect for detect mode.
- `pixelFormat` (string): Optional confirmed mode pixel format.
- `samplingMode` (string): Two-axis or explicit longitudinal sampling.
- `speedMMin` (number): Alternative speed in metres per minute; exclusive with speedMmS.
- `speedMmS` (number): Speed in millimetres per second; exclusive with speedMMin.
- `tdiStages` (integer): Optional TDI stage requirement.
- `widthMm` (number, required): Inspected web width in millimetres.

### `analog` (~65 tokens)

Camera cross-reference

Compare one unambiguous competitor model with bounded Hikrobot candidates. Compare one unambiguous competitor model with a bounded set of public Hikrobot candidates.

Input parameters:

- `lang` (string): Presentation language.
- `limit` (integer): Maximum results.
- `q` (string, required): Competitor model.

### `sensors` (~73 tokens)

Sensor lookup

Get a sensor aggregation by exactly one camera model or sensor part. Provide exactly one lookup key: a catalog camera model or a sensor part number.

Input parameters:

- `lang` (string): Presentation language.
- `model` (string): Catalog camera model; exclusive with sensor.
- `sensor` (string): Sensor part number; exclusive with model.

### `models` (~64 tokens)

Model search

Search the bounded public catalog projection. Search the bounded public catalog projection by literal model, alias, SKU or slug.

Input parameters:

- `lang` (string): Presentation language.
- `limit` (integer): Maximum results.
- `q` (string, required): Literal model, alias, SKU or slug search.

## Diagnostics

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

## Score history

- 2026-09-28: 70
- 2026-09-27: 63
- 2026-09-26: 62
- 2026-09-25: 62
- 2026-09-24: 61
- 2026-09-23: 61

## Common questions

### What is the MVisionPro Engineering Tools MCP server?

MVisionPro Engineering Tools is an MCP server listed in the public MCP registry as com.mvisionpro/tools. Read-only machine-vision calculations for optics, interfaces, line scan, sensors, and models. This page covers its hosted endpoint (https://mvisionpro.com/tools/mcp).

### Is the MVisionPro Engineering Tools MCP server safe to use?

MVisionPro Engineering Tools scores 70 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 MVisionPro Engineering Tools MCP server expose?

MVisionPro Engineering Tools exposes 6 tools: optics, interface, linescan, analog, sensors, models. Their descriptions and schemas cost roughly 1,160 tokens of context every time the server is loaded.

### Does the MVisionPro Engineering Tools MCP server require authentication?

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

### Is the MVisionPro Engineering Tools MCP server still maintained?

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

## Links

- Remote endpoint: https://mvisionpro.com/tools/mcp
- Website: https://mvisionpro.com/tools/api/
- Changelog RSS feed: https://verifymcp.io/servers/com-mvisionpro-tools/tools-mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-mvisionpro-tools/tools-mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-mvisionpro-tools/tools-mcp