Signal by StackEnhance
by gimarcus · remote · no sign-in to list tools · v1.2.1 · published by GitHub user gimarcus
Moved to com.stackenhance/signal: the same server, now published under the StackEnhance domain.
3 tools: 3 only read.
Scanned Oct 21, 2026
- Deletes or cancels0Claude Code: deny
- Can't be undone0Claude Code: ask
- Changes things0Claude Code: ask
- Only reads3Claude Code: allow: see these tools
No check matched anything in the tool definitions. No finding is not a safety guarantee. How the checks work.
claude mcp add --transport http signal https://stackenhance.com/api/mcpTools
Open a tool for its reasons and full description. Descriptions are the publisher's own words, shown as they are.
3 tools
Only reads 3Claude Code: allow
find_brandsEcommerce 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…No findings
Why it is in this group
- The name "find_brands" says "find": a word for reading.
Description, as the server wrote it 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.
Annotations the server declares
- title: Find brands by email frequency
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_brand_email_frequencyHow 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)…No findings
Why it is in this group
- The name "get_brand_email_frequency" says "get": a word for reading.
Description, as the server wrote it 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 and a period 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.
Annotations the server declares
- title: Brand email frequency
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
get_brand_summaryA brand's email-marketing profile as observed by StackEnhance Signal: market, category, the date Signal first observed it, total marketing emails observed, current frequency (avera…No findings
Why it is in this group
- The name "get_brand_summary" says "get": a word for reading.
Description, as the server wrote it A brand's email-marketing profile as observed by StackEnhance Signal: market, category, the date Signal first observed it, total marketing emails observed, 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.
Annotations the server declares
- title: Brand email summary
- readOnlyHint: true
- destructiveHint: false
- idempotentHint: true
- openWorldHint: false
This is not a safety rating, and no finding is not a safety guarantee. The groups and findings come from fixed checks of the tool definitions the server returned on the date shown, not from its code or what it does when called. How the checks work.
Install
Pinned to version 1.2.1. Values in angle brackets are yours to fill in.
claude mcp add --transport http signal https://stackenhance.com/api/mcpRun in a terminal.
Claude Code permissions
Allow the reads, ask before a change, deny the deletes. Paste into .claude/settings.json.
{
"permissions": {
"allow": [
"mcp__signal__get_brand_email_frequency",
"mcp__signal__get_brand_summary",
"mcp__signal__find_brands"
],
"ask": [],
"deny": []
}
}Tools that only read are allowed, tools that change things ask first, tools that delete or cancel are denied. It assumes the server is installed as signal. Review it before you use it.
