MCP HeartbeatTHE MCP OBSERVATORY
Public workspace

Explore

Evidence for your next connection.

Independent measurements of remote MCP servers. Every observation has a timestamp.

Read-only probes

MCP server · Communication & messaging

Signal by StackEnhance

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

Checks passed
15 / 22

0 failed · 7 not measured

Median response
678 ms

Median of successful probes over 7 days

30-day uptime
Not measured

Share of countable probes over 30 days, including daily rollups. Auth challenges are excluded.

Discovered tools
4

Tool definitions returned by this server

Independent monitoring

Health & checks

Status history

Responded

The server completed its last measured handshake. This is an observation, not a guarantee.

Last checked
Check summary by test group
Test areaPassedFailedUnmeasured
ConnectionCan a client connect and discover tools?
500
Reliability & speedDoes it respond consistently and quickly?
103
Access & authenticationWhat is required to use this server?
102
Tool qualityAre the tool definitions usable by an agent?
400
Publisher identityCan the publisher be traced to its source?
402

Unmeasured means there is not enough evidence to decide. How these checks work

Inspect individual checks 22 recorded

Core

  • Pass
    Reachable

    Latest probe returned HTTP 200 in 191 ms.

  • Pass
    Valid handshake

    protocolVersion 2025-11-25, serverInfo.name signal-by-stackenhance.

  • Pass
    Lists tools

    tools/list returned 4 tools.

  • Pass
    Current protocol

    Negotiated 2025-11-25. The bar is 2025-06-18 or newer.

  • Pass
    HTTPS

    The endpoint URL is https.

Performance

  • Not measured
    Fast (p50)

    Median latency 678 ms over 2 samples in 7 days. The bar is 1000 ms. Need at least 5 samples.

  • Not measured
    Consistent (p95)

    95th percentile 1116 ms over 2 samples in 7 days. The bar is 3000 ms. Need at least 20 samples.

  • Not measured
    Reliable (uptime)

    2 of 2 attempts returned a tool list in 30 days (100%). The bar is 99%. Need at least 30 samples.

  • Pass
    Stable tool list

    No tool was removed and no required parameter was added in the last 30 days.

Access

  • Pass
    Open access

    tools/list succeeded with no credential, and the record declares none.

  • Not measured
    Standard auth

    Auth is not required, so the OAuth metadata check does not apply.

  • Not measured
    Free tier cited

    No publisher quote has been checked.

Tools

  • Pass
    Tools described

    Every tool description is at least 20 characters.

  • Pass
    Valid input schemas

    Every inputSchema is a JSON Schema object.

  • Pass
    Parameters documented

    13 of 13 parameters have a description (100%). The bar is 80%.

  • Pass
    Safety hints

    Every tool sets readOnlyHint or destructiveHint.

Publisher

  • Pass
    Verified namespace

    Listed in the Official MCP Registry.

  • Pass
    Website matches publisher

    The website host matches the reverse-domain namespace.

  • Pass
    Source repo linked

    A repository URL is on file.

  • Not measured
    Repo owner matches

    This namespace is not an io.github login, so the owner comparison does not apply.

  • Pass
    Recently updated

    Updated 2026-11-08T15:17:13.358347Z, within 180 days.

  • Not measured
    Open-source licence

    The GitHub licence lookup has not returned an OSI result yet.

Start using Signal by StackEnhance

Connect to this server

Choose your client, copy the configuration, then enable the server in your client’s MCP settings.

Run this command in your terminal, then restart Claude Code.

Claude Code

claude mcp add --transport http signal-by-stackenhance https://mcp.stackenhance.com/mcp

Capabilities

Tools 4

compare_brands

Compare 2 to 5 ecommerce brands side by side in ONE call, as observed by StackEnhance Signal: current frequency (average marketing emails per week, last 90 days), emails observed in the last 6 months, the date Signal first observed each brand, the latest campaign date, and each brand's rank in its market when it has one, ordered by frequency. Use this instead of calling get_brand_summary repeatedly when the user names a set of brands: "Compare Mio, IKEA and Westwing", "Who emails more, Boozt or Zalando?", "How does Newport compare with its competitors?". Pass the brand names as the user wrote them. Give `market` (SE, NO, DK, FI, DE or a country name) when the brands are in one country, which is the usual case; a brand tracked in several countries without a market is listed as unavailable with the markets to choose from, never guessed. Optionally give `from` and `to` (YYYY-MM-DD, starting within the last six months) to also count each brand's sends in that period. More than 5 brands: call again with the rest. To discover competitors first, use find_brands. Returns aggregates only: no campaign list, subject lines, offers or creative analysis. There is no open, click or revenue data. Cite each brand's details_url as the source.

Discovered
find_brands

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 only; `market` is a country, never a topic. Brands with too little observed data are left out of rankings. To then compare some of the brands (or brands the user named), call compare_brands with their names. Returns brand names, categories and emails per week only. Each brand has a details_url to cite.

Discovered
get_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. To compare several brands over the same period, use compare_brands with from and to. 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.

Discovered
get_brand_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), the date of the latest observed campaign and, for brands Signal has followed 28+ days in SE, NO, DK, FI or DE, its rank in that market by frequency. 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. For two or more named brands use compare_brands instead of calling this once per brand. Returns aggregates only — no campaign list, subject lines, offers or creative analysis. Cite each result's details_url as the source.

Discovered

Recent measurements

Probe history

View status
Latest stored probes. Raw probe rows are kept for 14 days.
CheckedResultResponseTools
Connected191 ms4
Connected1165 ms4