dvera-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| CT_HOME | No | Path to the CT installation directory. Set this if CT is installed outside the default location. |
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 | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| dvera_check_environmentA | Report whether a local CT installation is usable by DVERA, and what is missing when it is not. Takes no arguments and needs no CT install, so it is the tool to run when the verification tools are absent from the list. |
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 1 tool
Only one tool exists, so there is no possibility of confusion or overlap with other tools.
The single tool name follows a clear verb_noun pattern (dvera_check_environment), though with only one tool the pattern is not strongly established.
A single tool is extremely thin for a server; even if the purpose is narrow, one tool provides very limited functionality.
The tool only checks the environment; there are no tools to actually perform DVERA operations, so the surface is severely incomplete for any real workflow.