Read your EyalSec security events, machines, runs and rules from an AI assistant.
The io.github.EyalSec/eyalsec-mcp MCP server lets an AI assistant read EyalSec security events, machines, runs, and rules. It is accessed via MCP, acting as an interface to EyalSec data for downstream querying or analysis by an assistant.
🛠️ Key Features
Read EyalSec security events
Read EyalSec machines
Read EyalSec runs
Read EyalSec rules
🚀 Use Cases
Fetch EyalSec security events in an AI-assisted workflow
Retrieve machine information for investigation or review
Access historical or current run details
Obtain rule definitions to support analysis
⚡ Developer Benefits
Provides a structured MCP endpoint for EyalSec data access
Supports integration patterns where an AI assistant reads security context (events, machines, runs, rules)
⚠️ Limitations
Server description specifies reading data only (no write/update capabilities are stated)
Ask your AI assistant about your EyalSec account in plain words: "what critical events came in since Monday?", "show me the full trace for event 90210", "which machines need an update?". This server gives Claude, Cursor and any other MCP client read access to your events, machines, runs and rules through the EyalSec API, so the assistant you already use for code review can also help you triage what EyalSec found.
EyalSec follows untrusted data (requests, files, environment variables and more) through your running program and reports when it reaches a risky operation: a SQL query, a shell command, deserialization, a file path. Each event names the operation, the line of code, the value it received and where the untrusted part came from. This server reads those events; it never changes anything on your account.
What you need
An EyalSec account and an API key. Create the key on your dashboard under Settings > API access. A read-only key is all this server needs, and it is the one we recommend: see API keys.
Python 3.10 or newer, or uv, which runs the server without a separate install.
The server speaks MCP over stdio. Your client starts it with uvx eyalsec-mcp (or eyalsec-mcp after pipx install eyalsec-mcp) and passes the key in the environment.
Claude Code
bash
claude mcp add eyalsec -e EYALSEC_API_KEY=es2_your_read_only_key -- uvx eyalsec-mcp
Claude Desktop
Add this to claude_desktop_config.json (Settings > Developer > Edit Config), then restart Claude Desktop:
It calls the API once and prints the account it reached, the key's scope and the number of machines.
Settings
Variable
Required
Meaning
EYALSEC_API_KEY
yes
Your API key, from Settings > API access. Read-only is enough.
EYALSEC_URL
no
Your EyalSec address. Defaults to https://eyalsec.com; set it only if your account lives on another domain. Must be https://.
What it can do
Every tool is a read. The server has no code path that adds, changes or deletes anything, so even a full-access key cannot be used to write through it.
Tool
What it answers
search_events
Your events, newest or most severe first, with the events page's filters: product, severity, dates, machine, taint source, impact class, label, sink pattern, run, and the advanced condition builder. Follows the API's paging for you.
get_event
One event in full: stack trace, where the data came in, where the value was created, nearby source code when the machine sends it, your note, and the runs that produced it.
event_stats
The dashboard summary: totals, the last hour, day and week, top event types and a 14-day timeline.
event_counts
How many events each product's list holds, live versus suppressed, and the count toward your monthly quota.
list_event_names
The distinct sink labels across your events, handy for building a filter.
event_map
The es-python events as a graph: sources, the files data was read from, and the operations it reached.
list_runs
The program invocations behind your events, with their command lines (secrets masked).
ci_findings
What runs on one machine reported since a moment, counted by severity, with which findings are new.
list_machines
Every machine: status, OS target, product, installed and newest build, and whether an update is waiting.
supported_targets
The Linux distributions, architectures and Python versions es-python installs on.
Your profile and limits, your key's scope and expiry (never the key), setup progress, and the activity log.
Some things to try:
"Summarize this week's critical and high events by machine."
"Open the newest SQL injection event and explain the path from the request to the query."
"Which runs of app.py produced command-injection events yesterday?"
"Do any machines have an update waiting or an install stuck in pending?"
Safety notes
Events contain untrusted text. A value that reached a sink, a stack trace or a command line came from a monitored program and its inputs, which can include text an attacker wrote. The server tells the assistant to treat it as data, not instructions; keep human review on anything the assistant proposes to do with it.
Use a read-only key. It can read everything this server reads and nothing more. A key can also carry an expiry date.
The key stays with you. It is read from the environment, sent only to your EyalSec address over HTTPS, and never returned by any tool. Plain HTTP is refused except to localhost.
The API's rate limits apply. search_events reads at most 10 pages per call and hands back a cursor for the rest.