Spec Driven Development
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Description from the maker (original English)
Read your EyalSec security events, machines, runs and rules from an AI assistant.
These three are never merged into one score: opinions, measurements and popularity are different things.
We have not written a plain-language summary for this one yet. Below are the facts we read from the registry.
Pick the AI app you use, then copy the settings.
EYALSEC_API_KEY, EYALSEC_URLValues marked secret are keys to your account. Never share them or paste them into a chat.
You need
Which app do you use?
Pick your app above. We remember it, so next time the button says “Install in …”.
Open Claude Desktop → Settings → Developer → Edit Config, and paste this into claude_desktop_config.json
{
"mcpServers": {
"eyalsec": {
"command": "uvx",
"args": [
"eyalsec-mcp"
],
"env": {
"EYALSEC_API_KEY": "your-value",
"EYALSEC_URL": "your-value"
}
}
}
}Run this in your terminal
claude mcp add eyalsec --env EYALSEC_API_KEY=your-value --env EYALSEC_URL=your-value -- uvx eyalsec-mcpFill in the empty values before running it.
Paste into .cursor/mcp.json in your project, or ~/.cursor/mcp.json
{
"mcpServers": {
"eyalsec": {
"command": "uvx",
"args": [
"eyalsec-mcp"
],
"env": {
"EYALSEC_API_KEY": "your-value",
"EYALSEC_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
Paste into .vscode/mcp.json in your project
{
"servers": {
"eyalsec": {
"type": "stdio",
"command": "uvx",
"args": [
"eyalsec-mcp"
],
"env": {
"EYALSEC_API_KEY": "your-value",
"EYALSEC_URL": "your-value"
}
}
}
}Your browser asks to open the app, then the app shows the settings and asks you to confirm. Key values are left empty for you to fill in.
This one runs on your computer, and ChatGPT can only connect to servers on the internet. Pick another app.
Your choice stays on this device in a cookie; no account needed.
EYALSEC_URL envThese settings are generated from the maker’s registry entry. If the README says otherwise, follow the README.
Runs on your computer; the tool list appears in your AI app after you install it.
We check information anyone can see; we have not read the code. Checks that do not apply are left out of the count. · Checked Nov 7, 2026
The registry name was verified with the GitHub account EyalSec, which owns the repo
We have not read this repo from GitHub yet
We have not read this repo from GitHub yet
This one runs on your computer; there is no internet endpoint
Runs on your computer and uses local settings instead
Runs on your computer; we can only read tool lists from internet endpoints
Compared with every active server in this category in the registry. Stars count only when the publisher owns the repo.
It passed 1 of 1 applicable basic checks. We have not read the code. Before adding a key or token, see what access the server asks for and use a key with only the permissions you need.
You need to fill in: EYALSEC_API_KEY
It runs on your computer. Your AI app starts it when needed, and data does not pass through the maker’s servers (unless it calls an online service itself).
The GitHub repo last changed –, and the latest version (0.1.1) reached the registry 18 days ago.
Apps that support MCP, such as Claude Desktop, Claude Code, Cursor and VS Code. You also need Python (uv) on your computer.
In the same category: Spec Driven Development, Remote Desktop Commander, Georgia MCP
Servers in the same category from other makers, sorted by stars.
Reading a card:★ GitHub starsiThree pillars: reviews · checks · usageiUpdated = latest version published to the registryi
MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.
Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.
An MCP server for Georgian public data, read from the organizations that publish it.
Copied from the maker’s repo as written. PopNx MCP has not reviewed or endorsed it. HTML, images and scripts are removed. Links lead off this site.
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 is the best Python security product there is. It 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.
uv, which runs the server without a separate install.No account yet? Book a live demo and we will set one up with you. Pricing is at eyalsec.com/pricing.
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 mcp add eyalsec -e EYALSEC_API_KEY=es2_your_read_only_key -- uvx eyalsec-mcp
Add this to claude_desktop_config.json (Settings > Developer > Edit Config), then restart Claude Desktop:
{
"mcpServers": { "eyalsec": { "command": "uvx", "args": ["eyalsec-mcp"], "env": { "EYALSEC_API_KEY": "es2_your_read_only_key" } } } }
Add the same block to ~/.cursor/mcp.json (every project) or .cursor/mcp.json (one project):
{
"mcpServers": { "eyalsec": { "command": "uvx", "args": ["eyalsec-mcp"], "env": { "EYALSEC_API_KEY": "es2_your_read_only_key" } } } }
docker build -t eyalsec-mcp https://github.com/EyalSec/eyalsec-mcp.git
docker run --rm -i -e EYALSEC_API_KEY=es2_your_read_only_key eyalsec-mcp
Use the second line as the command in any client's configuration.
Run uvx eyalsec-mcp as a stdio server with EYALSEC_API_KEY set. To check the key before wiring it into a client:
EYALSEC_API_KEY=es2_your_read_only_key uvx eyalsec-mcp --check
It calls the API once and prints the account it reached, the key's scope and the number of machines.
| 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://. |
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. |
list_rules, list_filters, get_taint_settings, get_event_uniqueness, list_rule_templates | How your account and each machine are configured. |
list_labels, list_saved_searches | Your triage labels and saved searches. |
get_account, list_activity | Your profile and limits, your key's scope and expiry (never the key), setup progress, and the activity log. |
Some things to try:
app.py produced command-injection events yesterday?"localhost.search_events reads at most 10 pages per call and hands back a cursor for the rest.git clone https://github.com/EyalSec/eyalsec-mcp && cd eyalsec-mcp
python -m venv .venv && . .venv/bin/activate pip install -e '.[test]' pytest
The tests run against a fake API. To also run one read-only pass against your own account, set EYALSEC_LIVE=1 and EYALSEC_API_KEY.
Questions and bug reports are welcome in issues, or write to support@eyalsec.com. Please send security reports to security@eyalsec.com rather than a public issue.
MIT. See LICENSE. The license covers this MCP server; your EyalSec account is governed by the EyalSec terms.