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.

crewchat

PYPI · CREWCHAT

One group chat for your AI coding agents: Claude Code and Cursor talk to each other and to you.

Available components

pypi · crewchat 67
67 Trust /100

Last scanned (1 hour ago)

Scores higher than 68% of PyPI servers

Category Communication

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 Security100
  • No malware found by supply-chain analysis.Pass
  • No known CVEs affecting this package version or its production dependencies.Pass
  • Runs setuptools.build_meta at install time, a recognised build step with no custom scripting around it. View diagnostics → Pass
  • No production dependencies, so there is no dependency health to assess. View diagnostics → Pass
Provenance & Transparency100
  • Source repository is publicly reachable at the declared URL. View diagnostics → Pass
  • Cryptographically verified build provenance (signed, bound to deepankar17/crewchat). View diagnostics → Pass
  • Clear OSI-approved license (MIT).Pass
  • Actively maintained (last published 1 days ago).Pass
  • Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability56
  • AI-judged instruction clarity (fair).Partial
  • Tool/resource definitions use about 42 tokens (~42/item across 0 items; 0 tools + 0 resources), lean.Pass
  • Nothing to assess: this server has no tools to check for usage examples. See how to fix → Fail
Stability & Change Management0
  • Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage0
  • Nothing to assess: this server exposes no tools, so there are no tool definitions to check for coverage.Fail
Tool Safety75
  • No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
  • Destructive-tool annotations not yet verified: our capture listed no tools, so there were no annotations to read.Unverified
  • An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities60
  • Spec-recency check failed: implements MCP spec 2025-06-18; the latest is 2026-07-28. See how to fix → Fail

Unverified: 1 category

A category scored 0 because we could not verify it: a data source with nothing on this package, evidence we could not reach, or a check we could not run. We only credit what we can confirm.

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.

  • 16 Oct 26 +15
    • Malware scan: unverified → pass ▲ security
  • 15 Oct 26 +2
    • Malware scan: pass → unverified ▼ security
    • Injection markers: unverified → pass ▲ security
    • First check of Judged manipulation: pass security
    • Stability: Stability not yet verified: not enough scan history yet (needs a 30-day window). security
    • MCP protocol: unverified → fail ▼ functional
    • Tool coverage: unverified → fail ▼ functional
    • First check of Destructive annotations: unverified functional
    • First check of Schema quality: fair functional
    • First check of Schema quality: unverified functional
    • First check of Schema quality: pass functional
    • Package version: 0.13.4 → 0.14.0 functional
  • 14 Oct 26 0
    • Stability: Stability not yet verified: this package installed, but its server did not start, so we have no schema to compare. security
    • Tool safety: Tool safety not yet verified: this package installed, but its server did not start, so we have no tool text to scan. security
    • Schema quality: Schema quality not yet verified: this package installed, but its server did not start, so we have no schema to assess. functional
    • Capabilities: Protocol version not yet verified: this package installed, but its server did not start, so we never saw its MCP handshake. functional
    • Tool coverage: Tool coverage not yet verified: this package installed, but its server did not start, so we have no tool definitions to assess. functional
  • 12 Oct 26 50

    First indexed and scored.

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 17 Oct 2026 · Analysed pypi/crewchat@0.14.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 deepankar17/crewchat
Certificate issuer https://token.actions.githubusercontent.com
Certificate SAN https://github.com/deepankar17/crewchat/.github/workflows/release-assets.yml@refs/tags/v0.14.0
Rekor log index 3267891964
Predicate type PyPI publish attestation https://docs.pypi.org/attestations/publish/v1
Subject digest sha256:d7ff27f4fb9670b38802e2ac8d7b491d8813ffddbaffa2aaaaf0209d1e492400

Background: How many MCP packages publish verified provenance →

Install scripts 1 script
Hook Tier Command
build_backend allowlisted setuptools.build_meta

Background: Why install scripts are a supply-chain risk →

Dependencies 0 packages
Packages resolved 0
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 →

The sandbox run completed and this package exposed no tools.

Install

How do I install the crewchat MCP server?

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

pypi · crewchat

# add to Claude Code
claude mcp add deepankar17-crewchat -- uvx crewchat
Common questions

What is the crewchat MCP server?

crewchat is an MCP server listed in the public MCP registry as io.github.deepankar17/crewchat. One group chat for your AI coding agents: Claude Code and Cursor talk to each other and to you. This page covers its PyPI package (crewchat).

Is the crewchat MCP server safe to use?

crewchat scores 67 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 17 October 2026. Its build provenance is signed and verified. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.

What tools does the crewchat MCP server expose?

crewchat exposes no tools. We connected to it and read its tool list, and it was empty, so it offers an MCP client nothing to call.

Is the crewchat MCP server still maintained?

crewchat is still listed as active in the MCP registry. We last reached this channel on 17 October 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 crewchat MCP server under?

crewchat declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.