Customer Thermometer
OCI · GHCR.IO/WYRE-AI/CUSTOMER-THERMOMETER-MCP:V1.0.3 · SCANNED SEP 20
MCP server for Customer Thermometer's customer feedback / NPS survey API.
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 & Transparency32
- 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
- License check failed: the license (NOASSERTION) isn't a recognized OSI-approved license. See how to fix → Fail
- Actively maintained (last published 0 days ago).Pass
- Disclosure check failed: no security disclosure policy was found in the source repository. See how to fix → Fail
Schema Quality & AI Usability78
- AI-judged instruction clarity (excellent).Pass
- Tool/resource definitions use about 814 tokens (~81/item across 10 items; 10 tools + 0 resources), lean.Pass
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management0
- Stability not yet verified: not enough scan history yet (needs a 30-day window).Unverified
Tool Coverage94
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 81% of tool parameters carry a description.Partial
Tool Safety75
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- 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. See how to fix → Fail
- An AI judge read all 10 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: 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.
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.
oci · ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3
claude mcp add wyre-ai-customer-thermometer-mcp -- docker run --rm -i ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3
{
"mcpServers": {
"wyre-ai-customer-thermometer-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
]
}
}
} {
"servers": {
"wyre-ai-customer-thermometer-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
]
}
}
} codex mcp add wyre-ai-customer-thermometer-mcp -- docker run --rm -i ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3
{
"$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
}
}
} mcp_servers:
wyre-ai-customer-thermometer-mcp:
command: "docker"
args: ["run", "--rm", "-i", "ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"] {
"McpServers": {
"wyre-ai-customer-thermometer-mcp": {
"Transport": "stdio",
"Command": "docker",
"Arguments": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
]
}
}
} {
"mcpServers": {
"wyre-ai-customer-thermometer-mcp": {
"command": "docker",
"args": [
"run",
"--rm",
"-i",
"ghcr.io/wyre-ai/customer-thermometer-mcp:v1.0.3"
]
}
}
} 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 36
First indexed and scored.
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/customer-thermometer-mcp:v1.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 →
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 →
customerthermometer_add_recipient_to_list ~77
Add a recipient to a Customer Thermometer recipient list.
| Name | Type | Req | Description |
|---|---|---|---|
| companyName | string | – | – |
| emailAddress | string | yes | Recipient email address. |
| firstName | string | – | – |
| lastName | string | – | – |
| listId | string | yes | ID of the recipient list to add to. |
No output schema declared.
No examples provided.
customerthermometer_get_blast_results ~144
Get raw survey responses received, optionally filtered by temperature (1=gold,2=green,3=yellow,4=red), blast, or date range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
customerthermometer_get_comments ~129
Get free-text comments left with survey responses, optionally filtered by temperature, blast, or date range.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
customerthermometer_get_credits ~26
Get the number of remaining Thermometer send credits on the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
customerthermometer_get_happiness_value ~103
Get the Happiness Factor (as a percentage) for the account or a filtered set of responses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
customerthermometer_get_nps_value ~106
Get the Net Promoter Score (positive or negative integer) for the account or a filtered set of responses.
| Name | Type | Req | Description |
|---|---|---|---|
| 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. |
No output schema declared.
No examples provided.
customerthermometer_get_recipient_lists ~30
List all recipient lists (names and IDs) on the Customer Thermometer account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
customerthermometer_get_thermometers ~34
List all Customer Thermometer survey templates (Thermometer names and IDs) on the account.
Input schema present but exposes no named parameters.
No output schema declared.
No examples provided.
customerthermometer_send_email ~110
Send a single Email Thermometer survey to one recipient.
| Name | Type | Req | Description |
|---|---|---|---|
| blastID | string | – | Optional blast ID to group this send under. |
| companyName | string | – | – |
| emailAddress | string | yes | Recipient email address. |
| firstName | string | – | – |
| lastName | string | – | – |
| listID | string | yes | ID of the recipient list the recipient belongs to. |
| thermometerID | string | yes | ID of the Thermometer (survey template) to send. |
No output schema declared.
No examples provided.
customerthermometer_unsubscribe_recipient ~55
Add an email address to the account's Customer Thermometer unsubscribe list.
| Name | Type | Req | Description |
|---|---|---|---|
| emailAddress | string | yes | Email address to unsubscribe. |
| notify | boolean | – | Whether to notify the account of the unsubscribe. |
No output schema declared.
No examples provided.
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 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 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.