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.

MVisionPro Engineering Tools

REMOTE · MVISIONPRO.COM · SCANNED SEP 28

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

Available components

70 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 Security74
Transport & Reachability100
Schema Quality & AI Usability64
  • AI-judged instruction clarity (good).Pass
  • 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. See how to fix → Fail
  • Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management17
  • Stability observed for 5 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
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 6 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
  • An AI judge read all 7 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail
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.

remote · mvisionpro.com

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

  • 28 Sept 26 +7
    • We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
  • 27 Sept 26 +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.

  • 25 Sept 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
  • 24 Sept 26 0
    • Stability: unverified → 0.03 ▲ functional
  • 23 Sept 26 61

    First indexed and scored.

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 28 Sept 2026 · Probed https://mvisionpro.com/tools/mcp

TLS valid

Negotiated TLS 1.3 with TLS_AES_256_GCM_SHA384 .

Subject Issuer Valid from Valid until Key Signature Serial
CN=mvisionpro.com CN=YE2,O=Let's Encrypt,C=US 18 Sept 2026 17 Dec 2026 ECDSA 256 ECDSA-SHA384 6e6831b44a5195e985525bcef4575db5e71
SANs: en.mvisionpro.com, kz.mvisionpro.com, mvisionpro.com, sa.mvisionpro.com, www.mvisionpro.com
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 mvisionpro.com. — Not signed

Zone DS Keys Algorithms Outcome
. trust_anchor 20326, 38696 8, 8 Verified
com. present 19718 13 Verified
mvisionpro.com. 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
content-security-policy default-src 'none'; base-uri 'none'; form-action 'none'; frame-ancestors 'none'; img-src 'none'; media-src 'none'; object-src 'none'; script-src 'none'; style-src 'none'
x-content-type-options nosniff
referrer-policy no-referrer

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

Transports 2 probes
Transport URL Outcome Status Location
streamable-http https://mvisionpro.com/tools/mcp Verified 200
http (plaintext) http://mvisionpro.com/tools/mcp HTTPS enforced 301 https://mvisionpro.com/tools/mcp
MCP tools · 6 exposed · ~1,160 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
analog ~65

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

NameTypeReqDescription
langstring–Presentation language.
limitinteger–Maximum results.
qstringyesCompetitor model.

No output schema declared.

No examples provided.

interface ~264

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.

NameTypeReqDescription
bitsinteger–Logical bit depth.
cableLengthMnumber–Cable length in metres.
camerastring–Catalog camera model; exclusive with manual stream fields.
camerasinteger–Camera count.
fpsnumber–Frame rate.
heightinteger–Alias for heightPx; do not send both.
heightPxinteger–Manual frame height in pixels.
interfacestring–Optional interface family to evaluate.
langstring–Presentation language.
packedboolean–Whether a greater-than-eight-bit stream is packed.
streamTypestring–Stream type.
widthinteger–Alias for widthPx; do not send both.
widthPxinteger–Manual frame width in pixels.

No output schema declared.

No examples provided.

linescan ~333

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.

NameTypeReqDescription
accuracyMmnumber–Allowed error for measure-v2 mode.
camerastring–Optional line-scan camera model.
defectMmnumber–Minimum defect for detect mode.
dutyCyclenumber–Fraction of a line period available for exposure.
interfacestring–Optional interface family filter.
kPxinteger–Sampling coefficient for measure-v2 mode.
langstring–Presentation language.
longitudinalStepMmnumber–Required when samplingMode is width.
marginPctnumber–Line-rate reserve percentage.
modestring–Calculation mode; inferred from the exclusive defect or accuracy input set when omitted.
nPxnumber–Pixels per defect for detect mode.
pixelFormatstring–Optional confirmed mode pixel format.
samplingModestring–Two-axis or explicit longitudinal sampling.
speedMMinnumber–Alternative speed in metres per minute; exclusive with speedMmS.
speedMmSnumber–Speed in millimetres per second; exclusive with speedMMin.
tdiStagesinteger–Optional TDI stage requirement.
widthMmnumberyesInspected web width in millimetres.

No output schema declared.

No examples provided.

models ~64

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

NameTypeReqDescription
langstring–Presentation language.
limitinteger–Maximum results.
qstringyesLiteral model, alias, SKU or slug search.

No output schema declared.

No examples provided.

optics ~361

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.

NameTypeReqDescription
blurPxnumber–Allowed motion blur in pixels.
camerastring–Catalog camera model; exclusive with sensor or manual sensor axes.
defectMmnumber–Feature size in millimetres.
fNumbernumber–Lens F-number.
fovHeightMmnumber–Optional field-of-view height in millimetres.
fovMmnumberyesField-of-view width in millimetres.
langstring–Presentation language.
motionAxisstring–Motion axis.
nPxnumber–Pixels required across a feature.
pixelSizeXUmnumber–Manual horizontal pixel size in micrometres; use with pixelSizeYUm.
pixelSizeYUmnumber–Manual vertical pixel size in micrometres; use with pixelSizeXUm.
resolutionHeightPxinteger–Manual vertical resolution; use with resolutionWidthPx.
resolutionWidthPxinteger–Manual horizontal resolution; use with resolutionHeightPx.
sensorstring–Optical format; exclusive with camera or manual sensor axes.
sensorHeightMmnumber–Manual active sensor height in millimetres; use with sensorWidthMm.
sensorWidthMmnumber–Manual active sensor width in millimetres; use with sensorHeightMm.
speedMmSnumber–Object speed in millimetres per second.
wdMmnumberyesWorking distance in millimetres.

No output schema declared.

No examples provided.

sensors ~73

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.

NameTypeReqDescription
langstring–Presentation language.
modelstring–Catalog camera model; exclusive with sensor.
sensorstring–Sensor part number; exclusive with model.

No output schema declared.

No examples provided.

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.