Vyntryx MCP connector
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
No arguments | |||
Instructions
Guidance the server publishes about itself, which clients place ahead of the tool catalog so the model reads it before choosing anything.
This server publishes no instructions, or was last inspected before Glama recorded them.
Capabilities
Features and capabilities supported by this server
Protocol revision2025-11-25
| Capability | Details |
|---|---|
| tools | {
"listChanged": false
} |
| prompts | {
"listChanged": false
} |
| resources | {
"subscribe": false,
"listChanged": false
} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| vyntryx_login_statusA | Show whether this connector is logged in to Vyntryx, and as whom. If not, the user must run |
| vyntryx_scan_source_uploadA | Package a local project folder (secrets, .gitignore'd files, .git, dependencies and build output are excluded), upload it to Vyntryx and start a SAST/SCA/secrets scan. Returns the scan session id. |
| vyntryx_scan_source_gitA | Ask Vyntryx to clone a git repository over https (optionally a branch/tag/commit |
| vyntryx_scan_statusC | State and progress of a scan session. |
| vyntryx_list_findingsB | Findings of a scan session (UUID, title, severity, file:line, CWE). Optional filters: severity (critical|high|medium|low|info), status. |
| vyntryx_get_findingA | Full detail, evidence and remediation of one finding: its scan |
| vyntryx_finding_relationshipsA | Findings linked to this one and what fixing it may affect (AI-suggested impact is labelled as such). |
| vyntryx_session_messagesA | Chat messages of a scan session (what the Vyntryx UI shows), optionally only those after |
| vyntryx_post_messageB | Post a message into a scan session's chat; it appears in the Vyntryx UI. |
| vyntryx_cancel_scanB | Cancel a running scan that you started. |
Prompts
Interactive templates invoked by user choice
| Name | Description |
|---|---|
No prompts | |
Resources
Contextual data attached and managed by the client
| Name | Description |
|---|---|
No resources | |
TDQS
Scored across 10 tools
Each tool maps to a distinct action on a distinct resource: starting scans (upload vs git, clearly separated by source), polling state, reading findings, navigating finding detail/relationships, and session chat. The only mild overlap is between vyntryx_scan_source_upload and vyntryx_scan_source_git, but the descriptions make the boundary explicit. No two tools appear to do the same thing.
All names share a uniform `vyntryx_` prefix and snake_case, and are readable. There is minor inconsistency in ordering (resource-first like `vyntryx_scan_status`/`vyntryx_list_findings` vs action-first like `vyntryx_post_message`/`vyntryx_cancel_scan`), but the pattern is predictable enough for selection.
Ten tools is well within the sweet spot and every tool earns its place in the scan workflow. Nothing looks like filler or a redundant variant.
The scan lifecycle (start, status, findings, cancel) and session chat are well covered. However, there is no way to list existing scan sessions or recover a session id after the initial call, and no tool to delete/archive sessions or export reports, which creates a dead end for resumed or cross-session workflows.