Stibo Step MCP Server

stibo-step-mcp-server npm v1.1.1

Published by akash25de — no publish provenance, so origin is unverified, but the source is public: the repository link below is self-declared yet readable, so you can inspect the code before adopting it.

Free, community-built MCP server for Stibo Systems STEP — connect any AI assistant to your STEP MDM/PIM instance

Trust grade
A
96/100
Last scanned get badge →
Trust
A · 96/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 = 96/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 − 4 = 96. 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
−1 publisher verification (public source) — no provenance, but the source is public and inspectable

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 77

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

  • download_asset_contentingests untrusted input
  • add_user_to_groupno sensitive capability
  • approve_objectno sensitive capability
  • batch_executeno sensitive capability
  • claim_workflow_taskno sensitive capability
  • create_assetno sensitive capability
  • create_classificationno sensitive capability
  • create_entityno sensitive capability
  • create_productno sensitive capability
  • create_referenceno sensitive capability
Show 67 more tools ↓
  • delete_assetno sensitive capability
  • delete_objectno sensitive capability
  • delete_referenceno sensitive capability
  • delete_valueno sensitive capability
  • disable_endpointno sensitive capability
  • disable_queueno sensitive capability
  • enable_endpointno sensitive capability
  • enable_queueno sensitive capability
  • execute_with_rollbackno sensitive capability
  • generate_business_rule_fileno sensitive capability
  • generate_stepxml_attribute_definitionno sensitive capability
  • generate_stepxml_basic_objectno sensitive capability
  • generate_stepxml_clear_attributesno sensitive capability
  • generate_stepxml_delete_data_containerno sensitive capability
  • generate_stepxml_lovno sensitive capability
  • get_active_configno sensitive capability
  • get_approval_statusno sensitive capability
  • get_assetno sensitive capability
  • get_asset_content_urlno sensitive capability
  • get_attributeno sensitive capability
  • get_background_processno sensitive capability
  • get_childrenno sensitive capability
  • get_classificationno sensitive capability
  • get_classification_childrenno sensitive capability
  • get_client_statsno sensitive capability
  • get_data_containersno sensitive capability
  • get_endpoint_statisticsno sensitive capability
  • get_endpoint_statusno sensitive capability
  • get_entityno sensitive capability
  • get_entity_childrenno sensitive capability
  • get_execution_reportno sensitive capability
  • get_graphql_schemano sensitive capability
  • get_incoming_referencesno sensitive capability
  • get_lovno sensitive capability
  • get_object_typeno sensitive capability
  • get_productno sensitive capability
  • get_queue_statusno sensitive capability
  • get_reference_typeno sensitive capability
  • get_reference_valueno sensitive capability
  • get_referencesno sensitive capability
  • get_system_infono sensitive capability
  • get_userno sensitive capability
  • get_user_groupno sensitive capability
  • get_valueno sensitive capability
  • get_workflowno sensitive capability
  • graphql_queryno sensitive capability
  • invoke_endpointno sensitive capability
  • list_background_process_typesno sensitive capability
  • list_contextsno sensitive capability
  • list_gateway_endpointsno sensitive capability
  • list_integration_endpointsno sensitive capability
  • list_workflowsno sensitive capability
  • remove_user_from_groupno sensitive capability
  • run_historic_changes_reportno sensitive capability
  • search_assetsno sensitive capability
  • search_classificationsno sensitive capability
  • search_entitiesno sensitive capability
  • search_productsno sensitive capability
  • search_workflow_tasksno sensitive capability
  • set_reference_valueno sensitive capability
  • set_valueno sensitive capability
  • trigger_exportno sensitive capability
  • trigger_importno sensitive capability
  • trigger_workflow_eventno sensitive capability
  • update_objectno sensitive capability
  • upload_asset_contentno sensitive capability
  • validate_stepxmlno 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
v1.1.1 latest A 96/100 0 1.13.0 2026-09-09

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 · 96/100
Markdown (GitHub README)
[![MCP Trust Score](https://mcptrustchecker.com/registry/stibo-step-mcp-server/badge.svg)](https://mcptrustchecker.com/registry/stibo-step-mcp-server)
HTML
<a href="https://mcptrustchecker.com/registry/stibo-step-mcp-server"><img src="https://mcptrustchecker.com/registry/stibo-step-mcp-server/badge.svg" alt="MCP Trust Score" height="20"></a>
Prefer shields.io styling? Point it at https://mcptrustchecker.com/registry/stibo-step-mcp-server/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 stibo-step-mcp-server --online

Use the free API → How scoring works

More in Developer Tools