Outsystems Mcp Extended MCP Server
outsystems-mcp-extended
npm
v1.0.0
Published by rpgomes-code — 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.
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:
| Points | Adoption-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
Tools 55
Each tool and what it can reach — statically extracted from the published source.
dep_deployment_analysis_startreads sensitive datamobile_build_logsingests untrusted inputmobile_build_statusingests untrusted inputasset_config_env_defaultsno sensitive capabilityasset_config_get_agentno sensitive capabilityasset_config_get_appno sensitive capabilityasset_getno sensitive capabilityasset_listno sensitive capabilityasset_revision_getno sensitive capabilityasset_revision_metadatano sensitive capability
Show 45 more tools ↓
asset_revision_release_notesno sensitive capabilityasset_revisions_listno sensitive capabilityasset_searchno sensitive capabilityauth_statusno sensitive capabilityauthenticateno sensitive capabilitycomplete_authenticationno sensitive capabilitydep_consumersno sensitive capabilitydep_deletion_analysis_startno sensitive capabilitydep_deletion_analysis_statusno sensitive capabilitydep_deployment_analysis_statusno sensitive capabilitydep_producersno sensitive capabilitydep_public_elements_searchno sensitive capabilitydep_referenced_elementsno sensitive capabilitydep_revision_public_elementsno sensitive capabilityenv_config_default_domainno sensitive capabilityenv_config_domains_listno sensitive capabilityenv_config_ip_filter_groups_listno sensitive capabilitymobile_build_listno sensitive capabilitymobile_build_startno sensitive capabilitymobile_build_validateno sensitive capabilitymobile_builder_versionsno sensitive capabilitymobile_config_android_getno sensitive capabilitymobile_config_android_patchno sensitive capabilitymobile_config_ios_getno sensitive capabilitymobile_config_ios_patchno sensitive capabilitymobile_version_suggestionsno sensitive capabilityportfolio_deployed_assetsno sensitive capabilityquality_analysis_statusno sensitive capabilityquality_analyze_startno sensitive capabilityquality_analyze_statusno sensitive capabilityquality_asset_summaryno sensitive capabilityquality_assets_metricsno sensitive capabilityquality_findingsno sensitive capabilityquality_findings_summaryno sensitive capabilityquality_findings_trendno sensitive capabilityquality_pattern_getno sensitive capabilityquality_patterns_listno sensitive capabilityuam_application_role_listno sensitive capabilityuam_application_role_usersno sensitive capabilityuam_groups_listno sensitive capabilityuam_organization_roles_listno sensitive capabilityuam_permissions_listno sensitive capabilityuam_user_application_rolesno sensitive capabilityuam_user_getno sensitive capabilityuam_user_searchno sensitive capability
What this scan could not see
- Tools were statically extracted from the published source (55 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>".
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.
| Version | Score | Findings | Engine | Scanned |
|---|---|---|---|---|
v1.0.0 latest |
A 96/100 | 0 | 1.10.0 | 2026-07-25 |
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.
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 outsystems-mcp-extended --onlineMore in Developer Tools
Security scan results for the 1stay MCP server.
Security scan results for the Adguard Home MCP server.
Security scan results for the Ado Browser MCP server.
Security scan results for the Adobe Experience Dev MCP server.
Security scan results for the Aemet MCP server.
Security scan results for the Affinity Mcp Bridge MCP server.