fortra-fim-mcp
Server Configuration
Describes the environment variables required to run the server.
| Name | Required | Description | Default |
|---|---|---|---|
| TE_HOST | Yes | The Tripwire Enterprise API URL (e.g., https://server/api or https://server/api/v1) | |
| TE_TIMEOUT | No | HTTP request timeout in seconds | 30 |
| TE_USERNAME | Yes | Username for authentication | |
| TE_API_TOKEN | Yes | API token for authentication | |
| TE_VERIFY_SSL | No | Whether to verify SSL certificates | false |
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 |
|---|---|
| te_get_statusC | Get Tripwire Enterprise API and server status. |
| te_list_nodesC | Search Tripwire nodes. Pass Tripwire query parameters in filters. |
| te_get_nodeB | Get one Tripwire node by readable-key node ID. |
| te_get_policy_test_resultsC | Search policy test results. Use filters for nodeId, state, policyTestName, paging, and other API parameters. |
| te_get_policy_test_resultB | Get one policy test result by readable-key result ID. |
| te_list_versionsC | Search element versions. Use filters for nodeId, ruleName, isPromoted, severityRange, paging, and other API parameters. |
| te_get_versionB | Get one element version by readable-key version ID. |
| te_promote_versionsC | Submit a Tripwire element version promotion request. |
| te_get_promote_requestC | Get status for a Tripwire element version promotion request. |
| te_api_requestB | Call any Tripwire Enterprise API endpoint under /api/v1. |
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 targets a distinct resource (nodes, versions, policy tests, promotions, status) with clear actions (get, list, promote). The generic te_api_request is a fallback for uncovered endpoints, not overlapping with specific tools.
All tools use the consistent 'te_verb_noun' pattern in snake_case, with verbs like get, list, promote. No mixing of conventions.
10 tools is well-scoped for a Tripwire Enterprise integration, covering core operations without excess or deficiency.
The toolset covers the main lifecycle (list/get nodes and versions, view policy test results, manage promotions) and the generic API endpoint fills any remaining gaps, ensuring no dead ends.