# io.github.wyre-technology/crewhu-mcp

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

- **Type:** MCP server
- **Trust:** 60/100 (B), scored on the content rubric
- **Verification:** community-indexed — nobody has claimed this listing
- **Version:** 2.0.3
- **Author:** io.github.wyre-technology
- **License:** Unknown
- **Source:** https://github.com/wyre-technology/crewhu-mcp

## Trust

60/100 (B), scored on the content rubric
- Publisher verified: no
- Install scripts: nothing suspicious found
- Prompt-injection scan: clean
- Obfuscation scan: clean
- Evidence age: 113 days — stale; the grade is a claim about the present made from dated evidence

## Security scan

- **Status:** clean
- **Scanned:** 2026-06-14T11:35:14.557Z
- **Version scanned:** HEAD
- **CVEs:** no coverage — this entry has no package coordinates to query OSV against, so "no known CVEs" is NOT asserted for it.

## Tools

18 declared. Statically extracted from the shipped source — a floor on the surface, not a census.
- `crewhu_badges_list`
- `crewhu_badges_get`
- `crewhu_badges_history_list`
- `crewhu_badges_user_recognition`
- `crewhu_badges_update_contest`
- `crewhu_prizes_list`
- `crewhu_prizes_get`
- `crewhu_prizes_history_list`
- `crewhu_prizes_user_redemptions`
- `crewhu_prizes_pending_redemptions`
- `crewhu_surveys_list`
- `crewhu_surveys_get`
- `crewhu_surveys_search`
- `crewhu_surveys_detractors`
- `crewhu_surveys_promoters`
- `crewhu_users_list`
- `crewhu_users_get`
- `crewhu_users_search`

## Install

This entry has no npm package and no hosted endpoint, so there is nothing for an MCP client to launch or connect to. It is indexed as source only.

## Blast radius

Contained to moderate — no credential declaration found, from the publisher, the upstream registry, or the README. Known so far: read-only tool surface.
- Floor 3, ceiling 33 (tier: unknown)
- `unknown` means the floor and ceiling land in different bands — not measured enough to name one. It does not mean low.
- This is impact, not likelihood. A high radius is not a defect: a filesystem server is supposed to write files. It is never part of the trust score.

## Machine-readable views of this entry

- Signed JSON: https://forgeregistry.com/api/v1/packages/io.github.wyre-technology%2Fcrewhu-mcp
- Install plan: https://forgeregistry.com/api/v1/packages/io.github.wyre-technology%2Fcrewhu-mcp/install-plan
- Alternatives: https://forgeregistry.com/api/v1/alternatives/io.github.wyre-technology%2Fcrewhu-mcp
- HTML page: https://forgeregistry.com/registry/io.github.wyre-technology%2Fcrewhu-mcp
- MCP: POST https://forgeregistry.com/api/mcp → `forge_get_package` / `forge_install_plan`

## About this document

Generated by Forge (https://forgeregistry.com) — a compact rendering of the same record served, signed, at the JSON URL above. Trust and scan facts are the registry's own measurements; anything Forge did not measure is named as unmeasured rather than omitted.