Stepsecurity MCP Server

@stepsecurity/stepsecurity-mcp npm v0.1.0

Published by @stepsecurity — no publish provenance and no public repository, so the publisher could not be verified and the source cannot be independently located.

Model Context Protocol server for StepSecurity APIs

Trust grade
A
95/100
Last scanned get badge →
Trust
A · 95/100
Adoption risk for you: the threat score, then adjusted down for blast radius, publisher verification and how much the scan could see. Deterministic; every point is auditable.
Capability
Moderate
Blast radius if it went rogue — what the server’s tools could reach. Independent of trust.
Coverage
Source
How much the scan could actually inspect. Shallow coverage is stated, never hidden.
Share this Trust Score
𝕏 Share LinkedIn Reddit
A Why this grade threat 100 − adoption risk = 95/100

The grade answers one question — how safe is this server for you to adopt — so it is computed in two auditable stages. Nothing below is an opinion or an LLM's guess; every line is a real term the deterministic engine applied, and the same input always yields the same number.

1. Threat score — 100 − 0 = 100. What the published surface and source actually contain:

The deterministic scan raised no scored threat in the surface it inspected — the threat score stayed at 100. Capability observations and advisory notes are recorded but never lower it.

2. Client adoption risk — 100 − 5 = 95. Three small, subtract-only factors that reflect your risk in adopting it — a clean scan proves less on a powerful, unverified or barely-inspectable package, so the grade says so plainly:

PointsAdoption-risk factor
−3 capability blast radius (moderate) — client exposure if the model is manipulated
−2 publisher verification (unlinked) — no provenance/repo link, but the shipped source was fully read

Capability observations and info notes are shown under Findings but never scored. Open any row's finding below for the file, line and evidence behind a deduction.

Findings 0

✓ No findings. The scan raised nothing on this surface — see Coverage for how deep it could look.

Tools 30

Each tool and what it can reach — statically extracted from the published source.

  • list_secrets_in_build_logreads sensitive data
  • analyze_anomalous_calls_by_processno sensitive capability
  • check_ioc_in_baselineno sensitive capability
  • check_npm_package_exposureno sensitive capability
  • check_npm_package_on_dev_machinesno sensitive capability
  • check_pypi_package_exposureno sensitive capability
  • check_python_package_on_dev_machinesno sensitive capability
  • create_suppression_ruleno sensitive capability
  • delete_suppression_ruleno sensitive capability
  • describe_capabilitiesno sensitive capability
Show 20 more tools ↓
  • find_endpoint_calls_in_tenantno sensitive capability
  • find_repos_using_endpointno sensitive capability
  • get_my_tenantno sensitive capability
  • get_suppression_ruleno sensitive capability
  • get_threat_incidentno sensitive capability
  • list_anomalous_network_callsno sensitive capability
  • list_blocked_domain_callsno sensitive capability
  • list_detectionsno sensitive capability
  • list_github_api_calls_in_runno sensitive capability
  • list_https_outbound_callsno sensitive capability
  • list_imposter_commit_detectionsno sensitive capability
  • list_recent_workflow_runsno sensitive capability
  • list_suppression_rulesno sensitive capability
  • list_suspicious_process_eventsno sensitive capability
  • list_tenant_github_orgsno sensitive capability
  • list_threat_incidentsno sensitive capability
  • pingno sensitive capability
  • preview_suppression_ruleno sensitive capability
  • search_action_usageno sensitive capability
  • update_suppression_ruleno sensitive capability

What this scan could not see

Versions 1

Scan history per published version. The engine is deterministic — the same version always yields the same score, so a changed score means the package itself changed.

VersionScoreFindingsEngineScanned
v0.1.0 latest A 95/100 0 1.13.0 2026-09-07

Embed this score

Show this server's live Trust Score in your README, docs or website. The badge is served straight from the registry and updates automatically after every rescan — no API key needed. It links back to this page, so anyone who sees the grade can also read the findings behind it instead of taking a number on faith.

MCP Trust Score: A · 95/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/stepsecurity-stepsecurity-mcp/badge.svg)](https://mcptrustchecker.com/registry/stepsecurity-stepsecurity-mcp)
HTML
<a href="https://mcptrustchecker.com/registry/stepsecurity-stepsecurity-mcp"><img src="https://mcptrustchecker.com/registry/stepsecurity-stepsecurity-mcp/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/stepsecurity-stepsecurity-mcp/badge.json via https://img.shields.io/endpoint?url=…

Verify this score yourself

The score above is reproducible: the same package version always yields the same result. Run it locally or over the free API — no account, no LLM, fully deterministic.

npx mcptrustchecker scan @stepsecurity/stepsecurity-mcp --online

Use the free API → How scoring works

More in Security & Testing