Crewhu
OCI · GHCR.IO/WYRE-AI/CREWHU-MCP:V2.0.4 · SCANNED SEP 20
MCP server for Crewhu — customer feedback (CSAT/NPS), employee engagement, and gamification.
Available components
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 Security0
- Malware scan not yet available for this package.Unverified
- 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.Unverified
- Install-script risk not yet assessed.Unverified
- 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.Unverified
Provenance & Transparency45
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (Apache-2.0).Pass
- Actively maintained (last published 25 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability83
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 1309 tokens (~72/item across 18 items; 18 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management83
- Stability observed for 25 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 18 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 18 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
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.
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.
oci · ghcr.io/wyre-ai/crewhu-mcp:v2.0.4
claude mcp add wyre-ai-crewhu-mcp -- docker run --rm -i ghcr.io/wyre-ai/crewhu-mcp:v2.0.4
{
"mcpServers": {
"wyre-ai-crewhu-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
]
}
}
} {
"servers": {
"wyre-ai-crewhu-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
]
}
}
} codex mcp add wyre-ai-crewhu-mcp -- docker run --rm -i ghcr.io/wyre-ai/crewhu-mcp:v2.0.4
{
"$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
}
}
} mcp_servers:
wyre-ai-crewhu-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"] {
"McpServers": {
"wyre-ai-crewhu-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
]
}
}
} {
"mcpServers": {
"wyre-ai-crewhu-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/crewhu-mcp:v2.0.4"
]
}
}
} 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.
- 20 Sept 26 +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.
- 18 Sept 26 +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.
- 16 Sept 26 +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.
- 14 Sept 26 +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.
- 12 Sept 26 +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.
- 9 Sept 26 +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.
- 7 Sept 26 +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.
- 5 Sept 26 +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.
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 20 Sept 2026 · Analysed oci/ghcr.io/wyre-ai/crewhu-mcp:v2.0.4
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | oci |
| Reason | No attestation published |
Background: How many MCP packages publish verified provenance →
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 →
crewhu_badges_get ~30
Get details of a specific badge
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Badge ID (_id) |
No output schema declared.
No examples provided.
crewhu_badges_history_list ~118
List badge award history (peer recognition feed)
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
crewhu_badges_list ~58
List available badges and recognition elements
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Results per page (default: 50, API max: 100) |
| step | number | – | Page number, 1-based (default: 1) |
No output schema declared.
No examples provided.
crewhu_badges_update_contest ~67
Update contest target or settings (write operation)
| Name | Type | Req | Description |
|---|---|---|---|
| description | string | – | Contest description |
| id | string | yes | Contest/badge ID to update |
| name | string | – | Contest name |
| target | number | – | New target value for the contest |
No output schema declared.
No examples provided.
crewhu_badges_user_recognition ~61
Get all badge awards/recognition for a specific user
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 20, max: 100) |
| user_id | string | yes | User ID to get recognition for |
No output schema declared.
No examples provided.
crewhu_prizes_get ~30
Get details of a specific prize
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Prize ID (_id) |
No output schema declared.
No examples provided.
crewhu_prizes_history_list ~122
List prize redemption history
| Name | Type | Req | Description |
|---|---|---|---|
| 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 |
No output schema declared.
No examples provided.
crewhu_prizes_list ~88
List prizes in the reward catalog (the prize title is its description; prizes have no separate name field)
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
crewhu_prizes_pending_redemptions ~59
Get pending prize redemptions for processing (statuses containing 'pend' are matched client-side within the fetched page)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 50, max: 100) |
No output schema declared.
No examples provided.
crewhu_prizes_user_redemptions ~61
Get prize redemption history for a specific user
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 20, max: 100) |
| user_id | string | yes | User ID to get redemptions for |
No output schema declared.
No examples provided.
crewhu_surveys_detractors ~71
Get recent negative surveys (rating -5) for follow-up and service recovery
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 20, max: 100) |
| since | string | – | Return detractors since this date (default: last 30 days) |
No output schema declared.
No examples provided.
crewhu_surveys_get ~31
Get a specific survey by its ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | Survey ID (_id) |
No output schema declared.
No examples provided.
crewhu_surveys_list ~157
List customer surveys (CSAT responses) with optional filtering and pagination.
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
crewhu_surveys_promoters ~65
Get recent positive surveys (rating 5) for recognition
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Maximum number of results (default: 20, max: 100) |
| since | string | – | Return promoters since this date (default: last 30 days) |
No output schema declared.
No examples provided.
crewhu_surveys_search ~84
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).
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Surveys to fetch and search within (default: 100, API max: 100) |
| query | string | yes | Search query text |
No output schema declared.
No examples provided.
crewhu_users_get ~29
Get a specific user by ID
| Name | Type | Req | Description |
|---|---|---|---|
| id | string | yes | User ID (_id) |
No output schema declared.
No examples provided.
crewhu_users_list ~93
List employees/users with optional filtering and pagination
| Name | Type | Req | Description |
|---|---|---|---|
| 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) |
No output schema declared.
No examples provided.
crewhu_users_search ~85
Search users by name, employee ID, department, position, or location (client-side within the fetched page; the API has no search endpoint)
| Name | Type | Req | Description |
|---|---|---|---|
| limit | number | – | Users to fetch and search within (default: 100, API max: 100) |
| query | string | yes | Search query (name, employee ID, department, position, or location) |
No output schema declared.
No examples provided.
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.