Local MCP capabilities provider for Expo
Nothing to run from here
EyalSec is installed from its publisher's own source and answers where it runs, so this marketplace is not in the path of a single call. There is no address here to send one to, and a panel that pretended otherwise would be showing you an answer we made up. Install it and call it from your own client — the Installation tab has the entry for each one.
99/100
trust score
19
tools declared
local
runs on your machine
—
downloads a day
What it does
Read your EyalSec security events, machines, runs and rules from an AI assistant.
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'EYALSEC_API_KEY=${EYALSEC_API_KEY}' --transport stdio eyalsec-mcp '--' uvx eyalsec-mcp
# 2 — ask your agent for something these tools do
# search_events, get_event, event_stats and 16 more
It needs EYALSEC_API_KEY: this reads it from your environment, so export it first.
EyalSec costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
EYAll 1 server
EyalSec1 server
1 category
Collected from a public index. Nobody has claimed this account, so nothing here was written by its author — claim it if it is yours.
Installation
Where are you running it?
Every route below installs the same thing and ends at the same approval screen. This one runs on your machine: your client starts EyalSec as a process under your own user, with your files and your network, so the tool surface below is what it can do to your computer rather than to a server somewhere else. Its scan result is on the Security tab — read the surface before you approve it.
Claude Codedeclared by this listing
This is a public server: you run it yourself and this marketplace is not in the path. You need uv (docs.astral.sh/uv): uvx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads EYALSEC_API_KEY (Your EyalSec API key, from Settings > API access. A read-only key is enough) from your environment each time it starts the server, so the value stays out of its config: export it in your shell profile (macOS, Linux), or run setx EYALSEC_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'EYALSEC_API_KEY=${EYALSEC_API_KEY}' --transport stdio eyalsec-mcp '--' uvx eyalsec-mcpReconnect, or start a new session, and the tools appear in the model’s tool list.
Free on mcprush, and it runs from its publisher’s own package: this marketplace is not in the path, so there is no key of ours to hold and no card to add.
What it asks of you
It reaches a system of yours, so it needs your own credential rather than the publisher’s: EYALSEC_API_KEY — Your EyalSec API key, from Settings > API access. A read-only key is enough.. You set it in your own client’s config, on your machine — this marketplace never holds it.
What it writes
One config entry your client uses to start the process locally. A local server runs with your file system and your network, which is why it is priced without metering.
What you approve
19 tools, with what each one reads, writes and reaches shown before you agree — the same list on every route above. Read the tool surface.
Tool surface
What the model actually sees. Descriptions are diffed on every release — see version history.
List events from the EyalSec account, newest first, with the same filters as the dashboard's events page.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | no | — | |
| severity | no | — | |
| date_from | no | — | |
| date_to | no | — | |
| machine | no | — | |
| sources | no | — | |
| tags | no | — | |
| labels | no | — | |
| sink_include | no | — | |
| sink_exclude | no | — | |
| run_uid | no | — | |
| advanced | no | — | |
| bucket | no | — | |
| xss_only | boolean | no | Only es-chromium events whose sink can run script. Needs view='browser'. |
| sort | string | no | 'newest' (default) or 'severity' (most severe first). |
| cursor | string | no | next_cursor from a previous call with the same filters, to continue. |
| limit | integer | no | Stop once at least this many events are collected (whole pages of up to 100). |
| value_chars | integer | no | Cut each event's str_repr to this many characters (0 = no cut). |
Get one event's full detail: stack trace, where the data came in (origin), where the value was created, nearby source code when the machine sends it, your note, and the runs (program invocations) that produced it.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| event_id | integer | yes | The event id (the 'id' field of a search_events result). |
The dashboard summary: total hits, distinct event types, counts for the last hour, day and week, the top event types, recent events and a 14-day timeline.
No parameter schema on file.
How many events the account has: per product list, live versus suppressed, and the count toward the monthly event quota (pass view for the number one product's list is capped by).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | no | — | |
| bucket | no | — |
The distinct sink labels (the 'where' field) across the account's events, useful for building filters.
No parameter schema on file.
The es-python events as a graph: which sources untrusted data came from, which files it was read from, and which operations (sinks) it reached, each with event and hit counts and the worst severity.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| severity | no | — | |
| date_from | no | — | |
| date_to | no | — | |
| machine | no | — | |
| sources | no | — | |
| tags | no | — | |
| labels | no | — | |
| sink_include | no | — | |
| sink_exclude | no | — | |
| run_uid | no | — | |
| advanced | no | — | |
| bucket | no | — | |
| focus_source | string | no | Focus on one source category (or 'other') and list its newest events. |
| focus_file | string | no | Focus on one file path, exactly as listed in 'files'. |
| focus_sink | string | no | Focus on one sink, exactly as listed in 'sinks'. |
The runs behind the account's events, newest first. A run is one invocation of one monitored program, with its command line, how many distinct events it produced and how many times. Pass a run_uid to search_events to see only that run's events.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| machine | no | — | |
| q | string | no | A case-insensitive piece of the command line. |
| limit | integer | no | Rows per page. |
| before | string | no | next_before from a previous call, to continue. |
What programs on one es-python machine reported since a moment: counts by severity, how many are at or above a threshold, which ones no earlier run had reached, and the findings themselves (ids, not values).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| machine | string | yes | The machine's name. |
| since | string | yes | Start of the window: RFC3339 (2026-10-07T12:00:00Z), Unix seconds or an HTTP date. |
| min_severity | no | Threshold; the default is 'high'. | |
| limit | integer | no | How many findings to list, worst first. |
The account's saved events-page searches for one product.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| view | string | no | 'python' (default) or 'browser'. |
The account's triage labels (id, name, color). Use an id in search_events' labels filter.
No parameter schema on file.
Every machine on the account: name, status, public_id, OS target, installed and newest build, Python version, product, and flags for a clone, a stalled install or an old copy still reporting.
No parameter schema on file.
The Linux distributions, architectures and Python versions es-python can be installed for.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| os | string | no | An OS target such as 'ubuntu_24_04_x86_64' to list only the Python versions for it. |
The rules in one scope. Mode 1 = Hide, 2 = Show, 3 = Raise, 4 = Don't send.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| machine | no | — |
The account's event filters (standing blacklist or whitelist patterns on the events page).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| engine | string | no | 'python' or 'browser' for one product's Filters page. |
Which kinds of incoming data a scope treats as untrusted. Each setting is on, off or unset (unset inherits from the level above).
| Parameter | Type | Required | Notes |
|---|---|---|---|
| machine | no | — |
What makes two detections count as the same event for one product and scope.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| agent_kind | string | no | The product: 'python' or 'browser'. |
| machine | no | — |
Every rule template the account can see (its own and the EyalSec ones), with their rules and categories.
No parameter schema on file.
The account's profile, limits and permissions, the API key's scope and expiry (never the key itself), and how far es-python setup has got, with the next step.
No parameter schema on file.
The account's audit trail, newest first, 50 per page, kept for 30 days: sign-ins, machine changes, key generation and API calls.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| action | string | no | One exact action name, such as 'machine.create' or 'auth.login'. |
| outcome | string | no | Keep only this outcome. |
| before_ts | string | no | Next page: the 'time' of the last entry received. |
| before_id | integer | no | Next page: the 'id' of the last entry received. |
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under MIT
- Runs on your machine — nothing of it reaches our gateway
- Nothing to cap, because mcprush bills nothing
What counts against your monthly calls
| Tool | Unit | Calls used | Out of the allowance |
|---|
Nothing here is billable: mcprush charges nothing to install EyalSec or to call it, at any volume.
Call allowance · this installenforced at the gateway
Monthly allowance, in calls
—
—
Alert at 80% · then the tool returns a normal MCP error
Used this month: —
ATrust score 99 / 100
Release 0.1.0 · scanned 16 Oct 2026
Two independent axes, because powerful and malicious are different questions. The grade is threat only. The capability level is blast radius, and it is never a penalty on the grade — it is priced as one subtract-only term in the score, where you can see it.
Threat score100
Client score99
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationrepo
Surface digestec97fe2e060661d48041cd22b5d12e60206e7725910f3507783a20d507201ad5
Score vectorthreat 100 → client 99
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | repo | publisher verification (public source) — no provenance, but the source is public and inspectable | −1 |
| coverage-honesty | source | inspection depth (source) — how much of the target the scan could see | −0 |
score = clamp(round(threatScore − E_cap − E_ver − E_cov), 0, 100). No model, no opinion, no network call at scoring time: the same methodology version against the same bytes always produces this number, and every line above is a field of the report rather than a summary of it.
What the scan could actually read
A grade is only as meaningful as its coverage, so the scanner publishes its own depth before it publishes its result.
Tool surfaceread
Implementation sourceread
Package metadataread
Live transportnot available
Tools were statically extracted from the published source (19 recovered), not enumerated from a running server. Tool-poisoning, Unicode-smuggling, capability and toxic-flow analysis ran on this inferred surface, but a mis-parsed registration could be missed or mis-attributed, so tool-derived findings are capped below “confirmed”. To grade the real runtime surface, scan the running server: --command "npx -y <package>".
Capability — what it could do if the model were manipulated
Tags derived from each tool’s schema and the implementation, not from what the tool calls itself. minimal is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| search_events | no tags | |
| get_event | no tags | |
| event_stats | no tags | |
| event_counts | no tags | |
| list_event_names | no tags | |
| event_map | no tags | |
| list_runs | no tags | |
| ci_findings | no tags | |
| list_saved_searches | no tags | |
| list_labels | no tags | |
| list_machines | no tags | |
| supported_targets | no tags | |
| list_rules | no tags | |
| list_filters | no tags | |
| get_taint_settings | no tags | |
| get_event_uniqueness | no tags | |
| list_rule_templates | no tags | |
| get_account | no tags | |
| list_activity | no tags |
Toxic-flow graph
The lethal trifecta, checked as a graph rather than as a checklist: untrusted input, a sensitive source and an external sink have to meet before there is a path worth worrying about.
The public result for this release does not print the flow graph, so there is nothing to show here. That is not the same as "no paths were found": what the scan did read is above, under coverage.
Supply chain and provenance
Integrityfirst-seen
Surface digestec97fe2e060661d4
Scanned2026-10-16
This is the first scan of this surface here, so there is nothing yet to compare it against.
Every result on this tab comes from one deterministic pass over the published package — offline, rule by rule, and auditable line by line above. Same methodology version, same bytes, same score.
Release history
Always latest — the install command names no version, so it installs the newest release when it runs; the current release on file is 0.1.0. Pin a release below and the command asks for exactly that one.
0.1.0
undated
latestNo release note was published with this version.
—
no reviews yet
Who can review
One review per account, from a signed-in account that does not publish this listing. Nothing else is asked — you can say what you think before you install it. Publishers can reply once per review, and a review can be edited or deleted by whoever wrote it.
Sign in to write one
Any signed-in account that does not publish EyalSec can review it, once — before installing it or after. A review from an account that has installed it is marked as one.
No reviews yet
Nobody has reviewed this listing. The rating on the card is the mean of the reviews written here and nothing else, so there is no rating until somebody writes the first — which takes a signed-in account that does not publish it, and nothing else.