Vynix
REMOTE · MCP.VYNIX.IN · 2 COMPONENTS · SCANNED SEP 20
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.
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 Security77
- 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
- HSTS check failed: the Strict-Transport-Security header is absent. See how to fix → View diagnostics → Fail
- 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 Usability85
- 100% of prompts and resources have a non-trivial description (not blank, and not just the item's name).Pass
- AI-judged instruction clarity (good).Pass
- Tool/resource definitions use about 1168 tokens (~68/item across 17 items; 17 tools + 0 resources), lean.Pass
- 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 Coverage84
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 45% of tool parameters carry a description.Partial
- Structured output schemas are declared (100% of tools); any adoption earns full credit.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 17 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 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 Vynix MCP server?
Vynix is a hosted endpoint at https://mcp.vynix.in/mcp, 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.vynix.in
claude mcp add --transport http in-vynix-vynix-mcp 'https://mcp.vynix.in/mcp'
{
"mcpServers": {
"in-vynix-vynix-mcp": {
"url": "https://mcp.vynix.in/mcp"
}
}
} {
"servers": {
"in-vynix-vynix-mcp": {
"type": "http",
"url": "https://mcp.vynix.in/mcp"
}
}
} [mcp_servers.in-vynix-vynix-mcp] url = "https://mcp.vynix.in/mcp"
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"in-vynix-vynix-mcp": {
"type": "remote",
"url": "https://mcp.vynix.in/mcp",
"enabled": true
}
}
} openclaw mcp add in-vynix-vynix-mcp --url 'https://mcp.vynix.in/mcp' --transport streamable-http
mcp_servers:
in-vynix-vynix-mcp:
url: "https://mcp.vynix.in/mcp" {
"McpServers": {
"in-vynix-vynix-mcp": {
"Transport": "http",
"Url": "https://mcp.vynix.in/mcp"
}
}
} assistant mcp add in-vynix-vynix-mcp -t streamable-http -u 'https://mcp.vynix.in/mcp'
{
"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.
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.
- 31 Aug 26 0
- Server version: 0.1.2 → 0.1.4 functional
- 27 Aug 26 +1
- Stability: 0.97 → pass security
- 26 Aug 26 +1
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 24 Aug 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 87 to 90. That category is still filling its 30-day observation window: 26 days of observed history at the previous scan, 27 at this one. The score rises as the window fills, whether or not the server changes.
- 11 Aug 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 31 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 30 Jul 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 29 Jul 26 0
- Stability: unverified → 0.03 ▲ functional
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.vynix.in/mcp
TLS valid
Negotiated TLS 1.3 with TLS_AES_128_GCM_SHA256 .
| Subject | Issuer | Valid from | Valid until | Key | Signature | Serial |
|---|---|---|---|---|---|---|
| CN=vynix.in | CN=WE1,O=Google Trust Services,C=US | 28 Aug 2026 | 26 Nov 2026 | ECDSA 256 | ECDSA-SHA256 | 4c41732c35468d060e9baa86af81c83f |
| SANs: vynix.in, *.vynix.in | ||||||
| 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.vynix.in. — Secure
| Zone | DS | Keys | Algorithms | Outcome |
|---|---|---|---|---|
| . | trust_anchor | 20326, 38696 | 8, 8 | Verified |
| in. | present | 10094 | 13 | Verified |
| vynix.in. | present | 2371 | 13 | Verified |
| mcp.vynix.in. | 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 |
Background: How OAuth 2.1 works in the 2026 MCP spec →
Transports 2 probes
| Transport | URL | Outcome | Status | Location |
|---|---|---|---|---|
| streamable-http | https://mcp.vynix.in/mcp | Verified | 200 | |
| http (plaintext) | http://mcp.vynix.in/mcp | HTTPS enforced | 301 | https://mcp.vynix.in/mcp |
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 →
add_comment Add comment ~49
Add a comment to an annotation’s thread, e.g. to record what you changed. Notifies the team.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| body | string | yes | The comment text. |
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | – | – | – |
| body | – | – | – |
| created_at | – | – | – |
| id | string | – | – |
No examples provided.
create_github_issue Create GitHub issue ~93
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | 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. |
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | – | – | – |
| created_at | – | – | – |
| id | string | – | – |
| issue_number | number|null | – | – |
| issue_url | string|null | – | – |
| provider | – | – | – |
| repo | – | – | – |
| state | – | – | – |
No examples provided.
create_share_link Create share link ~70
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.
| Name | Type | Req | Description |
|---|---|---|---|
| expires_in_days | integer | – | Days until the link expires. 0 or omitted means it never expires. |
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | – | – | – |
| expires_at | string|null | – | – |
| id | string | – | – |
| is_expired | boolean | – | – |
| path | – | – | – |
| project_id | – | – | – |
| scope | – | – | – |
No examples provided.
diagnose_annotation Run AI diagnosis ~118
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| model | string | – | Override the model. Optional. |
| provider | string | – | Override the AI provider. Defaults to the workspace default. |
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | – | – | – |
| confidence | number|null | – | – |
| created_at | – | – | – |
| id | string | – | – |
| model | – | – | – |
| provider | string|null | – | – |
| root_causes | array | – | – |
| status | – | – | – |
| suggested_files | – | – | – |
| suggested_fix | – | – | – |
| summary | – | – | – |
| updated_at | – | – | – |
No examples provided.
generate_prompt Generate coding prompt ~76
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | The id of the annotation to turn into a prompt. |
| target | string | – | Which assistant to format for. Defaults to generic. |
| Name | Type | Req | Description |
|---|---|---|---|
| prompt | – | – | – |
| target | string | – | – |
No examples provided.
get_activity Get activity ~32
Recent activity feed for a project (status changes, comments, issues, members).
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| activity | array | yes | – |
No examples provided.
get_annotation Get annotation ~54
Fetch one annotation with its full captured context: page, target element (selector, XPath, styles), surrounding DOM, and runtime diagnostics (console + network).
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | The id of the annotation to fetch. |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | – | – | – |
| description | string|null | – | – |
| dom | – | – | – |
| element | – | – | – |
| id | string | – | – |
| page | – | – | – |
| page_title | – | – | – |
| page_url | – | – | – |
| priority | – | – | – |
| project_id | – | – | – |
| selector | – | – | – |
| status | – | – | – |
| title | – | – | – |
| type | – | – | – |
| updated_at | – | – | – |
No examples provided.
get_annotation_analysis Get AI diagnosis ~56
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.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| analysis | – | – | – |
| diagnosis_enabled | boolean | – | – |
No examples provided.
get_annotation_screenshots Get screenshots ~43
Return the region screenshots attached to an annotation as viewable images, so you can see exactly what the reporter pointed at.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| count | number | – | – |
| screenshots | array | yes | – |
No examples provided.
get_metrics Get metrics ~28
Overview of your projects: KPI counts, status breakdown, a daily time series, and recent activity.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| kpis | – | – | – |
| recent_activity | – | – | – |
| status_breakdown | array | – | – |
| timeseries | – | – | – |
No examples provided.
list_annotation_issues List annotation issues ~71
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).
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| refresh | boolean | – | Reconcile live state from GitHub. Optional. |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
No examples provided.
list_annotations List annotations ~100
List a project’s annotations, optionally filtered by status, type, or priority. Start here with status "open" to see what needs fixing.
| Name | Type | Req | Description |
|---|---|---|---|
| limit | integer | – | Page size, 1-200 (default 50). |
| offset | integer | – | – |
| priority | string | – | – |
| project_id | string | yes | The id of the project to list annotations for. |
| status | string | – | – |
| type | string | – | – |
| Name | Type | Req | Description |
|---|---|---|---|
| items | array | yes | – |
| limit | – | – | – |
| offset | – | – | – |
| total | number | – | – |
No examples provided.
list_comments List comments ~24
Read the discussion thread on an annotation.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| comments | array | yes | – |
No examples provided.
list_members List members ~28
List a project’s team members, including role and status.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| members | array | yes | – |
| owner | – | – | – |
No examples provided.
list_project_issues List project issues ~35
List every tracker issue across a project, with an open/closed/agent summary.
| Name | Type | Req | Description |
|---|---|---|---|
| project_id | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| issues | array | yes | – |
| summary | object | yes | – |
No examples provided.
list_projects List projects ~17
List the Vynix projects you own.
Input schema present but exposes no named parameters.
| Name | Type | Req | Description |
|---|---|---|---|
| projects | array | yes | – |
No examples provided.
update_annotation_status Update status ~41
Update an annotation’s status, e.g. to mark it in_progress or completed.
| Name | Type | Req | Description |
|---|---|---|---|
| annotation_id | string | yes | – |
| status | string | yes | – |
| Name | Type | Req | Description |
|---|---|---|---|
| created_at | – | – | – |
| description | string|null | – | – |
| dom | – | – | – |
| element | – | – | – |
| id | string | – | – |
| page | – | – | – |
| page_title | – | – | – |
| page_url | – | – | – |
| priority | – | – | – |
| project_id | – | – | – |
| selector | – | – | – |
| status | – | – | – |
| title | – | – | – |
| type | – | – | – |
| updated_at | – | – | – |
No examples provided.
What is the Vynix MCP server?
Vynix is an MCP server listed in the public MCP registry as in.vynix/vynix-mcp. Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis. This page covers its hosted endpoint (https://mcp.vynix.in/mcp).
Is the Vynix MCP server safe to use?
Vynix scores 87 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 Vynix MCP server expose?
Vynix exposes 17 tools: list_projects, list_annotations, get_annotation, list_comments, get_annotation_analysis, and 12 more. Their descriptions and schemas cost roughly 935 tokens of context every time the server is loaded.
Does the Vynix MCP server require authentication?
No. We connected to Vynix without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.
Is the Vynix MCP server still maintained?
Vynix 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.