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.

Crewhu

OCI · GHCR.IO/WYRE-TECHNOLOGY/CREWHU-MCP:V2.0.3

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

−2 this week 48 Trust /100

Last scanned (23 hours ago)

Scores higher than 70% of OCI servers

Category CRM and Sales

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 Security0
  • No malware scan is available for this kind of package: the supply-chain vendors we use do not cover it. This is a permanent gap in our coverage, not a finding about the package.Unverified
  • Known CVEs could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
  • Install-script risk not yet assessed.Unverified
  • Dependency health could not be checked: this artifact ships no SBOM or dependency manifest, so there is no dependency list to read.Unverified
Provenance & Transparency19
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.

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 −3
    • Stability: pass → 0.83 functional
  • 15 Oct 26 +1
    • Stability: 0.97 → pass security
  • 13 Oct 26 +1

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

  • 12 Oct 26 +1

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

  • 10 Oct 26 −2

    No change was recorded against any check on this day. Stability & Change Management went from 97 to 83.

  • 6 Oct 26 +1

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

  • 4 Oct 26 +1

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

  • 3 Oct 26 0
    • Source repository: unverified → fail ▼ security
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 16 Oct 2026 · Analysed oci/ghcr.io/wyre-technology/crewhu-mcp:v2.0.3

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 →

MCP tools · 18 exposed · ~1,309 tokens

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 →

Tool Tokens
crewhu_badges_get ~30

Get details of a specific badge

NameTypeReqDescription
idstringyesBadge ID (_id)

No output schema declared.

No examples provided.

crewhu_badges_history_list ~118

List badge award history (peer recognition feed)

NameTypeReqDescription
awarded_bystring–Filter by the giver's user ID
badge_idstring–Filter by specific badge ID
limitnumber–Results per page (default: 20, API max: 100)
sincestring–Return awards updated since this date (ISO string)
stepnumber–Page number, 1-based (default: 1)
user_idstring–Filter by recipient user ID

No output schema declared.

No examples provided.

crewhu_badges_list ~58

List available badges and recognition elements

NameTypeReqDescription
limitnumber–Results per page (default: 50, API max: 100)
stepnumber–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)

NameTypeReqDescription
descriptionstring–Contest description
idstringyesContest/badge ID to update
namestring–Contest name
targetnumber–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

NameTypeReqDescription
limitnumber–Maximum number of results (default: 20, max: 100)
user_idstringyesUser ID to get recognition for

No output schema declared.

No examples provided.

crewhu_prizes_get ~30

Get details of a specific prize

NameTypeReqDescription
idstringyesPrize ID (_id)

No output schema declared.

No examples provided.

crewhu_prizes_history_list ~122

List prize redemption history

NameTypeReqDescription
limitnumber–Results per page (default: 20, API max: 100)
prize_idstring–Filter by specific prize ID
sincestring–Return redemptions updated since this date (ISO string)
statusstring–Filter by redemption status (exact match; status values are account-specific)
stepnumber–Page number, 1-based (default: 1)
user_idstring–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)

NameTypeReqDescription
available_onlyboolean–Show only active prizes (default: true)
limitnumber–Results per page (default: 50, API max: 100)
stepnumber–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)

NameTypeReqDescription
limitnumber–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

NameTypeReqDescription
limitnumber–Maximum number of results (default: 20, max: 100)
user_idstringyesUser 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

NameTypeReqDescription
limitnumber–Maximum number of results (default: 20, max: 100)
sincestring–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

NameTypeReqDescription
idstringyesSurvey ID (_id)

No output schema declared.

No examples provided.

crewhu_surveys_list ~157

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

NameTypeReqDescription
include_inactiveboolean–Include inactive/deleted surveys (default: false, meaning only active)
limitnumber–Results per page (default: 50, API max: 100)
sentimentstring–Filter by rating sentiment (positive = rating 5, neutral = 0, negative = -5). Filtered client-side within the fetched page.
sincestring–Return surveys updated since this date (ISO string, e.g., "2026-01-01T00:00:00Z")
stepnumber–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

NameTypeReqDescription
limitnumber–Maximum number of results (default: 20, max: 100)
sincestring–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).

NameTypeReqDescription
limitnumber–Surveys to fetch and search within (default: 100, API max: 100)
querystringyesSearch query text

No output schema declared.

No examples provided.

crewhu_users_get ~29

Get a specific user by ID

NameTypeReqDescription
idstringyesUser ID (_id)

No output schema declared.

No examples provided.

crewhu_users_list ~93

List employees/users with optional filtering and pagination

NameTypeReqDescription
departmentstring–Filter by department name (exact match)
include_inactiveboolean–Include inactive users (default: false, meaning only active)
limitnumber–Results per page (default: 50, API max: 100)
stepnumber–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)

NameTypeReqDescription
limitnumber–Users to fetch and search within (default: 100, API max: 100)
querystringyesSearch query (name, employee ID, department, position, or location)

No output schema declared.

No examples provided.

Install

How do I install the Crewhu MCP server?

Crewhu runs locally as a container image, launched with docker run --rm -i -e CREWHU_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/crewhu-mcp:v2.0.3. 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-technology/crewhu-mcp:v2.0.3

# add to Claude Code
claude mcp add wyre-technology-crewhu-mcp -- docker run --rm -i -e CREWHU_API_TOKEN -e MCP_TRANSPORT -e AUTH_MODE -e LOG_LEVEL ghcr.io/wyre-technology/crewhu-mcp:v2.0.3

This image reads CREWHU_API_TOKEN, MCP_TRANSPORT, AUTH_MODE and LOG_LEVEL. Set them in your client's env block for this server; docker run -e passes each one through to the container.

Common questions

What is the Crewhu MCP server?

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

Is the Crewhu MCP server safe to use?

Crewhu scores 48 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 16 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 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.