Moltline Vision Maths
REMOTE · MCP.MOLTLINESTUDIO.COM · SCANNED SEP 20
Image header probing, bbox conversion, resize plans and colour maths. 4 of 6 free.
Available components
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 Security83
- The endpoint's TLS certificate is valid, in date, and uses a strong key. View diagnostics → Pass
- No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one. See how to fix → View diagnostics → Partial
- HTTPS is enforced; there's no plaintext access path. View diagnostics → Pass
- The HSTS (Strict-Transport-Security) header is present. View diagnostics → Pass
- DNSSEC is configured correctly; the domain's records validate against the full chain to the root. View diagnostics → Pass
Transport & Reachability100
- Verified streamable-http transport via a live MCP handshake. View diagnostics → Pass
Schema Quality & AI Usability61
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 2380 tokens (~396/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 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
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "nms" implies "remove" and declares readOnlyHint instead, contradicting what its own name says it does. See how to fix → Fail
- An AI judge read all 7 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
How do I install the Moltline Vision Maths MCP server?
Moltline Vision Maths is a hosted endpoint at https://mcp.moltlinestudio.com/vision, 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 · mcp.moltlinestudio.com
claude mcp add --transport http com-moltlinestudio-vision 'https://mcp.moltlinestudio.com/vision'
{
"mcpServers": {
"com-moltlinestudio-vision": {
"url": "https://mcp.moltlinestudio.com/vision"
}
}
} {
"servers": {
"com-moltlinestudio-vision": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/vision"
}
}
} [mcp_servers.com-moltlinestudio-vision] url = "https://mcp.moltlinestudio.com/vision"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-moltlinestudio-vision": {
"type": "remote",
"url": "https://mcp.moltlinestudio.com/vision",
"enabled": true
}
}
} openclaw mcp add com-moltlinestudio-vision --url 'https://mcp.moltlinestudio.com/vision' --transport streamable-http
mcp_servers:
com-moltlinestudio-vision:
url: "https://mcp.moltlinestudio.com/vision" {
"McpServers": {
"com-moltlinestudio-vision": {
"Transport": "http",
"Url": "https://mcp.moltlinestudio.com/vision"
}
}
} assistant mcp add com-moltlinestudio-vision -t streamable-http -u 'https://mcp.moltlinestudio.com/vision'
{
"mcpServers": {
"com-moltlinestudio-vision": {
"type": "http",
"url": "https://mcp.moltlinestudio.com/vision"
}
}
} The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.
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.
- 19 Sept 26 +1
- Stability: 0.97 → pass security
- 17 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 90 to 93. That category is still filling its 30-day observation window: 27 days of observed history at the previous scan, 28 at this one. The score rises as the window fills, whether or not the server changes.
- 15 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 13 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 70 to 73. That category is still filling its 30-day observation window: 21 days of observed history at the previous scan, 22 at this one. The score rises as the window fills, whether or not the server changes.
- 8 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.
- 6 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.
- 4 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 47 to 50. That category is still filling its 30-day observation window: 14 days of observed history at the previous scan, 15 at this one. The score rises as the window fills, whether or not the server changes.
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://mcp.moltlinestudio.com/vision
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=moltlinestudio.com | CN=WE1,O=Google Trust Services,C=US | 15 Aug 2026 | 13 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 72e09c6114448e7a0ed370fb03c277cb |
| SANs: moltlinestudio.com, *.moltlinestudio.com | ||||||
| CN=WE1,O=Google Trust Services,C=US (CA) | CN=GTS Root R4,O=Google Trust Services LLC,C=US | 13 Dec 2023 | 20 Feb 2029 | ECDSA 256 | ECDSA-SHA384 | 7ff31977972c224a76155d13b6d685e3 |
| CN=GTS Root R4,O=Google Trust Services LLC,C=US (CA) | CN=GlobalSign Root CA,OU=Root CA,O=GlobalSign nv-sa,C=BE | 15 Nov 2023 | 28 Jan 2028 | ECDSA 384 | SHA256-RSA | 7fe530bf331343bedd821610493d8a1b |
Background: What to check on a remote MCP endpoint →
DNSSEC secure
Validation of mcp.moltlinestudio.com. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| com. | present | 19718 | 13 | Verified |
| moltlinestudio.com. | present | 2371 | 13 | Verified |
| mcp.moltlinestudio.com. | Verified address RRset verified with the apex keys |
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=15576000; includeSubDomains |
| content-security-policy | default-src 'self'; script-src 'self' 'unsafe-inline'; style-src 'self' 'unsafe-inline'; img-src 'self' data:; font-src 'self' data:; connect-src 'self' https://api.moltlinestudio.com https://mcp.moltlinestudio.com; form-action 'self'; frame-ancestors 'none'; base-uri 'self'; object-src 'none'; upgrade-insecure-requests |
| x-content-type-options | nosniff |
| x-frame-options | DENY |
| referrer-policy | strict-origin-when-cross-origin |
| permissions-policy | camera=(), microphone=(), geolocation=() |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.moltlinestudio.com/vision | Verified | 200 | |
| http (plaintext) | http://mcp.moltlinestudio.com/vision | HTTPS enforced | 301 | https://mcp.moltlinestudio.com/vision |
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 →
bbox_convert Bbox Convert ~472
Convert bounding boxes between COCO, Pascal VOC and YOLO. FREE. The three formats disagree on everything: COCO is [x, y, width, height], VOC is [x1, y1, x2, y2], YOLO is [cx, cy, w, h] normalised to the image. Getting this wrong produces boxes that look plausible and quietly ruin every metric. Typical input {"boxes": [[10, 20, 100, 50]], "from_format": "coco", "to_format": "yolo", "image_width": 640, "image_height": 480} returns {"boxes": [[0.0938, 0.0938, 0.1562, 0.1042]], "converted": 1, "rejected": []}. Use whenever a dataset and a model disagree about format. Not for scoring predictions (detection_metrics) and not for removing overlaps (nms). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "boxes must contain at least one box"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| boxes | array | yes | Boxes to convert, each a list of exactly four numbers in from_format, e.g. [[10, 20, 100, 50]]. |
| clip | boolean | – | When true, clamp boxes to the image bounds instead of returning them as they are. Off by default, because a box outside the image is usually a bug worth seeing. |
| from_format | string | yes | "coco" for [x, y, w, h], "voc" for [x1, y1, x2, y2], or "yolo" for normalised [cx, cy, w, h]. |
| image_height | integer | – | Pixel height, required whenever yolo is on either side. |
| image_width | integer | – | Pixel width, required whenever yolo is on either side. |
| to_format | string | yes | The format to convert to; same three choices. |
Structured output declared, but exposes no named fields.
No examples provided.
colour_check Colour Check ~290
Check a colour pair against the WCAG contrast thresholds. FREE. Uses the WCAG 2 relative-luminance formula, so the number matches what an accessibility audit will report. Typical input {"foreground": "#767676", "background": "#ffffff"} returns {"contrast_ratio": 4.54, "AA": true, "AAA": false, "required": {"AA": 4.5, "AAA": 7.0}, "verdict": "Passes AA for normal text, fails AAA."}. Use when generating or auditing an interface. Not for converting colours between spaces and not for palettes. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "foreground must be a hex colour like #767676"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| background | string | yes | Background colour in the same notation. |
| foreground | string | yes | Text colour as hex, e.g. "#767676" or "767676" or "#777". |
| large_text | boolean | – | True for text at least 18pt, or 14pt bold, which WCAG allows to pass at a lower ratio. Default false. |
Structured output declared, but exposes no named fields.
No examples provided.
detection_metrics Detection Metrics ~447
Score detections against ground truth and show the working. PREMIUM (license). Greedy matching at the IoU threshold, highest-confidence prediction first, each ground-truth box matched at most once - the standard protocol. Reports per-class precision, recall and F1, and average precision by the all-points interpolation used by Pascal VOC 2010 onward. Typical input {"predictions": [{"box": [0,0,10,10], "label": "cat", "score": 0.9}], "ground_truth": [{"box": [1,1,11,11], "label": "cat"}]} returns {"overall": {"tp": 1, "fp": 0, "fn": 0, "precision": 1.0, "recall": 1.0, "f1": 1.0}, "per_class": {...}, "mAP": 1.0}. Use to compare two models on the same held-out set. Not for cleaning up a single model's overlapping output first - run nms before this. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "ground_truth must contain at least one box"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| box_format | string | – | "voc", "coco" or "yolo". Default "voc". |
| ground_truth | array | yes | True boxes, each {"box": [...], "label": ...}. |
| image_height | integer | – | Pixel height; required for yolo boxes. |
| image_width | integer | – | Pixel width; required for yolo boxes. |
| iou_threshold | number | – | Overlap at which a prediction counts as a match. Default 0.5, the usual reporting threshold. |
| predictions | array | yes | Predicted boxes, each {"box": [...], "label": ..., "score": ...}. Score defaults to 1.0 when omitted. |
Structured output declared, but exposes no named fields.
No examples provided.
image_probe Image Probe ~309
Read an image's format and pixel size from its header alone. FREE. Dimensions live in the first few dozen bytes of PNG, JPEG, GIF, BMP and WebP, so a base64 prefix is enough - you do not need to send the whole file, and nothing is decoded. Typical input {"data_base64": "iVBORw0KG..."} returns {"format": "png", "width": 1920, "height": 1080, "aspect_ratio": 1.7778, "aspect_label": "16:9", "megapixels": 2.07, "orientation": "landscape", "bytes_inspected": 512}. Use to find out what you are dealing with before planning a resize. Not for pixel content - nothing here reads pixels - and not for EXIF. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "data_base64 must not be empty"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| data_base64 | string | yes | The image file, base64-encoded. The first few hundred bytes are enough for every supported format; send a prefix rather than a large file. Data-URL prefixes like "data:image/png;base64," are accepted… |
Structured output declared, but exposes no named fields.
No examples provided.
nms Nms ~391
Remove duplicate detections of the same object. PREMIUM (license). Greedy non-maximum suppression: keep the highest-scoring box, drop everything overlapping it above the threshold, repeat. Ties break on the earlier index, so the result is deterministic rather than dependent on sort stability. Typical input {"boxes": [[0,0,10,10],[1,1,11,11],[50,50,60,60]], "scores": [0.9, 0.8, 0.7]} returns {"keep": [0, 2], "suppressed": [{"index": 1, "by": 0, "iou": 0.6807}], "kept": 2}. Use after a detector that emits overlapping boxes. Not for scoring against ground truth (detection_metrics) and not for format changes (bbox_convert). Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "boxes and scores must be the same length"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| box_format | string | – | "voc", "coco" or "yolo". Default "voc". |
| boxes | array | yes | Candidate boxes in box_format, e.g. [[0, 0, 10, 10]]. |
| image_height | integer | – | Pixel height; required for yolo boxes. |
| image_width | integer | – | Pixel width; required for yolo boxes. |
| iou_threshold | number | – | Overlap above which the lower-scoring box is dropped. Default 0.5. |
| scores | array | yes | One confidence per box, same order and same length as boxes. |
Structured output declared, but exposes no named fields.
No examples provided.
resize_plan Resize Plan ~417
Work out the exact scale, padding and crop for a model input size. FREE. Returns the numbers you need to transform boxes alongside the image, which is the step that usually gets skipped. Typical input {"width": 1920, "height": 1080, "target": "yolo_640"} returns {"scale": 0.3333, "resized": [640, 360], "pad": {"left": 0, "top": 140, "right": 0, "bottom": 140}, "box_transform": "x_new = x * 0.3333 + 0; y_new = y * 0.3333 + 140"}. Use before feeding an image to a fixed-input model. Not for finding out the image's size in the first place - that is image_probe. Errors: on invalid, missing, or malformed input this tool never raises a protocol error — it returns {"error": "<what is wrong and how to fix it>"} (for example {"error": "unknown target <value>; use one of <value> or set"}). Every call is read-only and idempotent, so after correcting the input it is always safe to retry.
| Name | Type | Req | Description |
|---|---|---|---|
| height | integer | yes | Source image height in pixels. |
| mode | string | – | "letterbox" scales to fit and pads the remainder, preserving aspect; "cover" scales to fill and crops the overflow; "stretch" distorts to fit exactly. Default "letterbox". |
| target | string | – | A named preset: "clip_224", "vit_384", "yolo_640", "sam_1024", "sd_512", "sd_768" or "detr_800". Ignored when target_size is set. |
| target_size | integer | – | A square side length in pixels, overriding target. Use this for a size the presets do not cover. |
| width | integer | yes | Source image width in pixels. |
Structured output declared, but exposes no named fields.
No examples provided.
What is the Moltline Vision Maths MCP server?
Moltline Vision Maths is an MCP server listed in the public MCP registry as com.moltlinestudio/vision. Image header probing, bbox conversion, resize plans and colour maths. 4 of 6 free. This page covers its hosted endpoint (https://mcp.moltlinestudio.com/vision).
Is the Moltline Vision Maths MCP server safe to use?
Moltline Vision Maths scores 85 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 Moltline Vision Maths MCP server expose?
Moltline Vision Maths exposes 6 tools: image_probe, bbox_convert, resize_plan, colour_check, nms, detection_metrics. Their descriptions and schemas cost roughly 2,326 tokens of context every time the server is loaded.
Does the Moltline Vision Maths MCP server require authentication?
No. We connected to Moltline Vision Maths without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Moltline Vision Maths MCP server still maintained?
Moltline Vision Maths 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.