Local MCP capabilities provider for Expo
Nothing to run from here
Stepsecurity 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.
92/100
trust score
26
downloads a day
local
runs on your machine
655
downloads in 30d
What it does
Model Context Protocol server for StepSecurity APIs
Quickstart
# 1 — add it to Claude Code
claude mcp add --scope user stepsecurity-mcp '--' npx -y @stepsecurity/stepsecurity-mcp
# 2 — ask your agent for something these tools do
# ping, describe_capabilities, list_threat_incidents and 27 more
Stepsecurity costs nothing on mcprush: there is no plan to choose here, no cap to set and nothing mcprush can bill you for.
Publishernot claimed
STAll 1 server
@stepsecurity1 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 Stepsecurity 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. The '--' is in quotes so that PowerShell passes it on.
claude mcp add --scope user stepsecurity-mcp '--' npx -y @stepsecurity/stepsecurity-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 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
30 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.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
No parameter schema on file.
Free
$0 forever
- Every tool, no call limit
- No card, and mcprush charges nothing for it
- Source published under Apache-2.0
- 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 Stepsecurity 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 92 / 100
Release 0.1.0 · scanned 15 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 score92
Findings1 threat · 1 capability
Capabilityhigh
Coveragesource
Verificationnone
Surface digest8ec000acdf3ced783d599f985973849c8acd5ddf5bb9580c15ea64fe67f2042f
Score vectorthreat 100 → client 92
| Term | Level | What it prices | Points |
|---|---|---|---|
| capability-exposure | high | capability blast radius (high) — client exposure if the model is manipulated | −6 |
| verification-discount | none | publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read | −2 |
| 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 (30 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. high is the level these add up to.
| Tool | Capability tags | Why the tag was assigned |
|---|---|---|
| ping | no tags | |
| describe_capabilities | no tags | |
| list_threat_incidents | no tags | |
| get_threat_incident | no tags | |
| check_npm_package_exposure | no tags | |
| check_ioc_in_baseline | no tags | |
| search_action_usage | no tags | |
| list_detections | no tags | |
| check_npm_package_on_dev_machines | no tags | |
| check_pypi_package_exposure | no tags | |
| check_python_package_on_dev_machines | no tags | |
| list_anomalous_network_calls | no tags | |
| list_blocked_domain_calls | no tags | |
| list_https_outbound_calls | no tags | |
| list_suspicious_process_events | no tags | |
| list_secrets_in_build_log | sensitive-source | sensitive-source: keyword "list_secrets" |
| list_imposter_commit_detections | no tags | |
| get_my_tenant | no tags | |
| list_tenant_github_orgs | no tags | |
| list_recent_workflow_runs | no tags | |
| list_github_api_calls_in_run | no tags | |
| find_endpoint_calls_in_tenant | no tags | |
| find_repos_using_endpoint | no tags | |
| analyze_anomalous_calls_by_process | no tags | |
| list_suppression_rules | no tags | |
| get_suppression_rule | no tags | |
| preview_suppression_rule | no tags | |
| create_suppression_rule | external-sink | external-sink: handler sends an HTTP POST (request("POST", …)) at dist/server.js:1472 |
| update_suppression_rule | external-sink | external-sink: handler sends an HTTP PUT (request("PUT", …)) at dist/server.js:1540 |
| delete_suppression_rule | external-sink | external-sink: handler sends an HTTP DELETE (request("DELETE", …)) at dist/server.js:1573 |
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.
list_secrets_in_build_log → create_suppression_rule
A sensitive-source → external-sink chain exists: list_secrets_in_build_log → create_suppression_rule.
Supply chain and provenance
Integrityfirst-seen
Surface digest8ec000acdf3ced78
Scanned2026-10-15
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 Stepsecurity 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.