# Signal by StackEnhance (remote · mcp.stackenhance.com)

How often 750+ e-commerce brands send marketing emails: counts, send dates, recent subject lines.

- Trust score: 84/100 (high trust)
- Change this week: +3
- Registry status: active
- Liveness: live
- Owner verified: no
- Last scored: 2026-11-05

## Components

- remote · `mcp.stackenhance.com`: 84/100 (this document), [markdown](https://verifymcp.io/servers/com-stackenhance-signal/mcp.md), [page](https://verifymcp.io/servers/com-stackenhance-signal/mcp)

## Channel facts

- Endpoint: `https://mcp.stackenhance.com/mcp`
- Transports: `streamable-http`
- Auth: `none`
- Version: `1.2.0`

## Trust breakdown

How this component scores in each security and reliability category. Every signal is checked automatically against the live server, 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-11-05.

- **Endpoint Security**: 83/100
  - The endpoint's TLS certificate is valid, in date, and uses a strong key.
  - No authorisation is required to call this server. Nothing on it is marked destructive, but we can't show that an anonymous caller can only read: full credit needs the server to list at least one tool and every tool to be verifiably read-only. We use a best-effort check of tool names and descriptions to tell read-only tools from tools that change things, so some genuinely read-only tools may not get full credit. Names that start with a read verb (get, list, read, search and similar) and accurate readOnlyHint annotations help. Meet that to earn full credit, or require authorisation.
  - HTTPS is enforced; there's no plaintext access path.
  - The HSTS (Strict-Transport-Security) header is present.
  - DNSSEC is configured correctly; the domain's records validate against the full chain to the root.
- **Transport & Reachability**: 100/100
  - Verified streamable-http transport via a live MCP handshake.
- **Schema Quality & AI Usability**: 64/100
  - AI-judged instruction clarity (excellent).
  - Context-footprint check failed: tool/resource definitions use about 1054 tokens (~351/item across 3 items; 3 tools + 0 resources), over budget; trim descriptions and params.
  - Usage-examples check failed: none of the tools include examples.
- **Stability & Change Management**: 80/100
  - Stability observed for 24 of 30 days with no destabilising changes; credit accrues until the full window elapses.
- **Tool Coverage**: 100/100
  - 100% of tools have a non-trivial description (not blank, and not just the tool's name).
  - 100% of tool parameters carry a description.
  - Structured output schemas are declared (100% of tools); any adoption earns full credit.
- **Tool Safety**: 100/100
  - No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.
  - We read all 3 captured tool definition(s), and no name or description among them implies an irreversible operation.
  - An AI judge read all 4 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.

## Install

### How do I install the Signal by StackEnhance MCP server?

Signal by StackEnhance is a hosted endpoint at https://mcp.stackenhance.com/mcp, so there is nothing to install locally. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.

### Claude

```bash
claude mcp add --transport http com-stackenhance-signal 'https://mcp.stackenhance.com/mcp'
```

### Cursor

```json
{
  "mcpServers": {
    "com-stackenhance-signal": {
      "url": "https://mcp.stackenhance.com/mcp"
    }
  }
}
```

### VS Code

```json
{
  "servers": {
    "com-stackenhance-signal": {
      "type": "http",
      "url": "https://mcp.stackenhance.com/mcp"
    }
  }
}
```

### Codex

```toml
[mcp_servers.com-stackenhance-signal]
url = "https://mcp.stackenhance.com/mcp"
```

### opencode

```json
{
  "$schema": "https://opencode.ai/config.json",
  "mcp": {
    "com-stackenhance-signal": {
      "type": "remote",
      "url": "https://mcp.stackenhance.com/mcp",
      "enabled": true
    }
  }
}
```

### OpenClaw

```bash
openclaw mcp add com-stackenhance-signal --url 'https://mcp.stackenhance.com/mcp' --transport streamable-http
```

### Hermes

```yaml
mcp_servers:
  com-stackenhance-signal:
    url: "https://mcp.stackenhance.com/mcp"
```

### Netclaw

```json
{
  "McpServers": {
    "com-stackenhance-signal": {
      "Transport": "http",
      "Url": "https://mcp.stackenhance.com/mcp"
    }
  }
}
```

### Vellum

```bash
assistant mcp add com-stackenhance-signal -t streamable-http -u 'https://mcp.stackenhance.com/mcp'
```

### Other

```json
{
  "mcpServers": {
    "com-stackenhance-signal": {
      "type": "http",
      "url": "https://mcp.stackenhance.com/mcp"
    }
  }
}
```

The mcpServers block is a cross-client convention. Remote transports vary, so check your client's docs.

## 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-11-04 (score 84, +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.

### 2026-11-02 (score 83, +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.

### 2026-10-31 (score 82, +1)

- [security] The server rewrote its instructions, which are the text every model session reads
- [security] Tool “get_brand_summary” rewrote its description, which is the text the model reads

### 2026-10-29 (score 81, +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.

### 2026-10-27 (score 80, +1)

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

### 2026-10-25 (score 79, +1)

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

### 2026-10-24 (score 78, 0)

- [security] Tool “get_brand_email_frequency” rewrote its description, which is the text the model reads

### 2026-10-23 (score 78, +1)

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

## MCP tools (3)

### `get_brand_email_frequency` (~431 tokens)

Brand email frequency

How many marketing emails a brand sent in a calendar period, and when, as observed by StackEnhance Signal (ecommerce brands, mostly in Sweden, Norway, Denmark, Finland and Germany). Use for questions like "How many emails did Newport send in August 2026?", "What did Newport send last week?" or "What has X sent recently?". Without a market, a brand tracked in several countries gets one result per market. Resolve relative dates yourself to YYYY-MM-DD: "last week" is the previous Monday–Sunday, "last month" the previous calendar month, "recently" the last 14 days. Dates are the brand's local calendar dates. The period must start within the last six months (older history is in a Signal account) and may span up to two years. Returns the count; for periods of up to 31 days also the date of each send; and at most two subject lines, only ones already shown on the brand's public StackEnhance page and sent in the period. Every listed send was captured in full; a send without a quoted subject is listed in sends_with_subject_in_signal because its subject is withheld by that limit, not missing. Counts are de-duplicated marketing sends (welcome, birthday and transactional emails excluded). There is no open, click or revenue data. Full campaigns, other subject lines, offers, products and creative analysis are not available through this tool. Cite each result's details_url as the source and as where the full campaigns are.

Input parameters:

- `brand` (string, required): Brand name as the user wrote it, e.g. "Newport" or "IKEA". A domain such as newport.se also works.
- `from` (string, required): First day of the period, YYYY-MM-DD.
- `market` (string): Country of one storefront as a two-letter code (SE, NO, DK, FI, DE) or its name ("Sweden"). Omit it to get every market the brand is tracked in.
- `to` (string, required): Last day of the period, inclusive, YYYY-MM-DD.

Output parameters:

- `results` (array)
- `unavailable` (array)

### `get_brand_summary` (~212 tokens)

Brand email summary

A brand's email-marketing profile as observed by StackEnhance Signal: market, category, the date Signal first observed it, marketing emails observed in the last 6 months, current frequency (average emails per week over the last 90 days) and the date of the latest observed campaign. Use for questions like "How often does Newport email customers?" or "Is IKEA still sending newsletters?". Without a market, a brand tracked in several countries gets one summary per market. Returns aggregates only — no campaign list, subject lines, offers or creative analysis. Cite each result's details_url as the source.

Input parameters:

- `brand` (string, required): Brand name as the user wrote it, e.g. "Newport" or "IKEA". A domain such as newport.se also works.
- `market` (string): Country of one storefront as a two-letter code (SE, NO, DK, FI, DE) or its name ("Sweden"). Omit it to get every market the brand is tracked in.

Output parameters:

- `results` (array)
- `unavailable` (array)

### `find_brands` (~216 tokens)

Find brands by email frequency

Ecommerce brands StackEnhance Signal tracks in one market, ranked by current email frequency (average marketing emails per week over the last 90 days), optionally within a category such as "Fashion & Apparel" or "Home & Interior". Use for questions like "Which brands email most frequently in Swedish ecommerce?" or to find a brand when the user names a kind of brand ("a Swedish fashion brand"). Rankings are available for SE, NO, DK, FI and DE. Brands with too little observed data are left out of rankings. Returns brand names, categories and emails per week only. Each brand has a details_url to cite.

Input parameters:

- `category` (string): Optional category, e.g. "Fashion & Apparel", "Home & Interior", "Beauty & Cosmetics", "Sports & Outdoor".
- `limit` (integer): How many brands to return (1-10, default 10).
- `market` (string, required): Country as a two-letter code (SE, NO, DK, FI or DE) or its name ("Sweden").

Output parameters:

- `brands` (array)
- `brands_tracked` (integer)
- `category` (string|null)
- `market` (string)
- `window_days` (integer)

## Diagnostics

Captured diagnostic sections: TLS, DNSSEC, Authorisation, Transports. The full working is on the page: https://verifymcp.io/servers/com-stackenhance-signal/mcp#diagnostics

## Score history

- 2026-11-05: 84
- 2026-11-04: 84
- 2026-11-03: 83
- 2026-11-02: 83
- 2026-11-01: 82
- 2026-10-31: 82
- 2026-10-30: 81
- 2026-10-29: 81
- 2026-10-28: 80
- 2026-10-27: 80
- 2026-10-26: 79
- 2026-10-25: 79
- 2026-10-24: 78
- 2026-10-23: 78
- 2026-10-22: 77
- 2026-10-21: 77
- 2026-10-20: 77
- 2026-10-19: 76
- 2026-10-18: 76
- 2026-10-17: 75
- 2026-10-16: 75
- 2026-10-15: 74
- 2026-10-14: 74
- 2026-10-13: 73
- 2026-10-12: 73

## Common questions

### What is the Signal by StackEnhance MCP server?

Signal by StackEnhance is an MCP server listed in the public MCP registry as com.stackenhance/signal. How often 750+ e-commerce brands send marketing emails: counts, send dates, recent subject lines. This page covers its hosted endpoint (https://mcp.stackenhance.com/mcp).

### Is the Signal by StackEnhance MCP server safe to use?

Signal by StackEnhance scores 84 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 Signal by StackEnhance MCP server expose?

Signal by StackEnhance exposes 3 tools: get_brand_email_frequency, get_brand_summary, find_brands. Their descriptions and schemas cost roughly 859 tokens of context every time the server is loaded.

### Does the Signal by StackEnhance MCP server require authentication?

No. We connected to Signal by StackEnhance without credentials and it answered, so anything it exposes is reachable by anyone who knows the address.

### Is the Signal by StackEnhance MCP server still maintained?

Signal by StackEnhance is still listed as active in the MCP registry. We last reached this channel on 5 November 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.

### What did VerifyMCP test on the Signal by StackEnhance MCP server?

VerifyMCP ran 13 checks on Signal by StackEnhance, covering TLS certificate, Authorization, HTTPS, HSTS header and 9 more. Supply Chain Security and Provenance & Transparency do not apply to a hosted endpoint, so they were not tested. The score does not measure everything, and the scoring documentation lists what it leaves out.

## Links

- Remote endpoint: https://mcp.stackenhance.com/mcp
- Repository: https://github.com/stackenhance/signal-mcp
- Website: https://stackenhance.com/signal
- Changelog RSS feed: https://verifymcp.io/servers/com-stackenhance-signal/mcp.xml
- Changelog JSON feed: https://verifymcp.io/servers/com-stackenhance-signal/mcp/changelog.json
- Trust report (JSON): https://verifymcp.io/servers/com-stackenhance-signal/mcp.json
- HTML version of this page: https://verifymcp.io/servers/com-stackenhance-signal/mcp