Skip to content
Vynix logo

Vynix MCP server

Which MCP servers are Vynix's own, from the official registry and from asking its own domain, whether they answer, and what they offer. A program checked each of these, nobody copied them from a product page.

read 2026-10-19

← Back to Vynix

Whose server it is
  • Registry namein.vynix/vynix-mcpverified in the MCP registry

The registry name sits under vynix.in. The registry only lets a publisher use that namespace after proving control of the domain through DNS or HTTP.

When we asked itchecked 2026-10-19
  • Stateanswerschecked 2026-10-19
  • Tools17
  • Server calls itselfvynix
  • Server version0.1.4
  • Protocol version2025-06-18

On 2026-10-19 the server answered initialize and tools/list without a sign-in. First answer in 1136 ms.

Should an agent connect itNot proven either way yet
  • Whether its tools do the product's job has not been judged yet.

Once connected

  • add_comment, create_github_issue, create_share_link change data without a sign-in: anyone with the address can call them.
  • Parameters are untyped or undescribed in 12 of 17 tools: check arguments before calling.

Said by rules from the measurements above. The likely first call is a model's pick from the tool list; read its description before relying on it.

Measured dailydaily checks: 9, the first on 2026-10-19
  • INITE MCP score70 of 100answers 99 · definitions 88 · context 100 · use 29 · connects 100 · lowered by the warning signs below
  • Use13 npm downloads a week13 GitHub stars
  • Answered100% of days9 of 9 daily checks
  • Median first answer1056 ms
  • Space in an agent's context≈ 1,906 tokensthe definitions of all its tools (17), which an agent carries on every turn
  • Tool definitionsB · 88 of 100
  • Typed results17 of 17 toolsdeclared outputSchema: results come typed, read once
  • Parameters without a description: in 12 of 17

What an agent can do with it

  • not sure · capture element selectors and console errors with each annotation
  • not sure · turn pinned feedback notes into GitHub issues
  • can do · share read-only review links with clients

Each of the product's use cases, put to Jev against this server's tool list: can an agent do it with these tools?

Worth a look

  • Tools that change data, on a server that answers without a sign-in: add_comment, create_github_issue, create_share_link

A program checks the server once a day: initialize and tools/list, no model. Tokens are the definitions' length at about four characters a token. The grade averages six checks of every tool's name, description, schema and annotations; it says how well the tools are described, not whether they work. The score weighs what was measured and nothing else: answering (25%), doing the product's job (25%), definitions (20%), context (10%), use (10%) and how readily a client connects (10%). A part that was not measured is left out, and a hidden instruction caps the score at 40. The state of vendors' MCP servers: method and numbers →

Tools it offers17 tools · read 2026-10-19
  • list_projects

    List the Vynix projects you own.

  • list_annotations

    List a project’s annotations, optionally filtered by status, type, or priority. Start here with status "open" to see what needs fixing.

  • get_annotation

    Fetch one annotation with its full captured context: page, target element (selector, XPath, styles), surrounding DOM, and runtime diagnostics (console + network).

  • list_comments

    Read the discussion thread on an annotation.

  • get_annotation_analysis

    Read the latest stored AI diagnosis for an annotation (root causes, confidence, suggested fix, and likely source files). Returns null when none has been generated yet; run diagnose_annotation to create one.

  • get_annotation_screenshots

    Return the region screenshots attached to an annotation as viewable images, so you can see exactly what the reporter pointed at.

  • list_annotation_issues

    List the tracker (GitHub) issues opened from an annotation, with each issue’s live state. Set refresh to reconcile against GitHub (open/closed + any linked pull request).

  • list_project_issues

    List every tracker issue across a project, with an open/closed/agent summary.

  • generate_prompt

    Render a ready-to-paste coding prompt for an annotation, formatted for a target assistant. A deterministic template (no AI spend); for a deeper analysis use diagnose_annotation.

  • get_metrics

    Overview of your projects: KPI counts, status breakdown, a daily time series, and recent activity.

  • list_members

    List a project’s team members, including role and status.

  • get_activity

    Recent activity feed for a project (status changes, comments, issues, members).

  • update_annotation_status

    Update an annotation’s status, e.g. to mark it in_progress or completed.

  • add_comment

    Add a comment to an annotation’s thread, e.g. to record what you changed. Notifies the team.

  • diagnose_annotation

    Run the AI Diagnosis Engine on an annotation: it analyses the captured page, element, DOM, and runtime errors to produce ranked root causes, a confidence score, a suggested fix, and the likely source files. Calls an AI provider (uses…

  • create_github_issue

    Create a GitHub issue from an annotation. Uses the project’s configured repo and assignee unless overridden. Embeds the generated AI prompt in the issue body.

  • create_share_link

    Mint a read-only public review link for a project, so a stakeholder can review its annotations without an account. Reporter emails are hidden on shared views.

How to connect

Add the server to your MCP client config. Claude Desktop, Cursor and most other clients read this shape:

{
  "mcpServers": {
    "vynix-mcp": {
      "type": "http",
      "url": "https://mcp.vynix.in/mcp"
    }
  }
}

Add it

Claude Code, in a terminal

claude mcp add --transport http vynix https://mcp.vynix.in/mcp

Add to CursorAdd to VS Code

claude.ai, ChatGPT and other clients: add https://mcp.vynix.in/mcp as a custom connector in the settings.

Also shipped through: npm

Each line is something a program found when it went looking: the registry entry, the server's own answer, a spec that parses. A missing line means we did not find it, not that it does not exist.