Skip to main content
Beta Scan dependencies, detect vulnerabilities, find leaked secrets, and review code for security issues directly inside OpenAI Codex, powered by your AI agent.

​
What you can do

With the Endor Labs MCP server, you can:
  • Check dependency safety before adding a new package
  • Scan for vulnerabilities and malware in your open source dependencies
  • Find leaked secrets accidentally committed in your Git history
  • Run AI security reviews on your code changes (Enterprise Edition)

​
Install the MCP server

The Developer Edition is free and uses default security policies from Endor Labs. When you use the MCP server for the first time, a browser window opens for authentication through GitHub, GitLab, or Google.
Have questions? Email us at community-support@endor.ai.

​
Verify the installation

codex mcp list
Confirm that endor-cli-tools appears in the list. You can also use /mcp in the Codex TUI to view active MCP servers.

​
Try a test prompt

After installing the MCP server, try the following prompt in your AI chat or CLI to verify that the tools are working. 
Check if the npm package lodash version 4.17.20 has any vulnerabilities
The MCP server uses the check_dependency_for_vulnerabilities tool to check for known vulnerabilities and return the results. If you see a response with vulnerability details, the MCP server is working correctly.

​
Manage MCP server tools

In the Codex TUI, use /mcp to see your active MCP servers. You can also disable specific tools in the config.toml file: 
[mcp_servers.endor-cli-tools]
command = "npx"
args = ["-y", "endorctl", "ai-tools", "mcp-server"]
enabled_tools = ["check_dependency_for_vulnerabilities", "scan"]

​
How to use the Endor Labs MCP server

The Endor Labs MCP server provides the following tools:
  • check_dependency_for_vulnerabilities: Check if a dependency in your project is vulnerable.
  • check_dependency_for_risks: Check a dependency for security risks including vulnerabilities and malware.
  • get_endor_vulnerability: Get the details of a specific vulnerability from the Endor Labs vulnerability database.
  • get_resource: Retrieve additional context from commonly used Endor Labs resources about your software, such as findings, vulnerabilities, and projects.
  • scan: Run an Endor Labs security scan to detect risks in your open source dependencies, find common security issues, and spot any credentials accidentally exposed in your Git repository.
  • security_review: Perform security review analysis on code diffs. Analyzes local uncommitted changes (both staged and unstaged) compared to HEAD, or diffs between the main branch and the last commit. Requires the Enterprise Edition. You must specify your namespace in the MCP server configuration. You must also enable AI security code review for your namespace in the Endor Labs platform. See AI security code review for setup instructions.
After you set up the MCP server, you can choose to disable the tools that you do not want to use.

​
Configure AGENTS.md

To enhance the MCP server integration, you can add instructions in AGENTS.md at the root of your repository. Codex reads AGENTS.md files to guide AI development with your project-specific instructions.
  1. Navigate to the root of your repository.
  2. Create or edit the AGENTS.md file in the root of your repository.
  3. Add appropriate rules for your project. For example, you can add a rule to check if the code is free from vulnerabilities.

​
Example AGENTS.md instructions

You can use the following AGENTS.md instructions as a quick start for the Endor Labs MCP server. Modify the instructions to meet your specific organization’s needs. For more information, refer to the OpenAI Codex AGENTS.md documentation. 
# Software Composition Analysis (SCA) Rule (Endor Labs via MCP)

This project uses Endor Labs for automated dependency (SCA) scanning, integrated through the MCP server.

## Workflow

Every time a manifest or lockfile (package.json, requirements.txt, go.mod, pom.xml, etc.) is created or modified in any way, immediately do the following prior to performing your next task.

**Important**: Do not proceed after creating or modifying a manifest file without running this first.

- Run `endor-cli-tools` using the `check_dependency_for_vulnerabilities` tool via the MCP server.
- Provide the **ecosystem**, **dependency name**, and **version** always when making this tool call.
- If a vulnerability or error is identified:
  - Upgrade to the suggested safe version, or
  - Replace the dependency with a non-vulnerable alternative.
- Re-run the check using `endor-cli-tools` to confirm the issue is resolved.

## Notes
- All scans must be performed using the MCP server integration (`endor-cli-tools`). Do not invoke `endorctl` directly.

​
Troubleshooting

Use the following troubleshooting steps to resolve common issues with the Endor Labs MCP server.
Run npx --version in your terminal. If the command fails, install Node.js version 18 or later. After installing, restart your IDE or CLI to reload the MCP server configuration.
Ensure your IDE or CLI can open a browser. Check firewall or security software that might block browser launch. For Enterprise Edition with SSO, verify that ENDOR_MCP_SERVER_AUTH_MODE and ENDOR_MCP_SERVER_AUTH_TENANT are set correctly in your MCP configuration.
Install endorctl globally and update your MCP config to call it directly instead of using npx. For more information, see Install endorctl.Replace the command and args entries with:
"command": "endorctl",
"args": ["ai-tools", "mcp-server"]
Verify your namespace is correct and your user has Read-Only permissions in Endor Labs. See Authorization policies for details. Also ensure endorctl is on your PATH if you installed it globally instead of using npx.
On Windows, ensure the following prerequisites are met:
  • Node.js is installed
  • npm global bin directory is in your PATH

​
Install Node.js

If Node.js is not installed, download and install the LTS version from nodejs.org. During installation, ensure the option to add Node.js to PATH is selected.

​
Configure the PATH environment variable

After installing Node.js, verify that the npm global bin directory is in your PATH:
  1. Run the following command in the command line. 
    npm config get prefix
    This returns the npm global directory path, typically C:\Users\<YourUsername>\AppData\Roaming\npm.
  2. Add the npm global directory path to the Path variable under User variables in your system’s environment variables settings.
  3. Restart for the PATH changes to take effect.

​
Verify the setup

Run the following command in your terminal.
npx --version
If this returns a version number, your Windows setup is complete and the MCP server can use npx to run endorctl.