Skip to content
verify mcp Beta VerifyMCP is currently in beta. If you notice any issues, get in touch and we’ll put it right.

io.github.thomasxm/crowdsentinel-mcp-server

PYPI · CROWDSENTINEL-MCP-SERVER

AI threat hunting & incident response for Elasticsearch/OpenSearch with endpoint & network forensics

0 this week 0 Trust /100

Last scanned (13 hours ago)

Scores higher than 0% of PyPI servers

Category Security

Recent critical change

CVE-2026-32871 affects this package (4 Aug 2026). See the changelog before you install this server.

Trust breakdown (7 categories)

How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →

Supply Chain Security62
Provenance & Transparency97
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to thomasxm/CrowdSentinels-AI-MCP). View diagnostics → Pass
  • Clear OSI-approved license (GPL-3.0-only).Pass
  • Actively maintained (last published 108 days ago).Pass
  • Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability0
  • Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.Unverified
Stability & Change Management0
  • Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.Unverified
Tool Coverage0
  • Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.Unverified
Tool Safety0
  • Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.Unverified
Capabilities0
  • Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.Unverified

Unverified: 5 categories

Categories scored 0 because our sandbox has not given us the schema these checks need to read. That is a gap on our side rather than a finding about the package, and we only credit what we can confirm, so the score stands at 0 until the capture succeeds. We are working through the fleet, so this normally clears without any action from you. How we score packages →

What we tested

Checks we ran (8)

  • Malware scan
  • Known CVEs
  • Dependency health
  • Source repository
  • Provenance
  • License
  • Maintenance
  • Security disclosure

Checks we could not complete (6)

These are gaps on our side, not findings about this package. We only credit what we can confirm, so a category made up entirely of them scores 0.

  • Install scripts in Supply Chain SecurityInstall-script risk not yet assessed.
  • Schema quality in Schema Quality & AI Usability (scores 0 for this)Schema quality not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to assess.
  • Stability in Stability & Change Management (scores 0 for this)Stability not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no schema to compare.
  • Tool coverage in Tool Coverage (scores 0 for this)Tool coverage not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool definitions to assess.
  • Tool safety in Tool Safety (scores 0 for this)Tool safety not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we have no tool text to scan.
  • Capabilities in Capabilities (scores 0 for this)Protocol version not yet verified: this server's registry entry declares environment variables (an API key or similar), and its server did not start in our sandbox, so we never saw its MCP handshake.

Does not apply to this package (2)

  • Endpoint SecurityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.
  • Transport & ReachabilityScored on hosted endpoints only. A package has no live endpoint of its own for us to probe.

The score does not measure everything. What the score does not measure →

Changelog

Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.

  • 5 Nov 26 0
    • Malware scan: unverified → pass ▲ security
  • 3 Nov 26 0
    • Malware scan: pass → unverified ▼ security
  • 1 Nov 26 0
    • Malware scan: unverified → pass ▲ security
  • 31 Oct 26 0
    • Malware scan: pass → unverified ▼ security
  • 13 Oct 26 −34
    • Known CVEs: unverified → fail ▼ critical
    • Score status: scored → failed ▼ critical
    • Dependency health: unverified → 0.95 ▲ functional
  • 12 Oct 26 +34
    • Known CVEs: fail → unverified ▼ security
    • Dependency health: 0.95 → unverified ▼ functional
    • Score status: failed → scored ▲ functional
  • 4 Oct 26 0
    • Security disclosure: unverified → fail ▼ functional
  • 3 Oct 26 0
    • Security disclosure: fail → unverified ▼ functional
Diagnostics

Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.

Captured 5 Nov 2026 · Analysed pypi/crowdsentinel-mcp-server@0.6.0

Provenance Verified

A signed build attestation was found and verified, binding this exact artifact to the source repository it claims to come from.

Result Verified
Ecosystem pypi
Reason Verified
Discovered via Registry attestation endpoint
Source repo thomasxm/CrowdSentinels-AI-MCP
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/thomasxm/CrowdSentinels-AI-MCP/.github/workflows/pypi-publish.yaml@refs/heads/main
Rekor log index 2203595101
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:a1d8b6959b6d17eb1878af9eced3326eefb53f6ade5ada7e0d87277d504f5032

Background: How many MCP packages publish verified provenance →

Vulnerabilities 42 findings
ID CVE Severity Vector Fix available
GHSA-5h2m-4q8j-pqpj CVE-2025-69196 high yes
GHSA-c2jp-c369-7pvx high yes
GHSA-m8x7-r2rg-vh5g CVE-2025-64340 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
GHSA-mxxr-jv3v-6pgc CVE-2025-62800 medium yes
GHSA-rcfx-77hg-w2wv high yes
GHSA-rj5c-58rq-j5g5 CVE-2025-62801 medium yes
GHSA-rww4-4w9c-7733 CVE-2026-27124 high yes
GHSA-vv7q-7jx5-f767 CVE-2026-32871 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes
PYSEC-2026-1364 CVE-2025-62800 none yes
PYSEC-2026-1365 CVE-2025-62801 none yes
PYSEC-2026-2474 CVE-2025-69196 none yes
PYSEC-2026-2475 CVE-2025-64340 medium CVSS:3.1/AV:L/AC:H/PR:L/UI:R/S:U/C:H/I:H/A:H yes
PYSEC-2026-2476 CVE-2026-27124 none yes
PYSEC-2026-338 CVE-2026-32871 critical CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:C/C:H/I:H/A:H yes
GHSA-3qhf-m339-9g5v CVE-2025-53366 high yes
GHSA-5h93-6whr-6q8j CVE-2026-116685 medium CVSS:3.1/AV:N/AC:H/PR:N/UI:N/S:U/C:H/I:N/A:N yes
GHSA-84m7-p3x7-pcfv CVE-2026-59951 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-9h52-p55h-vw2f CVE-2025-66416 high yes
GHSA-j975-95f5-7wqh CVE-2025-53365 high yes
GHSA-jpw9-pfvf-9f58 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
GHSA-vj7q-gjh5-988w CVE-2026-59950 high yes
PYSEC-2026-1616 CVE-2025-53366 none yes
PYSEC-2026-1617 CVE-2025-66416 none yes
PYSEC-2026-1618 CVE-2025-53365 none yes
PYSEC-2026-3482 CVE-2026-52869 high CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:H/A:L yes
PYSEC-2026-3483 CVE-2026-59950 none yes
GHSA-mf9w-mj56-hr94 CVE-2026-28684 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H yes
PYSEC-2026-2270 CVE-2026-28684 medium CVSS:3.1/AV:L/AC:L/PR:L/UI:R/S:U/C:N/I:H/A:H yes
GHSA-2xpw-w6gg-jr37 CVE-2025-66471 high yes
GHSA-38jv-5279-wg99 CVE-2026-21441 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
GHSA-8988-9cw3-xx77 CVE-2026-97687 high yes
GHSA-gm62-xv2j-4w53 CVE-2025-66418 high yes
GHSA-pq67-6m6q-mj2v CVE-2025-50181 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N yes
GHSA-qccp-gfcp-xxvc CVE-2026-44431 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
GHSA-vxq7-64xx-v4gw CVE-2026-97689 high yes
PYSEC-2026-141 CVE-2026-44431 medium CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:L/I:N/A:N yes
PYSEC-2026-1994 CVE-2025-66471 none yes
PYSEC-2026-1996 CVE-2026-21441 high CVSS:3.1/AV:N/AC:L/PR:N/UI:N/S:U/C:N/I:N/A:H yes
PYSEC-2026-1998 CVE-2025-66418 none yes
PYSEC-2026-1999 CVE-2025-50181 medium CVSS:3.1/AV:N/AC:H/PR:L/UI:N/S:U/C:H/I:N/A:N yes
PYSEC-2026-4175 CVE-2026-97687 none yes
PYSEC-2026-4177 CVE-2026-97689 none yes

Background: What a vulnerability scan can and cannot prove →

Dependencies 73 packages
Packages resolved 73
Stale 8
Tree resolution Complete

Background: SBOMs and build attestations, explained →

MCP tools

The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →

Tools for package channels are captured by running the package in an isolated sandbox. The most recent sandbox run could not capture a tool list from this package.

Install

How do I install the io.github.thomasxm/crowdsentinel-mcp-server server?

io.github.thomasxm/crowdsentinel-mcp-server runs locally as a PyPI package, launched with uvx crowdsentinel-mcp-server. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

pypi · crowdsentinel-mcp-server

# add to Claude Code
claude mcp add thomasxm-crowdsentinel-mcp-server -- uvx crowdsentinel-mcp-server
Common questions

What is the io.github.thomasxm/crowdsentinel-mcp-server server?

io.github.thomasxm/crowdsentinel-mcp-server is listed in the public MCP registry as io.github.thomasxm/crowdsentinel-mcp-server. AI threat hunting & incident response for Elasticsearch/OpenSearch with endpoint & network forensics. This page covers its PyPI package (crowdsentinel-mcp-server).

Is the io.github.thomasxm/crowdsentinel-mcp-server server still maintained?

io.github.thomasxm/crowdsentinel-mcp-server is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

What licence is the io.github.thomasxm/crowdsentinel-mcp-server server under?

io.github.thomasxm/crowdsentinel-mcp-server declares the GPL-3.0-only licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.