Anywhere MCP Server

Created By
javierb507a year ago
AlienVault/USM Anywhere MCP Server - Threat intelligence and security monitoring
Overview

What is Anywhere MCP Server?

Anywhere MCP Server is a Model Context Protocol (MCP) server designed for integrating 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.

How to use Anywhere MCP Server?

To use the Anywhere MCP Server, clone the repository, install the dependencies, configure your USM Anywhere credentials in a .env file, and start the server using npm start. You can then integrate it with your MCP clients by adding the server configuration.

Key features of Anywhere MCP Server?

  • OAuth 2.0 Authentication: Secure authentication using client credentials flow.
  • USM Anywhere API Integration: Access to alarms, events, and security data.
  • Legacy OTX Support: Backward compatibility with AlienVault OTX API.
  • Type-Safe: Built with TypeScript and Zod validation.
  • MCP Protocol: Standard Model Context Protocol implementation.

Use cases of Anywhere MCP Server?

  1. Integrating security monitoring data into custom applications.
  2. Automating the retrieval of security alarms and events.
  3. Enhancing threat intelligence capabilities with legacy OTX support.

FAQ from Anywhere MCP Server?

  • What is the purpose of the Anywhere MCP Server?

It provides secure access to security monitoring data from the USM Anywhere platform.

  • Is it necessary to have USM Anywhere credentials?

Yes, you need valid USM Anywhere credentials to access the API.

  • Can I use this server for legacy OTX API?

Yes, it supports backward compatibility with the AlienVault OTX API.

Project Info
Created At
a year ago
Updated At
a year ago
Author Name
javierb507
Star
0
Language
TypeScript
License
-
Category
security

Recommend Servers

View All
Tavily Mcp
@tavily-ai

JavaScript
a year ago
Bring your real authenticated browser session to AI coding agents. Local-first MCP server + Chrome MV3 extension. No cloud. No telemetry.
@Cubenest

peek records the user's actual logged-in browser (DOM via rrweb, console events, network metadata, optional response bodies via opt-in Deep capture) through a Chrome MV3 extension. The extension ships events through a native-messaging stdio bridge to a local MCP server (peek-mcp), which persists them to a SQLite database at ~/.peek/sessions.db. AI coding agents (Claude Code, Cursor, Cline, Windsurf) read sessions from the database via 10 MCP tools: Tool What it does list_recent_sessions List recently recorded sessions (id, origin, ts, event count). get_session_summary LLM-readable narrative summary of a session. get_session_console_errors Console errors recorded in a session. get_session_network_errors Failed/notable network requests in a session. get_user_action_before_error Last N user actions before a console error. generate_playwright_repro Generate a runnable Playwright test from a session. get_dom_snapshot Reconstruct the DOM at a given timestamp. query_dom_history Timeline of attribute/text changes for a selector. request_authorization Side-panel consent for write actions (Level 3). execute_action Dispatch a UI action (gated by permission level + destructive blocklist). Why local-first matters Every other "browser session for AI" tool ships to a vendor cloud. peek's SQLite + extension live on the user's machine — no remote endpoints, no telemetry. The privacy policy (docs/peek/PRIVACY_POLICY.md) is the source of truth. Install # 1. Add the MCP server to Claude Code claude mcp add peek -- npx -y @peekdev/mcp # 2. Install the Chrome extension from the Chrome Web Store # (link added once the CWS listing is approved)

a day ago