Connect Vynix and your agent gets 17 tools, among them add_comment, create_github_issue, create_share_link. It answers at https://mcp.vynix.in/mcp over streamable HTTP, and it listed its tools to an anonymous client, so no sign-in was needed for that. Our probes reached it 6 of 6 times since 10 September 2026; the last check, on 19 October 2026, succeeded.
Give AI coding agents access to your Vynix visual feedback, bug reports, and AI diagnosis.
Description as the publisher wrote it.
| Tool | What it does |
|---|---|
add_comment | Add a comment to an annotation’s thread, e.g. to record what you changed. Notifies the team. Inputs: annotation_id, body |
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. Inputs: annotation_id, repo, assignees |
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. Inputs: project_id, expires_in_days |
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 tokens Inputs: annotation_id, provider, model |
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. Inputs: annotation_id, target |
get_activity | Recent activity feed for a project (status changes, comments, issues, members). Inputs: project_id |
get_annotation | Fetch one annotation with its full captured context: page, target element (selector, XPath, styles), surrounding DOM, and runtime diagnostics (console + network). Inputs: annotation_id |
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. Inputs: annotation_id |
get_annotation_screenshots | Return the region screenshots attached to an annotation as viewable images, so you can see exactly what the reporter pointed at. Inputs: annotation_id |
get_metrics | Overview of your projects: KPI counts, status breakdown, a daily time series, and recent activity. |
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). Inputs: annotation_id, refresh |
list_annotations | List a project’s annotations, optionally filtered by status, type, or priority. Start here with status "open" to see what needs fixing. Inputs: project_id, status, type, priority, limit, offset |
list_comments | Read the discussion thread on an annotation. Inputs: annotation_id |
list_members | List a project’s team members, including role and status. Inputs: project_id |
list_project_issues | List every tracker issue across a project, with an open/closed/agent summary. Inputs: project_id |
list_projects | List the Vynix projects you own. |
update_annotation_status | Update an annotation’s status, e.g. to mark it in_progress or completed. Inputs: annotation_id, status |
Every block below points at https://mcp.vynix.in/mcp. Pick your client and copy.
claude mcp add --transport http vynix https://mcp.vynix.in/mcp
{
"mcpServers": {
"vynix": {
"command": "npx",
"args": ["-y", "mcp-remote", "https://mcp.vynix.in/mcp"]
}
}
}{
"mcpServers": {
"vynix": {
"url": "https://mcp.vynix.in/mcp"
}
}
}{
"servers": {
"vynix": {
"type": "http",
"url": "https://mcp.vynix.in/mcp"
}
}
}{
"context_servers": {
"vynix": {
"url": "https://mcp.vynix.in/mcp"
}
}
}{
"mcpServers": {
"vynix": {
"serverUrl": "https://mcp.vynix.in/mcp"
}
}
}{
"mcpServers": {
"vynix": {
"url": "https://mcp.vynix.in/mcp"
}
}
}name: Vynix
version: 0.0.1
schema: v1
mcpServers:
- name: Vynix
type: streamable-http
url: https://mcp.vynix.in/mcp{
"mcpServers": {
"vynix": {
"httpUrl": "https://mcp.vynix.in/mcp"
}
}
}{
"mcpServers": {
"vynix": {
"type": "http",
"url": "https://mcp.vynix.in/mcp"
}
}
}{
"mcpServers": {
"vynix": {
"url": "https://mcp.vynix.in/mcp"
}
}
}goose://extension?url=https%3A%2F%2Fmcp.vynix.in%2Fmcp&type=streamable_http&id=vynix&name=Vynix
It answered our last check on 19 October 2026 in 544 ms. Over 6 checks since 10 September 2026 it answered 6. Status here comes from Neuronto's own probes, not from the publisher.
Yes. It is published by vynix.in and served from mcp.vynix.in, the vendor's own domain: https://mcp.vynix.in/mcp.
17, as returned by the server's own tools/list on 12 September 2026: add_comment, create_github_issue, create_share_link, diagnose_annotation, generate_prompt, get_activity, get_annotation, get_annotation_analysis, and 9 more.
It answered our last check on 19 October 2026 in 544 ms. Over 6 checks since 10 September 2026 it answered 6.
Put the server under mcpServers in ~/.cursor/mcp.json with the URL https://mcp.vynix.in/mcp. The exact JSON is above, with the same setup for Claude Code, Claude Desktop, VS Code, Windsurf, Zed, Gemini CLI and the rest.
It listed its tools to an anonymous client, so reading the tool list needs no key. Individual tools can still ask for credentials in their own inputs.
Publisher: in.vynix. Endpoint host: mcp.vynix.in. ARD identifier: urn:air:in.vynix:mcp:vynix-mcp.
First indexed 10 September 2026. The tools are exactly what the server returned; nothing on this page
is inferred from its name. Ranking in Neuronto search is never for sale.