# Crewhu (oci · ghcr.io/wyre-ai/crewhu-mcp:v2.0.4)

MCP server for Crewhu — customer feedback (CSAT/NPS), employee engagement, and gamification.

- Trust score: 54/100 (low)
- Change this week: +4
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-20

## Components

- oci · `ghcr.io/wyre-ai/crewhu-mcp:v2.0.4`: 54/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-crewhu-mcp/ghcr-io-wyre-ai-crewhu-mcp-v2-0-4.md), [page](https://verifymcp.io/servers/wyre-ai-crewhu-mcp/ghcr-io-wyre-ai-crewhu-mcp-v2-0-4)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/crewhu-mcp:v2.0.4`
- Transport: `stdio`

## Trust breakdown

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. Scores are 0–100 per category. Scoring method: https://verifymcp.io/docs/scoring (what has changed: https://verifymcp.io/docs/scoring/changelog)

Scored 2026-09-20.

- **Supply Chain Security**: 0/100
  - Malware scan not yet available for this package.
  - Known CVEs could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
  - Install-script risk not yet assessed.
  - Dependency health could not be checked: this artifact ships no SBOM, so there is no dependency list to read. Publishing one would let us assess it.
- **Provenance & Transparency**: 45/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - Clear OSI-approved license (Apache-2.0).
  - Actively maintained (last published 25 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 83/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 1309 tokens (~72/item across 18 items; 18 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 83/100
  - Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.
- **Capabilities**: 100/100
  - Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.

**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.

## Install

### How do I install the Crewhu MCP server?

Crewhu runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/crewhu-mcp:v2.0.4. Ready-made configuration for Claude, Cursor, VS Code, Codex and 3 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add wyre-ai-crewhu-mcp -- docker run --rm -i ghcr.io/wyre-ai/crewhu-mcp:v2.0.4
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-crewhu-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-crewhu-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-crewhu-mcp -- docker run --rm -i ghcr.io/wyre-ai/crewhu-mcp:v2.0.4
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "wyre-ai-crewhu-mcp": {
      "type": "local",
      "command": [
        "docker",
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
      ],
      "enabled": true
    }
  }
}
```

### Hermes

```yaml
mcp_servers:
  wyre-ai-crewhu-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-crewhu-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-crewhu-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
      ]
    }
  }
}
```

## Changelog

Every change recorded for this component, newest first. Days that predate change tracking, or that we cannot explain, say so: "we were watching and nothing happened" and "we were not watching" are different claims.

### 2026-09-20 (score 54, +1)

No change was recorded against any check on this day. Stability & Change Management went from 80 to 83. That category is still filling its 30-day observation window: 24 days of observed history at the previous scan, 25 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-18 (score 53, +1)

No change was recorded against any check on this day. Stability & Change Management went from 73 to 77. That category is still filling its 30-day observation window: 22 days of observed history at the previous scan, 23 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-16 (score 52, +1)

No change was recorded against any check on this day. Stability & Change Management went from 67 to 70. That category is still filling its 30-day observation window: 20 days of observed history at the previous scan, 21 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-14 (score 51, +1)

No change was recorded against any check on this day. Stability & Change Management went from 60 to 63. That category is still filling its 30-day observation window: 18 days of observed history at the previous scan, 19 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-12 (score 50, +1)

No change was recorded against any check on this day. Stability & Change Management went from 53 to 57. That category is still filling its 30-day observation window: 16 days of observed history at the previous scan, 17 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-09 (score 49, +1)

No change was recorded against any check on this day. Stability & Change Management went from 43 to 47. That category is still filling its 30-day observation window: 13 days of observed history at the previous scan, 14 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-07 (score 48, +1)

No change was recorded against any check on this day. Stability & Change Management went from 37 to 40. That category is still filling its 30-day observation window: 11 days of observed history at the previous scan, 12 at this one. The score rises as the window fills, whether or not the server changes.

### 2026-09-05 (score 47, +1)

No change was recorded against any check on this day. Stability & Change Management went from 30 to 33. That category is still filling its 30-day observation window: 9 days of observed history at the previous scan, 10 at this one. The score rises as the window fills, whether or not the server changes.

## MCP tools (18)

### `crewhu_surveys_list` (~157 tokens)

List customer surveys (CSAT responses) with optional filtering and pagination.

Input parameters:

- `include_inactive` (boolean): Include inactive/deleted surveys (default: false, meaning only active)
- `limit` (number): Results per page (default: 50, API max: 100)
- `sentiment` (string): Filter by rating sentiment (positive = rating 5, neutral = 0, negative = -5). Filtered client-side within the fetched page.
- `since` (string): Return surveys updated since this date (ISO string, e.g., "2026-01-01T00:00:00Z")
- `step` (number): Page number, 1-based (default: 1)

### `crewhu_surveys_get` (~31 tokens)

Get a specific survey by its ID

Input parameters:

- `id` (string, required): Survey ID (_id)

### `crewhu_surveys_search` (~84 tokens)

Search surveys by text in the customer comment, ticket summary, customer name, or ticket number. Searches within the most recent page of surveys (client-side; the API has no search endpoint).

Input parameters:

- `limit` (number): Surveys to fetch and search within (default: 100, API max: 100)
- `query` (string, required): Search query text

### `crewhu_surveys_detractors` (~71 tokens)

Get recent negative surveys (rating -5) for follow-up and service recovery

Input parameters:

- `limit` (number): Maximum number of results (default: 20, max: 100)
- `since` (string): Return detractors since this date (default: last 30 days)

### `crewhu_surveys_promoters` (~65 tokens)

Get recent positive surveys (rating 5) for recognition

Input parameters:

- `limit` (number): Maximum number of results (default: 20, max: 100)
- `since` (string): Return promoters since this date (default: last 30 days)

### `crewhu_users_list` (~93 tokens)

List employees/users with optional filtering and pagination

Input parameters:

- `department` (string): Filter by department name (exact match)
- `include_inactive` (boolean): Include inactive users (default: false, meaning only active)
- `limit` (number): Results per page (default: 50, API max: 100)
- `step` (number): Page number, 1-based (default: 1)

### `crewhu_users_get` (~29 tokens)

Get a specific user by ID

Input parameters:

- `id` (string, required): User ID (_id)

### `crewhu_users_search` (~85 tokens)

Search users by name, employee ID, department, position, or location (client-side within the fetched page; the API has no search endpoint)

Input parameters:

- `limit` (number): Users to fetch and search within (default: 100, API max: 100)
- `query` (string, required): Search query (name, employee ID, department, position, or location)

### `crewhu_badges_list` (~58 tokens)

List available badges and recognition elements

Input parameters:

- `limit` (number): Results per page (default: 50, API max: 100)
- `step` (number): Page number, 1-based (default: 1)

### `crewhu_badges_get` (~30 tokens)

Get details of a specific badge

Input parameters:

- `id` (string, required): Badge ID (_id)

### `crewhu_badges_history_list` (~118 tokens)

List badge award history (peer recognition feed)

Input parameters:

- `awarded_by` (string): Filter by the giver's user ID
- `badge_id` (string): Filter by specific badge ID
- `limit` (number): Results per page (default: 20, API max: 100)
- `since` (string): Return awards updated since this date (ISO string)
- `step` (number): Page number, 1-based (default: 1)
- `user_id` (string): Filter by recipient user ID

### `crewhu_badges_user_recognition` (~61 tokens)

Get all badge awards/recognition for a specific user

Input parameters:

- `limit` (number): Maximum number of results (default: 20, max: 100)
- `user_id` (string, required): User ID to get recognition for

### `crewhu_badges_update_contest` (~67 tokens)

Update contest target or settings (write operation)

Input parameters:

- `description` (string): Contest description
- `id` (string, required): Contest/badge ID to update
- `name` (string): Contest name
- `target` (number): New target value for the contest

### `crewhu_prizes_list` (~88 tokens)

List prizes in the reward catalog (the prize title is its description; prizes have no separate name field)

Input parameters:

- `available_only` (boolean): Show only active prizes (default: true)
- `limit` (number): Results per page (default: 50, API max: 100)
- `step` (number): Page number, 1-based (default: 1)

### `crewhu_prizes_get` (~30 tokens)

Get details of a specific prize

Input parameters:

- `id` (string, required): Prize ID (_id)

### `crewhu_prizes_history_list` (~122 tokens)

List prize redemption history

Input parameters:

- `limit` (number): Results per page (default: 20, API max: 100)
- `prize_id` (string): Filter by specific prize ID
- `since` (string): Return redemptions updated since this date (ISO string)
- `status` (string): Filter by redemption status (exact match; status values are account-specific)
- `step` (number): Page number, 1-based (default: 1)
- `user_id` (string): Filter by redeeming user ID

### `crewhu_prizes_user_redemptions` (~61 tokens)

Get prize redemption history for a specific user

Input parameters:

- `limit` (number): Maximum number of results (default: 20, max: 100)
- `user_id` (string, required): User ID to get redemptions for

### `crewhu_prizes_pending_redemptions` (~59 tokens)

Get pending prize redemptions for processing (statuses containing 'pend' are matched client-side within the fetched page)

Input parameters:

- `limit` (number): Maximum number of results (default: 50, max: 100)

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-crewhu-mcp/ghcr-io-wyre-ai-crewhu-mcp-v2-0-4#diagnostics

## Score history

- 2026-09-20: 54
- 2026-09-19: 53
- 2026-09-18: 53
- 2026-09-17: 52
- 2026-09-16: 52
- 2026-09-15: 51
- 2026-09-14: 51
- 2026-09-13: 50
- 2026-09-12: 50
- 2026-09-11: 49
- 2026-09-10: 49
- 2026-09-09: 49
- 2026-09-08: 48
- 2026-09-07: 48
- 2026-09-06: 47
- 2026-09-05: 47
- 2026-09-04: 46
- 2026-09-03: 46
- 2026-09-02: 42
- 2026-09-01: 42
- 2026-08-31: 42
- 2026-08-30: 42
- 2026-08-29: 42
- 2026-08-28: 42
- 2026-08-27: 42
- 2026-08-26: 42

## Common questions

### What is the Crewhu MCP server?

Crewhu is an MCP server listed in the public MCP registry as io.github.WYRE-AI/crewhu-mcp. MCP server for Crewhu, customer feedback (CSAT/NPS), employee engagement, and gamification. This page covers its container image (ghcr.io/wyre-ai/crewhu-mcp:v2.0.4).

### Is the Crewhu MCP server safe to use?

Crewhu scores 54 out of 100 on VerifyMCP. 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 Crewhu MCP server expose?

Crewhu exposes 18 tools: crewhu_surveys_list, crewhu_surveys_get, crewhu_surveys_search, crewhu_surveys_detractors, crewhu_surveys_promoters, and 13 more. Their descriptions and schemas cost roughly 1,309 tokens of context every time the server is loaded.

### Is the Crewhu MCP server still maintained?

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

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

## Links

- Repository: https://github.com/WYRE-AI/crewhu-mcp
- Changelog RSS feed: https://verifymcp.io/servers/wyre-ai-crewhu-mcp/ghcr-io-wyre-ai-crewhu-mcp-v2-0-4.xml
- Changelog JSON feed: https://verifymcp.io/servers/wyre-ai-crewhu-mcp/ghcr-io-wyre-ai-crewhu-mcp-v2-0-4.json
- HTML version of this page: https://verifymcp.io/servers/wyre-ai-crewhu-mcp/ghcr-io-wyre-ai-crewhu-mcp-v2-0-4