CanopiiCanopiiAll serversEnterprise →
io.github.thomasxm/crowdsentinel-mcp-server

io.github.thomasxm/crowdsentinel-mcp-server v0.6.0

Security Trust Score
Grade B · Moderate posture
Tier 1 · Public sourceHigh confidence · 92%
Declared MCP capabilities

Host io.github.thomasxm/crowdsentinel-mcp-server in a governed environment — SSO in front, every tool call attributed and audited.

Reputation205stars32forks1open issues39d agolast commit<1yage

Security controls

Deterministic, evidence-backed. Score earned from passing controls; a failed guard caps it.

Model–MCP Runtime Guardrails

  • Warn
    Strict JSON Schema Enforcementschemas not strict

    Tool inputs are constrained (additionalProperties:false), so unexpected arguments can't be smuggled in.

    Fix: Set additionalProperties:false and require explicit parameters on every tool.

  • Warn
    Tool Definition Integrityguard5 tool description(s) drifted after publish (no risk signals in diff)

    Every consecutive version pair is diffed for new injection markers or destructive scope — a risky diff anywhere in history is a rug-pull (fail, durable); benign description drift warns.

    correlate_siem_with_endpointendpoint_to_siem_pivotcreate_investigationgenerate_investigation_report

    Fix: Never add hidden directives or destructive scope to an already-published tool; document description changes in release notes.

  • Pass
    Indirect Prompt Injection (IPI) Defensesguardno injection markers

    Tool/prompt/resource text is free of hidden instructions that could hijack the agent.

  • Pass
    User-in-the-Loop / Approval Scopeguardno destructive tool scope

    No over-broad or destructive tools (arbitrary shell, bulk-delete) that warrant human approval.

Application Security Checks

  • Warn
    No known-vulnerable dependencies15 of 120 runtime deps vulnerable; worst critical

    Runtime dependencies (parsed from the lockfile) are scanned against OSV.dev for published CVEs. Advisory: flagged dependencies lower the score but don't hard-cap it, since transitive reachability is unproven.

    [email protected] — GHSA-7432-952r-cw78[email protected] — GHSA-9ggr-2464-2j32[email protected] — GHSA-fg6f-75jq-6523[email protected] — GHSA-g7f3-828f-7h7m

    Fix: Upgrade the flagged dependencies past their fixed versions.

  • Warn
    Established maintainerrecently published

    Brand-new / single anonymous maintainers raise takeover and malware risk.

    Fix: Publish under an established account/org; add multiple maintainers.

  • Warn
    Has a security policyno security policy

    A SECURITY.md gives a private path to report vulnerabilities.

    Fix: Add SECURITY.md with a disclosure contact and process.

  • Pass
    No command-injection sinksguardno sinks found

    Untrusted tool input reaching a shell yields remote code execution.

  • Pass
    No dynamic code executionguardno sinks found

    eval()/exec()/Function() on tool-derived strings allows arbitrary code execution.

  • Pass
    No path traversalguardno sinks found

    Naive path checks let tools read/write outside intended directories (EscapeRoute-class).

  • Pass
    No SSRF sinksguardno sinks found

    Fetching tool-supplied URLs can pivot into internal networks and metadata services.

  • Pass
    No unsafe deserializationguardno sinks found

    pickle/yaml.load/etc. on untrusted data can execute code.

  • Pass
    No committed secretsguardno secrets found

    Hardcoded keys/tokens in published source are live credentials an attacker can use.

  • Pass
    Credentials sourced from environmentreads credentials from environment

    Reading secrets from env/secret stores avoids hardcoding them.

  • Pass
    Dependencies pinned (lockfile)lockfile present

    A lockfile makes installs reproducible and resistant to silent dependency swaps.

  • Pass
    Package name not typosquattingguarddistinct package name

    Names mimicking popular packages are a common malware delivery vector.

  • Pass
    Actively maintainedrecent commits

    Unmaintained servers don't receive security fixes.

  • Pass
    Repository not archivedguardactive

    Archived repositories will never be patched.

  • Pass
    Declares a licenseGPL-3.0

    A clear license is required for legal enterprise use.

  • Pass
    Adoption & popularityestablished adoption

    A small, capped nudge from stars/downloads — widely-used servers get more eyes on bugs. It can never offset a real security failure.

  • Not checked
    No install/post-install scriptsguardnot determinable from PyPI metadata

    install hooks run arbitrary code on every consumer at install time.

  • Not checked
    Published with provenancenot determinable

    Build provenance attests the artifact was built from the claimed source by CI.

  • Not checked
    Signed releasesnot evaluated

    Signed releases let consumers verify artifacts weren't tampered with.

Transport & Trust Model

  • Warn
    Execution Sandboxingruns natively (no container image)

    A container/sandbox image limits blast radius; a server that runs natively has full host access.

    Fix: Ship a Dockerfile/Containerfile (or document a sandboxed run) so the server runs isolated.

  • Warn
    Network Exposurebinds 0.0.0.0

    Binding 0.0.0.0 or exposing debug inspectors widens the attack surface.

    Fix: Bind to 127.0.0.1 by default; never ship open debug endpoints.

  • N/A
    Transport Encryption (TLS)guardno remote endpoints

    Plaintext HTTP exposes traffic and bearer tokens to interception.

  • N/A
    IAM / Authentication Scopingno remote endpoints

    OAuth 2.1 / Protected Resource Metadata gates who can invoke tools.

  • N/A
    Live Endpoint Reachablenot dynamically scanned

    A dynamic scan connected to the declared remote endpoint and it responded — verified live, not a dead URL.

  • N/A
    Authentication Enforced (live)not dynamically scanned

    If the server declares auth is required, it must actually reject anonymous clients. Serving tools to unauthenticated callers is a real exposure.

Tools (80)

get_aliasget_indexput_aliaseql_deleteeql_searchesql_queryexport_iocscreate_indexdelete_aliasdelete_indexget_documentlist_aliaseslist_indicesquick_triageosquery_queryosquery_userseql_get_statusindex_documentiterative_huntcleanup_storagedelete_by_querydelete_documentget_data_streamget_shared_iocslist_esql_huntsosquery_socketsget_rule_detailsget_saved_assetsmy_new_operationsearch_documentscorrelate_by_timeexecute_esql_huntget_cluster_statsget_field_mappingosquery_processescheck_esql_supportcreate_data_streamdelete_data_streamget_cluster_healthget_index_metadataget_schema_detailssearch_ioc_in_evtxclose_investigationdiscover_all_assetsgeneral_api_requestget_indices_by_typeget_rule_statisticslist_investigationsbulk_index_documentscreate_investigationlist_detection_rulesresume_investigationdiscover_esql_indicesget_esql_hunt_detailshunt_with_sigma_rulesbuild_unified_timelineendpoint_hunt_from_iocendpoint_to_siem_pivotexecute_detection_ruleexecute_multiple_ruleslist_available_schemassuggest_rules_for_datavalidate_rule_for_datadetect_schema_for_indexget_diamond_model_guideget_investigation_queryget_kill_chain_overviewhunt_with_rule_categoryinvestigate_with_promptmap_events_to_kill_chainadd_iocs_to_investigationget_investigation_summaryget_pyramid_of_pain_guideget_esql_execution_historyget_progressive_disclosureshow_investigation_promptsstart_guided_investigationcorrelate_siem_with_endpointsearch_rules_by_mitre_attackgenerate_investigation_report

AI-flagged — for review

Observations from an AI review of tool descriptions. These are advisory only and do not affect the score — they can be noisy and need human judgement.

  • info
    Tool "correlate_siem_with_endpoint" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "endpoint_to_siem_pivot" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

  • info
    Tool "create_investigation" description changed after publish

    Benign definition drift: the description changed vs the prior version with no risk signals in the diff. Clients approve tools by name and don't re-review on update, so the change is invisible to existing grants.

Show 2 more