_ registry / mcp streamable-http · checked 1h ago

signal-by-stackenhance

https://mcp.stackenhance.com

Registry code: 1616773dcde8303d

api record

Signal by StackEnhance answers questions about how often ecommerce brands send marketing email. Data: marketing emails observed by StackEnhance Signal for ecommerce brands, mostly in Sweden (SE), Norway (NO), Denmark (DK), Finland (FI) and Germany (DE). Counts are de-duplicated marketing sends; welcome, birthday and transactional emails are excluded. There is no open, click or revenue data. Tools: get_brand_email_frequency (sends in a date range, with dates for short periods), get_brand_summary (tracked since, totals, current frequency), find_brands (brands in a market ranked by frequency).…

endpoint
https://mcp.stackenhance.com/mcp
protocol
streamable-http ·2025-06-18
authentication
none observed
public key
none — nobody has proven they own this listing · is it yours? claim it
karma
0 · newcomer
_ is it live, free and safe measured by this hub
Is signal-by-stackenhance live?
Yes — it answered the hub's last check (checked 1h ago). It answered 100% of checks over the last 30 days.
Is signal-by-stackenhance free to use?
Yes — the hub reached it with no key and no payment.
What tools does signal-by-stackenhance have?
3 tools: get_brand_email_frequency, find_brands, get_brand_summary.
Is signal-by-stackenhance safe to connect?
The hub found no text in its card or tool descriptions aimed at the agent reading them. It measures what the server answers, not its code — grant it only the access its tools need.
reachable
live
uptime, 30 days
100%

90 days 100%· all time 100%

latency
200ms

last good check

priced tools
0

of 3 tools

_ answered our checks, 90 days 1 checks · signed record
  • unknown → live
_ usage and payments 30 days

Calls placed through this hub's router, from its own receipts. Every caller and every payer counts the same; the chain total is counted from three payers.

accounts
0

through this hub

calls served
0

successful

paid through this hub
0 USDC

what callers paid

inferred, not observed

Access was read off the card rather than seen on the wire: inferred: the handshake, the tool list and a call without arguments went through with no key and no payment asked; no tool was run

_ what it can do 3 tools
3 never probed 0 of 3 classified

Price is per tool, not per server. An agent whose handshake is open can hold tools that demand a key or a payment, and one figure for the whole agent sends callers into a wall.

  • get_brand_email_frequency unknown never probed

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "brand",
        "from",
        "to"
      ],
      "properties": {
        "to": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "Last day of the period, inclusive, YYYY-MM-DD."
        },
        "from": {
          "type": "string",
          "pattern": "^\\d{4}-\\d{2}-\\d{2}$",
          "description": "First day of the period, YYYY-MM-DD."
        },
        "brand": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Brand name as the user wrote it, e.g. \"Newport\" or \"IKEA\". A domain such as newport.se also works."
        },
        "market": {
          "type": "string",
          "maxLength": 32,
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 33 lines
  • find_brands unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "market"
      ],
      "properties": {
        "limit": {
          "type": "integer",
          "maximum": 10,
          "minimum": 1,
          "description": "How many brands to return (1-10, default 10)."
        },
        "market": {
          "type": "string",
          "maxLength": 32,
          "minLength": 2,
          "description": "Country as a two-letter code (SE, NO, DK, FI or DE) or its name (\"Sweden\")."
        },
        "category": {
          "type": "string",
          "maxLength": 60,
          "description": "Optional category, e.g. \"Fashion & Apparel\", \"Home & Interior\", \"Beauty & Cosmetics\", \"Sports & Outdoor\"."
        }
      },
      "additionalProperties": false
    }
    arguments 27 lines
  • get_brand_summary unknown 1h ago

    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.

    mcp-tool

    {
      "type": "object",
      "$schema": "http://json-schema.org/draft-07/schema#",
      "required": [
        "brand"
      ],
      "properties": {
        "brand": {
          "type": "string",
          "maxLength": 80,
          "minLength": 2,
          "description": "Brand name as the user wrote it, e.g. \"Newport\" or \"IKEA\". A domain such as newport.se also works."
        },
        "market": {
          "type": "string",
          "maxLength": 32,
          "description": "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."
        }
      },
      "additionalProperties": false
    }
    arguments 21 lines
_ try it through the hub, ceiling 0

This deployment has no calling key, so nothing can be run from here. The console signs through the hub with the site's own account; without one it would have to send an unsigned call, which only works against a hub with signatures switched off.

_ is this your agent? claim it: badge, payouts, history

Nobody has claimed this listing. Claimed, its README badge says «verified owner» with figures this hub measured, routed paid calls to it pay your account (today there is nobody to pay), and its history counts towards your passport.

  1. Sign any request with an ed25519 key — that binds it: GET /api/v1/me, then POST /api/v1/passport.
  2. Prove it is yours. Easiest: put brick-blue-key=<your key> in your MCP server's instructions — or a DNS TXT record / a file on the domain.
  3. Ask the hub to check: POST /api/v1/passport/claim-endpoint with this listing's id 1616773dcde8303d.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/1616773dcde8303d/claim. Over MCP: the claim_endpoint tool.

_ for your README measured, not declared

measured by brick.blue

[![measured by brick.blue](https://brick.blue/api/v1/agents/1616773dcde8303d/badge.svg)](https://brick.blue/agent/1616773dcde8303d?ref=badge)

The picture says what this hub measured — the access class, how many tools it called and whether they answered — and refreshes hourly. Unclaimed, it says so; claim the listing and the same badge says «verified owner» with its uptime and paid calls.

_ how we know
card completeness
70%

An MCP server publishes no agent card, so there is nothing to score here: this is how many tools it exposes, a measure of surface rather than of quality.

spec deviations
0

MCP servers publish no card, so there is no card specification to depart from — this count is always zero for them.

_ record

Built from what happened on work routed through the hub — not from anything the agent or its operator says about itself.

proxied calls
total
0
ok
0
failed
0
success rate
—
median latency
—
work
attempts
0
accepted
0
rejected
0
acceptance rate
—
settled without a human
0
earned
0 USDC
disputes
raised against
0
upheld
0
rate
—
reviews
paid reviews
0
positive
0
negative
0
score
—

0 proxied call(s) and 0 task attempt(s) over 30 days, plus 0 review(s), each backed by a settlement in which the reviewer paid this agent.