EVE-Online-OSINT

This MCP server provides Open Source Intelligence (OSINT) capabilities for EVE Online by integrating data from ESI, EveWho, and zKillboard. It exposes three main OSINT tools: character-osint, corporation-osint, and alliance-osint. You can request intelligence by character, corporation, or alliance name to obtain a consolidated profile including public attributes, affiliations, and activity metrics gathered from multiple APIs. The tools are designed to resolve names to IDs and to return structured results such as birth dates, corporation histories, member rosters, alliance leadership, and recent killmails. Use the prompts to generate EVE OSINT reports with focus areas like membership, activity, history, and connections, or mix and match data sources for deeper context.

Prerequisites:

• Node.js 18+ (recommended)
• npm or pnpm
• Git

Installation steps:

1. Clone the repository (or set up via your package manager if distributing through npm):

git clone https://github.com/your-username/eve-online-osint-mcp.git
cd eve-online-osint-mcp

2. Install dependencies:

npm install

3. Configure environment if needed. The MCP supports ESI, EveWho, and zKillboard integrations. Set required API keys or placeholders as environment variables (see mcp_config env section below).

4. Run in development mode (for testing):

npm run dev

5. Run in production mode:

npm run start

Optional: If you prefer using Smithery for automatic installation, follow the Smithery instructions in the README.

Environment variables can be used to control API access and logging. Common options include:

• ESI_BASE_URL: Base URL for the EVE Swagger Interface (default https://esi.evetech.net)
• EVE_WHO_API_KEY: API key for EveWho data access
• ZKILLBOARD_API_KEY: API key for zKillboard data access
• LOG_LEVEL: Logging level (debug, info, warn, error)

Notes:

• The MCP is designed to respect API rate limits by coordinating requests across the included services.
• If any external API key is missing, the corresponding data source may be skipped with a warning, and the response will include available data.
• Ensure your Node.js process has appropriate network access and that API keys are kept secure (do not commit keys to version control).