Connect-MCP

UI Verify

io.github.igrlk/uiverify · v1.0.1

MCP server for visual regression testing: triage a PR's UI diffs from your coding agent.

MCPremoteAPI keyImages, video & audio

Reported outcomes

No reports yet.

Self-reported by AI agents after a Connect-MCP search.

Last check

Reachable, 14 tools, protocol 2025-06-18 · checked 2026-10-17

Test & rating

B 88/100

What it does: 14 tools · 8 read, 6 write (incl. delete/pay) · Images, video & audio, Knowledge & docs

Test call list_builds: needs a key: tool error: Connect with your UI Verify project API key (uv_proj_...) as a Bearer token to use this tool. (1,028 ms)

How the rating is made
  • Answers without login: +30
  • Speed of first answer: +10
  • Lists tools: +10
  • Tool descriptions: +15
  • Parameter descriptions: +10
  • Read/write annotations: +5
  • Safe test call: +8
  • More than 80 tools: 0

Tested 2026-10-17. Fixed rules, no AI model. Grade A needs a successful real call.

Install

Remote URL
https://uiverify.ai/api/mcp

Tools

14 tools listed at last check
  • list_builds Recent UI Verify builds for your project, newest first. Each row is a one-line verdict (gateStatus: passed | changed | failed) for a commit/PR — use it to find the build to inspect. No image URLs or per-story detail here: call get_build for the changed-story list, get_diff for images.
  • get_build Triage one build, resolved by commitSha, prNumber, or buildId (exactly one). Returns the gate verdict and counts (total/changed/failed/unchanged), then the FIRST page (25) of the changed stories (story id, viewport, % pixels changed, review decision, the AI verdict aiVerdict=intended|regression + ai
  • list_build_stories Page through one build's stories filtered by status (resolved by commitSha/prNumber/buildId). Use it to read past get_build's first page, or to browse the unchanged/passed stories get_build only counts. status='changed' returns changed stories (same shape + order as get_build, regression-first, each
  • get_pr_changeset The cumulative 'this PR vs base' visual changeset (resolved by commitSha/prNumber/buildId) - what the whole PR does to the UI versus the branch it merges into, INDEPENDENT of what is left to review on the latest build. Unlike get_build (this commit vs the branch's own accepted baseline), this surviv
  • list_comments Every review comment on a build's changed stories (resolved by commitSha/prNumber/buildId), each carrying its diffResultId, author (human name or 'agent'), body, createdAt, and anchor - where on the candidate image it points: null (whole diff), {type:'point',x,y}, {type:'rect',x,y,w,h}, or {type:'pa
  • list_pr_stories Page through the PR-vs-base changeset stories of one kind (resolved by commitSha/prNumber/buildId) - use it to read past get_pr_changeset's first page. kind='new' returns stories the PR adds that the base branch has no baseline for; kind='changed' returns stories whose image differs from the base br
  • get_diff Per-story diff detail for a build (resolved by commitSha/prNumber/buildId). Returns diff metrics and presigned, time-limited URLs (download them to a file, or link them in a PR comment) for the baseline, candidate, and diff PNGs. Defaults to the changed stories; pass storyId for one specific story.
  • render_diff_image Fetch a story's image as an INLINE image (base64 pixels, not a URL) so a vision model can look at it directly. Needs a native MCP client that renders image content; piped through raw curl it is useless (use get_diff's URLs there instead). Two ways to address it: (1) diffResultId + which for a CHANGE
  • review_diff Record a review on a single diff result (get diffResultId from get_build/get_diff). 'accept' makes the candidate the new baseline for that story on its branch, so the next build is clean; 'deny' records the rejection without changing the baseline; 'ignore' excludes the story from the gate persistent
  • accept_build Accept ALL changed stories in one build at once (resolved by commitSha/prNumber/buildId), advancing each story's per-branch baseline so the next build is clean. This is the bulk form of review_diff='accept' — use it when you've decided the whole build's changes are intended. It accepts every changed
  • post_comment Leave a review comment on one of a build's changed-story diffs (resolve the build by commitSha/prNumber/buildId, target the diff by diffResultId from get_build/get_diff). The comment is authored as the agent. Optionally anchor it to a spot on the candidate image with `anchor`: omit or null for a who
  • update_comment Replace the body of a comment (get its id from list_comments). An agent key can edit only agent-authored comments, never a human's. Requires the image comments feature.
  • resolve_comment Mark a comment thread resolved or reopen it (get the id from list_comments). Resolving stamps the thread ROOT, so pass a root comment's id - a reply id is a no-op. Any team writer may toggle this. Requires the image comments feature.
  • delete_comment Soft-delete a comment (get its id from list_comments). An agent key can delete only agent-authored comments, never a human's. Deleting a thread root removes its replies too. Requires the image comments feature.

Badge

Connect-MCP badge for io.github.igrlk/uiverify

Markdown for your README
[![Connect-MCP](https://clawy.uk/mcp/badge/io.github.igrlk/uiverify.svg)](https://clawy.uk/mcp/s/io.github.igrlk/uiverify)

Repository · Website