MCP.Market

Vector Mirror MCP server

by c64dos-png·io.github.c64dos-png/vector-mirror·v1.0.0

Deterministic SVG perception for LLM agents — measures, never guesses. MCP server.

B78/100grade B
What users say
No reviews yet
Be the first
Safety scan
B78/100

full report

Adoption
New

0 stars41 downloads/wk

Reviews

Write one

Nobody has reviewed Vector Mirror yet.

If you have run it, two minutes of your experience saves the next person an afternoon.

Vector Mirror tools

No tool declarations could be read from the package source. They show once the server is installed.

Public scan report

scanner v0.1.9 · 2026-09-27 · same rubric, same numbers if you re-run it

no findings
  • Code scan34 source files scanned25/25
  • –Live reliabilityno gateway calls yet and no remote to proben/a
  • –Tool poisoningtools not inspected (local package is not executed); not countedn/a
  • Auth qualitylocal package, no credentials required12/15
  • Maintenancelast push 107 days ago8/15
  • Maintainer identityregistry namespace matches repository owner6/10
Overall 78/100. Components that don't apply are left out of the denominator. Any critical finding is an F.RubricAppeal a findingJSON

How Vector Mirror compares

Against every graded AI and agents MCP server, from our own scans and uptime checks. Updated after each scan run.

Safety score
78/100
higher than 57% of 4,460 AI and agents servers
Downloads a week
41
more than 33% of 1,538 AI and agents servers with a package

Install Vector Mirror in Claude Code, Cursor or VS Code

Runs npx -y vector-mirror on your machine. Read the scan report first; the gateway never runs local packages.

claude mcp add vector-mirror -- npx -y vector-mirror
Add to Cursor

What the publisher says

From the Vector Mirror repository's README, as published. We do not edit it. Read it on GitHub

Mirror — a deterministic SVG perception eye for LLM agents

**Mirror renders SVG in a real browser and reports what is actually where — in grid cells and

W3C color names, with prose and structured output — and it never guesses.** Spatial layout

constraints become unit tests. And every tool description is a claim the server proves about

itself. Built for agents that can't afford to hallucinate coordinates.

What is this?

When an LLM agent edits an SVG, how does it know whether the change worked? Today it either guesses from the source text (and hallucinates positions, because layout is a render-time property, not a source property) or it takes a screenshot and guesses from pixels (and burns tokens on a vision round-trip that still can't name a color or address a region precisely).

Mirror is the third option: a measuring eye. It is a sensory organ for LLMs, not a tool with a purpose. It perceives and measures; it never interprets, decides, or acts — the brain (the LLM or you) does that. The eye has three tissues:

Because the measurement runs in a real browser engine, Mirror sees what the browser sees — including things the SVG source never tells you.

Killer demo: the perceive → constrain → correct → compare loop

A cold agent (no source code, MCP only) built a 17-element mission-control panel and verified it to an exact stop-condition. Here is the loop, with real outputs from that session:

# 1 — INSPECT: see the layout in LLM grammar (no constraints checked yet)
inspect(svg)
  → scene: 16 elements, grid 16×10, canvas_validity: valid
    e.g. { id: "led-ok", tag: "circle", cell: "B3", color: "lime" }
    colors come out as W3C NAMES, never hex.

# 2 — CONSTRAINTS: ask the vocabulary (it is finite and closed)
constraints()
  → 11 types. RIGHT-OF / BELOW deliberately do NOT exist
    (use LEFT-OF / ABOVE with swapped operands).

# 3 — ANALYZE: turn layout intent into unit tests
analyze(svg, ["#title CENTERED-IN #frame", "#led-ok ABOVE #led-warn", ...16 constraints])
  → PARTIAL: 2 unchecked SUBJECT_TIME_VARIANT
    "#beacon has an animated r → not measurable; geometrically satisfied @t0 (bbox …)"
    # the eye refuses to guess about an animated value. It says so, with a reason code.

# 4 — fix, re-analyze until PASS (convergence is tracked, not vibes)
analyze(svg_v3, [...], previousIssueCount: N)
  → PASS  (corrections == [] && unchecked == [] && canvas_validity == valid && diff == [])

# 5 — SNIPER LOOP: pin a baseline, edit, catch regressions in one call
bookmark("panel-pass", analysisId)
compare(sabotaged_svg, [], "panel-pass")
  → FAIL: FARBÄNDERUNG orange→crimson  

The agent's verdict, verbatim: "In 13 calls it never once guessed, lied, or made me guess. analyze landed on the first try. Lost diagnostic loops: 0." — 8.5/10.

Features — the honesty axes

Mirror's differentiator is not what it measures but that it is honest about what it cannot.

Shortened. The full README is on GitHub.

Nothing above is checked by us. What we check is on the safety report.

Vector Mirror: common questions

Is Vector Mirror MCP server safe?
Mostly: it is graded B (78/100). Read the Vector Mirror safety report
How do I install Vector Mirror?
It runs on your machine. Copy the Claude Code, Cursor, VS Code or Claude Desktop config from the install section.
Does Vector Mirror need an API key?
Not as far as the registry entry and our scan can tell: no credentials are declared or required.
Is Vector Mirror maintained?
The last commit was 145 days ago (2026-06-12). The latest release is v1.0.0.
What can I use instead of Vector Mirror?
Servers from other publishers that do the same job: MCP AutoMem MCP server.
How does Vector Mirror compare with other AI and agents MCP servers?
safety score 78/100 (higher than 57% of 4,460 AI and agents servers); downloads a week 41 (more than 33% of 1,538 AI and agents servers with a package). Full comparison.

Alternatives to Vector Mirror

Same job from other publishers: the closest match first, then the best rated.

  • MCP AutoMem
    Graph-vector memory for AI assistants using FalkorDB and Qdrant
    C