How do I authenticate with the server?
Authentication uses OAuth 2.0 client credentials. You must set `ANYWHERE_CLIENT_ID`, `ANYWHERE_CLIENT_SECRET`, and `ANYWHERE_SUBDOMAIN` environment variables in your `.env` file or MCP client configuration.
@javierb507
Basic information
AlienVault/USM Anywhere MCP Server - Threat intelligence and security monitoring
No standard config provided
This server doesn't expose a parseable MCP config block in its README. See the repository for install instructions.
RepositoryTool list not available yet
This listing does not currently have a tool list to display. This does not mean the server has no tools; check its documentation for supported capabilities.
We auto-extract tools from the README. The maintainer can list them under a ## Tools heading to populate this section.
Anywhere MCP Server is a Model Context Protocol (MCP) server that integrates with the Levelblue USM Anywhere platform, providing secure access to security monitoring data including alarms, events, and threat intelligence through the USM Anywhere API v2.0. It also offers legacy support for AlienVault OTX API. Built with TypeScript and Zod validation, it is intended for security analysts and developers who need to query security data via MCP-compatible clients.
Clone the repository, install dependencies with npm install, build with npm run build, and configure a .env file with your USM Anywhere credentials (client ID, client secret, subdomain) and optionally an OTX API key. Start the server with npm start. Add the server to your MCP client configuration by providing the path to the built index.js and the required environment variables. Tools include get_alarms, get_events, get_alarm_details, get_event_details, search_pulses, get_indicator, and get_pulse.
Authentication uses OAuth 2.0 client credentials. You must set `ANYWHERE_CLIENT_ID`, `ANYWHERE_CLIENT_SECRET`, and `ANYWHERE_SUBDOMAIN` environment variables in your `.env` file or MCP client configuration.
Seven tools are provided: `get_alarms`, `get_events`, `get_alarm_details`, `get_event_details` (USM Anywhere API v2.0), and `search_pulses`, `get_indicator`, `get_pulse` (legacy OTX API).
Yes, the server includes legacy OTX API support. You can optionally set an `OTX_API_KEY` environment variable to use the OTX tools.
Node.js is required. The server is built with TypeScript and must be compiled with `npm run build` before running.
Add a JSON entry to your MCP client configuration with `command: "node"`, `args` pointing to the built `dist/index.js`, and `env` containing the required credentials (`ANYWHERE_CLIENT_ID`, `ANYWHERE_CLIENT_SECRET`, `ANYWHERE_SUBDOMAIN`).

Windframe MCP gives your AI the design taste needed to create consistent, production-ready UI that feels intentionally designed. Available at https://windframe.dev/mcp

Agent-Native Terminal
Set up and manage the Eddyter AI rich text editor by talking to your AI agent — for Claude, Cursor, Codex and other MCP tools. A Model Context Protocol server that lets AI tools add Eddyter to a React, Next.js, Vite or R

Automated codebase documentation for GitHub: searchable docs, MCP context for AI agents, doc drift detection, and Friday Cleanup PRs.
Model Context Protocol (MCP) server for TranscriptFetch: fetch YouTube transcripts, search, channels, and playlists from any MCP client.
Comments