TripWire MCP Server
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
} |
| experimental | {} |
Tools
Functions exposed to the LLM to take actions
| Name | Description |
|---|---|
| safe_execD | Classify and safely route a command inside TripWire's sandbox. |
| rollbackC | Restore a TripWire snapshot in the configured demo sandbox. |
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 2 tools
The two tools have clearly distinct purposes: safe_exec routes commands into a sandbox, while rollback restores snapshots. There is no ambiguity between executing a command and restoring an earlier state.
Both names use a single-word verb (safe_exec, rollback) without a noun component, showing some inconsistency with the typical verb_noun pattern. They're readable and somewhat consistent in being commands, but 'safe_exec' mixes an adjective+verb while 'rollback' is a single verb.
Two tools is on the thin side even for a focused sandbox MCP server. The domain (sandbox command execution and snapshot management) could reasonably warrant a few more operations like listing snapshots or checking sandbox state.
There is no way to inspect snapshot state before executing or understand what command is being routed, and no visibility into sandbox status. The surface covers execution and rollback but leaves out key supporting operations that agents would need to make informed decisions.