_ registry / mcp http-sse · checked 2h ago

newsletter-commerce-intelligence

https://newsletter-commerce-mcp.sincetoday.workers.dev

Registry code: 6a77668c4e0f67d2

api record

Extracts product mentions, scores sponsors, and tracks affiliate trends from newsletters.

from a public catalogue that lists it, not from the operator

endpoint
https://newsletter-commerce-mcp.sincetoday.workers.dev/mcp
protocol
http-sse ·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 newsletter-commerce-intelligence live?
Yes — it answered the hub's last check (checked 2h ago). It answered 100% of checks over the last 30 days.
Is newsletter-commerce-intelligence free to use?
Not measured yet.
What tools does newsletter-commerce-intelligence have?
4 tools: analyze_newsletter_sponsors, generate_newsletter_products_section, extract_newsletter_products, track_product_trends.
Is newsletter-commerce-intelligence 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 99.6%· all time 99.6%

latency
389ms

last good check

priced tools
0

of 4 tools

_ answered our checks, 90 days 278 checks · signed record
  • degraded → live
  • degraded → live
  • live → degraded· timeout after 20000ms
  • unknown → live
_ what it is for
topic
productivity & business marketing & seo
used for
  • extract products from a newsletter
  • estimate newsletter sponsor value
  • track product trends across newsletters
  • format a newsletter products section
takes → gives
text, web pages → data, text
tools
4 reads
_ 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

_ what it can do 4 tools
4 never probed 0 of 4 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.

  • analyze_newsletter_sponsors reads unknown never probed

    Identify sponsored sections in a newsletter and estimate advertising value: CPM, read-through rate, and sponsor-reader fit score. Returns each sponsor's name, placement type (dedicated section, inline, footer), estimated CPM, and audience fit score. Use for newsletter advertising intelligence, sponsor acquisition research, and ad placement optimization. Reuses cached extraction when newsletter_id matches a prior extract_newsletter_products call.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "content"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional API key for paid access beyond the free tier"
    },
    "content": {
      "type": "string",
      "maxLength": 200000,
      "minLength": 1,
      "description": "Newsletter content as HTML or plain text"
    },
    "newsletter_id": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional newsletter issue identifier — uses cached extraction if available"
    }
  },
  "additionalProperties": false
}
    arguments 26 lines
  • generate_newsletter_products_section reads unknown never probed

    Format extracted newsletter products into a 'Products in This Edition' footer section. Returns ready-to-paste markdown or HTML, grouped by endorsement strength (strong/endorsed/mentioned), with affiliate links where resolved. Use after extract_newsletter_products — pass newsletter_id to use cached extraction, or pass products[] directly. Handles null affiliate_link gracefully (plain name, no broken link). Format: markdown (default) for newsletter editors and Ghost/Substack copy-paste; html for custom templates. Style: full (default) groups by endorsement with context quotes and a CTA footer; minimal produces a compact product list. Example: call extract_newsletter_products on 'swipe-file-issue-47', then call generate_newsletter_products_section with newsletter_id='swipe-file-issue-47' to get a formatted footer with Notion AI, Beehiiv, and Linear grouped by strength.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "properties": {
    "style": {
      "enum": [
        "minimal",
        "full"
      ],
      "type": "string",
      "description": "minimal = name + category list; full (default) = grouped by endorsement strength with context quotes and affiliate CTA"
    },
    "format": {
      "enum": [
        "markdown",
        "html"
      ],
      "type": "string",
      "description": "Output format: markdown (default) or html"
    },
    "api_key": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional API key for paid access beyond the free tier"
    },
    "products": {
      "type": "array",
      "items": {
        "type": "object",
        "required": [
          "name",
          "category",
          "recommendation_strength",
          "confidence"
        ],
        "properties": {
          "name": {
            "type": "string"
          },
          "category": {
            "type": "string"
          },
          "confidence": {
            "type": "number"
          },
          "is_sponsored": {
            "type": "boolean"
          },
          "affiliate_link": {
            "type": [
              "string",
              "null"
            ]
          },
          "mention_context": {
            "type": "string"
          },
          "recommendation_strength": {
            "type": "string"
          }
        },
        "additionalProperties": false
      },
      "description": "Raw products array from extract_newsletter_products output. Use instead of newsletter_id when passing data directly."
    },
    "newsletter_id": {
      "type": "string",
      "maxLength": 200,
      "description": "Newsletter issue ID from a prior extract_newsletter_products call — uses cached extraction. Example: 'swipe-file-issue-47'"
    }
  },
  "additionalProperties": false
}
    arguments 73 lines
  • extract_newsletter_products reads unknown never probed

    Extract affiliate links, product recommendations, and sponsored mentions from a newsletter issue. Supports HTML from Substack, Ghost, and Beehiiv plus plain text. Returns product name, category (saas, supplement, book, course, physical_goods), affiliate link URL, recommendation strength, and sponsor flag. Use for newsletter monetization analysis, affiliate program auditing, and cross-issue product tracking. Caches results by newsletter_id.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "content"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional API key for paid access beyond the free tier"
    },
    "content": {
      "type": "string",
      "maxLength": 200000,
      "minLength": 1,
      "description": "Newsletter content as HTML or plain text"
    },
    "newsletter_id": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional newsletter issue identifier for caching and trend tracking"
    },
    "category_filter": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 50
      },
      "maxItems": 20,
      "description": "Optional list of categories to include: saas, physical_goods, course, supplement, book, service, media, other"
    },
    "include_aesthetic_tags": {
      "type": "boolean",
      "default": false,
      "description": "When true, includes aestheticTags (warmth/density/origin/tradition) per product. Adds ~20 tokens per product. Default: false."
    }
  },
  "additionalProperties": false
}
    arguments 40 lines
  • track_product_trends reads unknown never probed

    Compare affiliate product mentions and brand frequency across multiple newsletter issues to detect rising, stable, and declining trends. Returns trend velocity, mention count per issue, and category breakdown. Use for newsletter affiliate marketing optimization, editorial product tracking, and sponsor category trends. Requires prior extract_newsletter_products calls for each newsletter_id.

    mcp-tool

    {
  "type": "object",
  "$schema": "http://json-schema.org/draft-07/schema#",
  "required": [
    "newsletter_ids"
  ],
  "properties": {
    "api_key": {
      "type": "string",
      "maxLength": 200,
      "description": "Optional API key for paid access beyond the free tier"
    },
    "newsletter_ids": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 200
      },
      "maxItems": 20,
      "minItems": 1,
      "description": "List of newsletter issue IDs to analyze. Each must have been previously extracted via extract_newsletter_products."
    },
    "category_filter": {
      "type": "array",
      "items": {
        "type": "string",
        "maxLength": 50
      },
      "maxItems": 20,
      "description": "Optional category filter to narrow trend analysis"
    }
  },
  "additionalProperties": false
}
    arguments 34 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 6a77668c4e0f67d2.

Every step, filled in for this listing: https://brick.blue/api/v1/agents/6a77668c4e0f67d2/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/6a77668c4e0f67d2/badge.svg)](https://brick.blue/agent/6a77668c4e0f67d2?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
80%

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.