# Vynix (remote · mcp.vynix.in)

Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.

- Trust score: 74/100 (medium)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-08-03

## Components

- remote · `mcp.vynix.in`: 74/100 (this document), [markdown](https://verifymcp.io/servers/in-vynix-vynix-mcp/mcp.md), [page](https://verifymcp.io/servers/in-vynix-vynix-mcp/mcp)
- npm · `@usevynix/mcp-server`: 35/100, [markdown](https://verifymcp.io/servers/in-vynix-vynix-mcp/usevynix-mcp-server.md), [page](https://verifymcp.io/servers/in-vynix-vynix-mcp/usevynix-mcp-server)

## Channel facts

- Endpoint: `https://mcp.vynix.in/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `0.1.4`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-08-03.

- **Endpoint Security**: 77/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Every tool declares its destructiveHint and none is destructive, so open access doesn't expose one.
  - HTTPS is enforced; there's no plaintext access path.
  - HSTS check failed: the Strict-Transport-Security header is absent.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 82/100
  - 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).
  - AI-judged instruction clarity (good).
  - Tool/resource definitions use about 1168 tokens (~68/item across 17 items; 17 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 20/100
  - Stability observed for 6 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 84/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 45% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

## Install

### Claude

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

### Codex

```toml
[mcp_servers.in-vynix-vynix-mcp]
url = "https://mcp.vynix.in/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "in-vynix-vynix-mcp": {
      "type": "remote",
      "url": "https://mcp.vynix.in/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add in-vynix-vynix-mcp --url https://mcp.vynix.in/mcp --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  in-vynix-vynix-mcp:
    url: "https://mcp.vynix.in/mcp"
```

### Other

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

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-08-03 (score 74, +1)

No change was recorded against any check on this day. Stability & Change Management went from 17 to 20. That category is still filling its 30-day observation window: 5 days of observed history at the previous scan, 6 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-08-01 (score 73, +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.

### 2026-07-31 (score 72, +3)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-30 (score 69, +1)

- [functional] We updated how we score, so this day's move reflects our rubric, not a change to the server

### 2026-07-29 (score 68, +1)

- [functional improvement] Stability: unverified → 0.03

### 2026-07-28 (score 67)

First indexed and scored.

## MCP tools (17)

### `list_projects` (~17 tokens)

List projects

List the Vynix projects you own.

Output parameters:

- `projects` (array)

### `list_annotations` (~100 tokens)

List annotations

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

Input parameters:

- `limit` (integer): Page size, 1-200 (default 50).
- `offset` (integer)
- `priority` (string)
- `project_id` (string, required): The id of the project to list annotations for.
- `status` (string)
- `type` (string)

Output parameters:

- `items` (array)
- `limit`
- `offset`
- `total` (number)

### `get_annotation` (~54 tokens)

Get annotation

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

Input parameters:

- `annotation_id` (string, required): The id of the annotation to fetch.

Output parameters:

- `created_at`
- `description` (string|null)
- `dom`
- `element`
- `id` (string)
- `page`
- `page_title`
- `page_url`
- `priority`
- `project_id`
- `selector`
- `status`
- `title`
- `type`
- `updated_at`

### `list_comments` (~24 tokens)

List comments

Read the discussion thread on an annotation.

Input parameters:

- `annotation_id` (string, required)

Output parameters:

- `comments` (array)

### `get_annotation_analysis` (~56 tokens)

Get AI diagnosis

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.

Input parameters:

- `annotation_id` (string, required)

Output parameters:

- `analysis`
- `diagnosis_enabled` (boolean)

### `get_annotation_screenshots` (~43 tokens)

Get screenshots

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

Input parameters:

- `annotation_id` (string, required)

Output parameters:

- `count` (number)
- `screenshots` (array)

### `list_annotation_issues` (~71 tokens)

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).

Input parameters:

- `annotation_id` (string, required)
- `refresh` (boolean): Reconcile live state from GitHub. Optional.

Output parameters:

- `issues` (array)

### `list_project_issues` (~35 tokens)

List project issues

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

Input parameters:

- `project_id` (string, required)

Output parameters:

- `issues` (array)
- `summary` (object)

### `generate_prompt` (~76 tokens)

Generate coding 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.

Input parameters:

- `annotation_id` (string, required): The id of the annotation to turn into a prompt.
- `target` (string): Which assistant to format for. Defaults to generic.

Output parameters:

- `prompt`
- `target` (string)

### `get_metrics` (~28 tokens)

Get metrics

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

Output parameters:

- `kpis`
- `recent_activity`
- `status_breakdown` (array)
- `timeseries`

### `list_members` (~28 tokens)

List members

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

Input parameters:

- `project_id` (string, required)

Output parameters:

- `members` (array)
- `owner`

### `get_activity` (~32 tokens)

Get activity

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

Input parameters:

- `project_id` (string, required)

Output parameters:

- `activity` (array)

### `update_annotation_status` (~41 tokens)

Update status

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

Input parameters:

- `annotation_id` (string, required)
- `status` (string, required)

Output parameters:

- `created_at`
- `description` (string|null)
- `dom`
- `element`
- `id` (string)
- `page`
- `page_title`
- `page_url`
- `priority`
- `project_id`
- `selector`
- `status`
- `title`
- `type`
- `updated_at`

### `add_comment` (~49 tokens)

Add comment

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

Input parameters:

- `annotation_id` (string, required)
- `body` (string, required): The comment text.

Output parameters:

- `annotation_id`
- `body`
- `created_at`
- `id` (string)

### `diagnose_annotation` (~118 tokens)

Run AI diagnosis

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 tokens / may cost money) and stores the result. Requires AI + diagnosis enabled by the workspace admin and a key set.

Input parameters:

- `annotation_id` (string, required)
- `model` (string): Override the model. Optional.
- `provider` (string): Override the AI provider. Defaults to the workspace default.

Output parameters:

- `annotation_id`
- `confidence` (number|null)
- `created_at`
- `id` (string)
- `model`
- `provider` (string|null)
- `root_causes` (array)
- `status`
- `suggested_files`
- `suggested_fix`
- `summary`
- `updated_at`

### `create_github_issue` (~93 tokens)

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.

Input parameters:

- `annotation_id` (string, required): The id of the annotation to file as an issue.
- `assignees` (array): GitHub usernames to assign. Optional.
- `repo` (string): owner/repository to file the issue in. Optional.

Output parameters:

- `annotation_id`
- `created_at`
- `id` (string)
- `issue_number` (number|null)
- `issue_url` (string|null)
- `provider`
- `repo`
- `state`

### `create_share_link` (~70 tokens)

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.

Input parameters:

- `expires_in_days` (integer): Days until the link expires. 0 or omitted means it never expires.
- `project_id` (string, required)

Output parameters:

- `created_at`
- `expires_at` (string|null)
- `id` (string)
- `is_expired` (boolean)
- `path`
- `project_id`
- `scope`

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/in-vynix-vynix-mcp/mcp#diagnostics

## Score history

- 2026-08-03: 74
- 2026-08-02: 73
- 2026-08-01: 73
- 2026-07-31: 72
- 2026-07-30: 69
- 2026-07-29: 68
- 2026-07-28: 67

## Links

- Remote endpoint: https://mcp.vynix.in/mcp
- Repository: https://github.com/UseVynix/vynix-mcp
- Website: https://www.vynix.in/mcp
- Changelog RSS feed: https://verifymcp.io/servers/in-vynix-vynix-mcp/mcp/changelog.xml
- Changelog JSON feed: https://verifymcp.io/servers/in-vynix-vynix-mcp/mcp/changelog.json
- HTML version of this page: https://verifymcp.io/servers/in-vynix-vynix-mcp/mcp