# Customer Thermometer (oci · ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3)

MCP server for Customer Thermometer's customer feedback / NPS survey API.

- Trust score: 36/100 (low)
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-09-21

## Components

- oci · `ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3`: 36/100 (this document), [markdown](https://verifymcp.io/servers/wyre-ai-customer-thermometer-mcp/ghcr-io-wyre-ai-customer-thermometer-mcp-v1-0-3.md), [page](https://verifymcp.io/servers/wyre-ai-customer-thermometer-mcp/ghcr-io-wyre-ai-customer-thermometer-mcp-v1-0-3)

## Channel facts

- Registry: `oci`
- Package: `ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3`
- 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-21.

- **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**: 32/100
  - Source repository is publicly reachable at the declared URL.
  - Provenance check failed: no build-provenance attestation is published.
  - License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license.
  - Actively maintained (last published 0 days ago).
  - Disclosure check failed: no security disclosure policy was found in the source repository.
- **Schema Quality & AI Usability**: 78/100
  - AI-judged instruction clarity (excellent).
  - Tool/resource definitions use about 814 tokens (~81/item across 10 items; 10 tools + 0 resources), lean.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 0/100
  - Stability not yet verified: not enough scan history yet (needs a 30-day window).
- **Tool Coverage**: 94/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 81% of tool parameters carry a description.
- **Tool Safety**: 75/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - 0 of 1 tool(s) whose name or description implies an irreversible operation declare an MCP destructiveHint annotation; "customerthermometer_send_email" implies "send" and declares no destructiveHint at all, which the MCP spec reads as destructive by default.
  - An AI judge read all 10 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: 2 categories.** Categories scored 0 because we could not verify them: 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 Customer Thermometer MCP server?

Customer Thermometer runs locally as a container image, launched with docker run --rm -i ghcr.io/wyre-ai/customer-thermometer-mcp:v1.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.

### Claude

```bash
claude mcp add wyre-ai-customer-thermometer-mcp -- docker run --rm -i ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3
```

### Cursor

```json
{
  "mcpServers": {
    "wyre-ai-customer-thermometer-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
      ]
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "wyre-ai-customer-thermometer-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
      ]
    }
  }
}
```

### Codex

```bash
codex mcp add wyre-ai-customer-thermometer-mcp -- docker run --rm -i ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3
```

### opencode

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

### Hermes

```yaml
mcp_servers:
  wyre-ai-customer-thermometer-mcp:
    command: "docker"
    args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"]
```

### Netclaw

```json
{
  "McpServers": {
    "wyre-ai-customer-thermometer-mcp": {
      "Transport": "stdio",
      "Command": "docker",
      "Arguments": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
      ]
    }
  }
}
```

### Other

```json
{
  "mcpServers": {
    "wyre-ai-customer-thermometer-mcp": {
      "command": "docker",
      "args": [
        "run",
        "--rm",
        "-i",
        "ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
      ]
    }
  }
}
```

## 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 36)

First indexed and scored.

## MCP tools (10)

### `customerthermometer_get_thermometers` (~34 tokens)

List all Customer Thermometer survey templates (Thermometer names and IDs) on the account.

### `customerthermometer_get_recipient_lists` (~30 tokens)

List all recipient lists (names and IDs) on the Customer Thermometer account.

### `customerthermometer_add_recipient_to_list` (~77 tokens)

Add a recipient to a Customer Thermometer recipient list.

Input parameters:

- `companyName` (string)
- `emailAddress` (string, required): Recipient email address.
- `firstName` (string)
- `lastName` (string)
- `listId` (string, required): ID of the recipient list to add to.

### `customerthermometer_unsubscribe_recipient` (~55 tokens)

Add an email address to the account's Customer Thermometer unsubscribe list.

Input parameters:

- `emailAddress` (string, required): Email address to unsubscribe.
- `notify` (boolean): Whether to notify the account of the unsubscribe.

### `customerthermometer_send_email` (~110 tokens)

Send a single Email Thermometer survey to one recipient.

Input parameters:

- `blastID` (string): Optional blast ID to group this send under.
- `companyName` (string)
- `emailAddress` (string, required): Recipient email address.
- `firstName` (string)
- `lastName` (string)
- `listID` (string, required): ID of the recipient list the recipient belongs to.
- `thermometerID` (string, required): ID of the Thermometer (survey template) to send.

### `customerthermometer_get_credits` (~26 tokens)

Get the number of remaining Thermometer send credits on the account.

### `customerthermometer_get_nps_value` (~106 tokens)

Get the Net Promoter Score (positive or negative integer) for the account or a filtered set of responses.

Input parameters:

- `blastID` (string): Restrict to a single blast/send.
- `fromDate` (string): Start date, e.g. 2026-01-01.
- `limit` (number): Maximum number of results to return.
- `toDate` (string): End date, e.g. 2026-01-31.

### `customerthermometer_get_happiness_value` (~103 tokens)

Get the Happiness Factor (as a percentage) for the account or a filtered set of responses.

Input parameters:

- `blastID` (string): Restrict to a single blast/send.
- `fromDate` (string): Start date, e.g. 2026-01-01.
- `limit` (number): Maximum number of results to return.
- `toDate` (string): End date, e.g. 2026-01-31.

### `customerthermometer_get_blast_results` (~144 tokens)

Get raw survey responses received, optionally filtered by temperature (1=gold,2=green,3=yellow,4=red), blast, or date range.

Input parameters:

- `blastID` (string): Restrict to a single blast/send.
- `fromDate` (string): Start date, e.g. 2026-01-01.
- `limit` (number): Maximum number of results to return.
- `temperatureID` (number): 1=gold, 2=green, 3=yellow, 4=red.
- `toDate` (string): End date, e.g. 2026-01-31.

### `customerthermometer_get_comments` (~129 tokens)

Get free-text comments left with survey responses, optionally filtered by temperature, blast, or date range.

Input parameters:

- `blastID` (string): Restrict to a single blast/send.
- `fromDate` (string): Start date, e.g. 2026-01-01.
- `limit` (number): Maximum number of results to return.
- `temperatureID` (number): 1=gold, 2=green, 3=yellow, 4=red.
- `toDate` (string): End date, e.g. 2026-01-31.

## Diagnostics

Captured diagnostic sections: Provenance. The full working is on the page: https://verifymcp.io/servers/wyre-ai-customer-thermometer-mcp/ghcr-io-wyre-ai-customer-thermometer-mcp-v1-0-3#diagnostics

## Score history

- 2026-09-21: 36
- 2026-09-20: 36

## Common questions

### What is the Customer Thermometer MCP server?

Customer Thermometer is an MCP server listed in the public MCP registry as io.github.WYRE-AI/customer-thermometer-mcp. MCP server for Customer Thermometer's customer feedback / NPS survey API. This page covers its container image (ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3).

### Is the Customer Thermometer MCP server safe to use?

Customer Thermometer scores 36 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 Customer Thermometer MCP server expose?

Customer Thermometer exposes 10 tools: customerthermometer_get_thermometers, customerthermometer_get_recipient_lists, customerthermometer_add_recipient_to_list, customerthermometer_unsubscribe_recipient, customerthermometer_send_email, and 5 more. Their descriptions and schemas cost roughly 814 tokens of context every time the server is loaded.

### Is the Customer Thermometer MCP server still maintained?

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

Customer Thermometer declares the NOASSERTION licence, which is not on the OSI-approved list. Read the terms before using it at work, and note this covers the source only, not the cost of any service it calls.

## Links

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