fortra-fim-mcp
This server provides a local stdio MCP interface for interacting with the Tripwire Enterprise REST API, primarily focused on File Integrity Monitoring (FIM) workflows. It exposes the following tools:
te_get_status: Retrieve the current status of the Tripwire Enterprise API and server.
te_list_nodes / te_get_node: Search and list monitored nodes with filters (name, paging, etc.), or fetch a specific node by ID.
te_get_policy_test_results / te_get_policy_test_result: Query policy compliance test results filtered by node, state, policy test name, etc., or fetch a single result by ID.
te_list_versions / te_get_version: Search element versions with filters (node ID, rule name, promotion status, severity range), or get a specific version by ID.
Allowlist results across four categories:
te_list_allowlist_software_resultste_list_allowlist_open_port_resultste_list_allowlist_user_resultste_list_allowlist_service_results
te_promote_versions: Submit a promotion request for one or more element versions (with approval ID, comment, and custom property type).
te_get_promote_request: Check the status of a previously submitted promotion request.
te_api_request: Make raw GET, POST, PUT, DELETE, or PATCH requests to any Tripwire Enterprise API endpoint under
/api/v1.
Additional features:
Most list tools accept a
filtersobject mapping to Tripwire query parameters (e.g.,name,nodeId,state,pageLimit,pageStart).All tools support a
rawflag to return full Tripwire JSON or a condensed, MCP-friendly summary with acount.
Click on "Install Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@fortra-fim-mcplist nodes with name containing 'prod'"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
fim-mcp
Local stdio MCP server for the Tripwire Enterprise REST API.
The first version wraps the core FIM workflows:
list and fetch nodes
get policy test results
list and fetch element versions
explore allowlist software, open port, user, and service results
promote element versions
check promote request status
make a raw Tripwire API request for uncovered endpoints
Setup
python -m venv .venv
.\.venv\Scripts\Activate.ps1
python -m pip install -e .
Copy-Item .env.example .envEdit .env:
TE_HOST=https://TECONSOLEHOST/api
TE_USERNAME=administrator
TE_API_TOKEN=replace-with-token
TE_VERIFY_SSL=false
TE_TIMEOUT=30TE_HOST may point at either the API root (https://server/api) or the versioned API root (https://server/api/v1).
Related MCP server: Shannon Lite MCP
Run
python -m fim_mcpFor MCP clients that need a command:
{
"mcpServers": {
"fim-mcp": {
"command": "python",
"args": ["-m", "fim_mcp"],
"env": {
"TE_HOST": "https://TECONSOLEHOST/api",
"TE_USERNAME": "administrator",
"TE_API_TOKEN": "replace-with-token",
"TE_VERIFY_SSL": "false"
}
}
}
}If your Python user scripts directory is on PATH, the installed fim-mcp command works too.
Use with Codex
Codex reads MCP server definitions from config.toml in your Codex home directory. On Windows this is usually:
C:\Users\<you>\.codex\config.tomlAfter running the setup steps above, add this to that file. Use the full path to the virtual environment Python for the repo:
[mcp_servers.fim-mcp]
command = 'C:\path\to\fim-mcp\.venv\Scripts\python.exe'
args = ['-m', 'fim_mcp']
startup_timeout_sec = 30
[mcp_servers.fim-mcp.env]
TE_HOST = 'https://TECONSOLEHOST/api'
TE_USERNAME = 'administrator'
TE_API_TOKEN = 'replace-with-token'
TE_VERIFY_SSL = 'false'
TE_TIMEOUT = '30'For this checkout, the command path would look like:
command = 'C:\Users\chris\Downloads\vibes\te mcp\.venv\Scripts\python.exe'If you install the package somewhere already on PATH, you can use the console script instead:
[mcp_servers.fim-mcp]
command = 'fim-mcp'
args = []
startup_timeout_sec = 30
[mcp_servers.fim-mcp.env]
TE_HOST = 'https://TECONSOLEHOST/api'
TE_USERNAME = 'administrator'
TE_API_TOKEN = 'replace-with-token'
TE_VERIFY_SSL = 'false'
TE_TIMEOUT = '30'Restart Codex, or start a new Codex session, after editing config.toml. To verify the server is available, ask Codex to list Tripwire Enterprise nodes or call te_get_status. If the server starts correctly, Codex will have access to the te_* tools listed below.
Tools
te_get_statuste_list_nodeste_get_nodete_get_policy_test_resultste_get_policy_test_resultte_list_versionste_get_versionte_list_allowlist_software_resultste_list_allowlist_open_port_resultste_list_allowlist_user_resultste_list_allowlist_service_resultste_promote_versionste_get_promote_requestte_api_request
Most list tools accept a filters object. The keys map directly to Tripwire Enterprise query parameters, so filters such as name, sub_name, nodeId, state, pageLimit, and pageStart can be passed without code changes.
Set raw: true on wrapped tools to return the Tripwire JSON unchanged. The default response returns a smaller MCP-friendly summary plus a count.
Maintenance
Resources
Unclaimed servers have limited discoverability.
Looking for Admin?
If you are the server author, to access and configure the admin panel.
Latest Blog Posts
- Your AI Chatbot Just Exposed Your CEO's Salary to an InternBy Om-Shree-0709 on .Agent IdentityMCP SecurityOAuth Delegation
- Why MCP Servers Need Execution Sandboxing (And Why Your Current Stack Isn't Enough)By Om-Shree-0709 on .Agentic AiPrompt InjectionWebAssembly
MCP directory API
We provide all the information about MCP servers via our MCP API.
curl -X GET 'https://glama.ai/api/mcp/v1/servers/askjarv/fim-mcp'
If you have feedback or need assistance with the MCP directory API, please join our Discord server