Local MCP capabilities provider for Expo
Nothing to run from here
Security Engineer 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.
100/100
trust score
6
tools declared
local
runs on your machine
—
downloads a day
What it does
Fix GuardBee AI Security Engineer findings in your repo with your coding agent, then verify
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user --env 'GUARDBEE_API_KEY=${GUARDBEE_API_KEY}' --transport stdio security-engineer-mcp '--' npx -y @guardbee/mcp-security-engineer
# 2 — ask your agent for something these tools do
# list_assessments, get_assessment, detect_stack and 3 more
It needs GUARDBEE_API_KEY: this reads it from your environment, so export it first.
Security Engineer costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
GUAll 7 servers
GuardBee7 servers
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 Security Engineer 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 Node.js — the current LTS (24) is the safe choice; npx comes with it. Claude Code registers it in one command; --scope user makes it available in every project. Claude Code reads GUARDBEE_API_KEY (GuardBee API key with remediations.read and remediations.write scopes) 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 GUARDBEE_API_KEY … and open a new terminal (Windows). The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user --env 'GUARDBEE_API_KEY=${GUARDBEE_API_KEY}' --transport stdio security-engineer-mcp '--' npx -y @guardbee/mcp-security-engineerReconnect, 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: GUARDBEE_API_KEY — GuardBee API key with remediations.read and remediations.write scopes. 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
6 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.
Read from its source code. A server that builds its tool list when it starts can list more tools than this.
List recent GuardBee AI Security Engineer assessments of your workspace (id, site, status, risk level).
No parameter schema on file.
Get the actionable findings of an assessment, highest priority first, with the platforms each can be fixed on.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | Assessment id from list_assessments |
Detect how this repository is served (Next.js, Express, Nginx, Apache, Cloudflare) from its own files, and find web server config files to diff fixes against.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| projectPath | string | no | Repository root (default: current working directory) |
Get a reviewable fix for a finding, tailored to the platform. If configPath points to the project's Nginx/Apache config, GuardBee returns an exact diff. Returns step-by-step instructions for applying the change in this repository.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| runId | string | yes | — |
| findingId | string | yes | findingId from get_assessment |
| platform | string | no | Defaults to the platform detected on the live site |
| configPath | string | no | Nginx/Apache config file inside the project, for an exact diff |
| projectPath | string | no | — |
Record in GuardBee that the fix was applied in the repository (after the user approved the change). Pass the commit SHA or PR URL as ref.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| remediationId | string | yes | — |
| ref | string | no | — |
After the fix is deployed, ask GuardBee to re-run the check that reported the finding against the live site. Takes up to a few minutes.
| Parameter | Type | Required | Notes |
|---|---|---|---|
| remediationId | string | yes | — |
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 Security Engineer 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 100 / 100
Release 0.1.1 · scanned 7 Nov 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 score100
Findings0 threat · 0 capability
Capabilityminimal
Coveragesource
Verificationsource
Surface digest1b0193fcac7842b1d954395203ca9ef5f718f1dba990abaa87b1be04e8a4b07c
Score vectorthreat 100 → client 100
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | minimal | capability blast radius (minimal) — client exposure if the model is manipulated | −0 |
| verification-discount | source | publisher verification (provenance) — cryptographic build provenance ties the artifact to its source | −0 |
| 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 (6 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 |
|---|---|---|
| list_assessments | no tags | |
| get_assessment | no tags | |
| detect_stack | no tags | |
| get_fix | no tags | |
| report_applied | no tags | |
| verify_fix | 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 digest1b0193fcac7842b1
Scanned2026-11-07
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.1. Pin a release below and the command asks for exactly that one.
0.1.1
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 Security Engineer 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.