EyalSec

Name: EyalSec
Author: EyalSec

作者：EyalSec版本 0.1.1i★ –i在你的电脑上运行

注册名称io.github.EyalSec/eyalsec-mcp

安装

概览

作者提供的说明（英文原文）

Read your EyalSec security events, machines, runs and rules from an AI assistant.

PopNx MCP 的三大支柱

这三项永远不会合并成一个分数：意见、测量和人气是不同的东西。

用户评价i暂无评价评价功能将在后续阶段与账户功能一起开放
我们的基础检查i1 项中通过 1 项依据公开信息检查；尚未扫描代码
使用情况i尚未统计★ –

它能帮你做什么

我们还没有为它写通俗的介绍。下面是我们从注册中心读取到的事实。

连接方式: 在你的电脑上运行
传输方式: stdio
分类: 其他
你需要填写：EYALSEC_API_KEY

安装

选择你使用的 AI 应用，然后复制设置。

安装之前

基础检查：1 项中通过 1 项
在你的电脑上运行，拥有你的用户账户的权限（文件、网络、应用）。
需要你自己填写： EYALSEC_API_KEY, EYALSEC_URL

标为机密的值是你账户的钥匙。千万不要分享给别人，也不要粘贴到聊天里。

你需要

PyPI已安装 Python 的 uv（用于 uvx 命令）

你用的是哪个应用？

ClaudeClaude CodeCursorVS CodeChatGPT

在上方选择你的应用。我们会记住它，下次按钮会显示“安装到 …”。

打开 Claude Desktop → Settings → Developer → Edit Config，把下面的内容粘贴到 claude_desktop_config.json

{
  "mcpServers": {
    "eyalsec": {
      "command": "uvx",
      "args": [
        "eyalsec-mcp"
      ],
      "env": {
        "EYALSEC_API_KEY": "your-value",
        "EYALSEC_URL": "your-value"
      }
    }
  }
}

在终端中运行这条命令

claude mcp add eyalsec --env EYALSEC_API_KEY=your-value --env EYALSEC_URL=your-value -- uvx eyalsec-mcp

运行前请先填写空着的值。

在 Cursor 中打开

或者自己复制设置

粘贴到项目中的 .cursor/mcp.json，或 ~/.cursor/mcp.json

{
  "mcpServers": {
    "eyalsec": {
      "command": "uvx",
      "args": [
        "eyalsec-mcp"
      ],
      "env": {
        "EYALSEC_API_KEY": "your-value",
        "EYALSEC_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

在 VS Code 中打开

或者自己复制设置

粘贴到项目中的 .vscode/mcp.json

{
  "servers": {
    "eyalsec": {
      "type": "stdio",
      "command": "uvx",
      "args": [
        "eyalsec-mcp"
      ],
      "env": {
        "EYALSEC_API_KEY": "your-value",
        "EYALSEC_URL": "your-value"
      }
    }
  }
}

浏览器会先询问是否打开应用，然后应用会显示设置并请你确认。密钥的值会留空，由你自己填写。

这个服务器在你的电脑上运行，而 ChatGPT 只能连接互联网上的服务器。请选择其他应用。

你的选择通过 Cookie 保存在这台设备上，无需账户。

需要你填写的值

EYALSEC_API_KEY 机密必填 env
Your EyalSec API key, from Settings > API access. A read-only key is enough.
EYALSEC_URL env
Your EyalSec address, if your account is not on https://eyalsec.com.

这些设置是根据作者在注册中心的条目生成的。如果 README 的写法不同，请以 README 为准。

它能做什么

它在你的电脑上运行；安装后，工具列表会显示在你的 AI 应用中。

基础检查i

我们检查的是任何人都能看到的信息；我们没有阅读代码。不适用的检查项不计入总数。 · 检查于 2026年11月7日

✓ 通过
作者与仓库一致
注册名称已通过 GitHub 账户 EyalSec 验证，该账户拥有此仓库
… 尚未检查
仍在维护
我们还没有从 GitHub 读取这个仓库
… 尚未检查
有许可证
我们还没有从 GitHub 读取这个仓库
– 不适用
端点有响应
它在你的电脑上运行，没有互联网端点
– 不适用
使用 OAuth 登录
在你的电脑上运行，改用本地设置
… 尚未检查
工具描述中没有隐藏指令
它在你的电脑上运行；我们只能读取互联网端点的工具列表

与“其他”中的其他服务器比较i

星标数多于此分类中其他 32606 个服务器的 0%
发布到注册中心的时间比此分类中其他 32606 个服务器的 67% 更新
基础检查结果等于或优于此分类中其他 32606 个服务器的 100%

与注册中心里这个分类中所有活跃的服务器比较。只有当发布者拥有该仓库时，星标数才计入。

常见问题

EyalSec 安全吗？

它在 1 项适用的基础检查中通过了 1 项。我们没有阅读代码。在添加密钥或令牌之前，请先看看这个服务器要求哪些权限，并使用只具备所需权限的密钥。

它需要哪些密钥或代码？

你需要填写：EYALSEC_API_KEY

它在我的电脑上运行还是在云端？

它在你的电脑上运行。你的 AI 应用会在需要时启动它，数据不会经过作者的服务器（除非它自己调用在线服务）。

它还在维护吗？

GitHub 仓库最后更新于–，最新版本（0.1.1）于18天前进入注册中心。

哪些应用可以使用它？

支持 MCP 的应用，例如 Claude Desktop、Claude Code、Cursor 和 VS Code。你的电脑上还需要有 Python (uv)。

有什么可以替代它？

同一分类中有：Spec Driven Development, Remote Desktop Commander, Georgia MCP

替代选择

同一分类中其他作者的服务器，按星标数排序。

如何看卡片：★ GitHub 星标i三大支柱：评价 · 检查 · 使用情况i更新 = 最新版本发布到注册中心的时间i

Spec Driven Development

作者：formulahendry

MCP Server that facilitates spec-driven development workflows, not just Vibe Coding.

在你的电脑上运行★ 440MIT14个月前更新

安装

Remote Desktop Commander

作者：desktop-commander

Remote Desktop Commander: use files, terminal and processes on your own computers from any AI app.

在云端运行★ 211前天更新

安装

Georgia MCP

作者：abgeo

An MCP server for Georgian public data, read from the organizations that publish it.

电脑或云端今天更新

安装

作者的 README

打开 README

按原文从作者的仓库复制。PopNx MCP 没有审查或背书其内容。HTML、图片和脚本已被移除。链接会离开本站。

EyalSec MCP server

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.

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.

No account yet? Book a live demo and we will set one up with you. Pricing is at eyalsec.com/pricing.

Set it up

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

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:

"mcpServers": { "eyalsec": { "command": "uvx", "args": ["eyalsec-mcp"], "env": { "EYALSEC_API_KEY": "es2_your_read_only_key" } } } }

Cursor

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

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.

Any other MCP client

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.

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.
`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:

"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.

Development

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.

Help

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.

License

MIT. See LICENSE. The license covers this MCP server; your EyalSec account is governed by the EyalSec terms.