# Exploding Topics (Exploding Topics Pro): MCP server status, API access gate and what it does > Surfaces topics, products, and search queries showing accelerating growth in interest before they go... No MCP found, Paid, self-serve. Checked 2026-09-02. *Markdown twin of the HTML page at the same path. Same content, no navigation, no styling, no scripts. Links below point at other twins. Site map for machines: [llms.txt](../llms.txt). The whole dataset: [directory.json](../data/directory.json).* *Maintained by Andrew McGuire (https://andrewcmcguire.com), who also publishes https://gtmsignals.co and https://justsaid.ai.* --- [Directory](../index.md) / [Community & Dark Social](../categories/community-dark-social.md) / Exploding Topics (Exploding Topics Pro) # Exploding Topics (Exploding Topics Pro) [No MCP found](../mcp/none-found.md) [Paid, self-serve](../gates/paid.md) [Community & Dark Social](../categories/community-dark-social.md) RESEARCHED Checked 2026-09-02 > **RESEARCHED** Facts from public sources with URLs. No usage claims. Nobody has run this tool. The other tier is BENCH-TESTED, which means Andrew personally ran the tool on a stated date and cannot be bought at any price. Across the whole directory that count is 1. Vendor: [https://explodingtopics.com](https://explodingtopics.com) · entry id 15-exploding-topics · source 15-community-dark-social.md line 216 **What it does** Surfaces topics, products, and search queries showing accelerating growth in interest before they go mainstream, by tracking search/social/web signal velocity across a large keyword database. **AI features, separated from automation with an AI label on it** Vendor markets a proprietary trend-detection algorithm for identifying "exploding" (rapidly accelerating) topics; methodology is not publicly disclosed in detail, so treat the "AI-powered" framing as an unverified vendor claim rather than a confirmed ML architecture. **RevOps role** Early trend/topic-discovery layer for content and product-marketing ideation - more upstream/strategic than a real-time mention-monitoring tool, but relevant to GTM engineers building topic-based outbound triggers. **MCP server** - **Status bucket**: No MCP found - **Auth**: n/a - **Parsed URLs**: 0 found in the mcp_url field No server was found at the time of the check. That is a statement about the search, not a promise that none exists. The status was established on 2026-09-02. mcp_status, verbatim from the file: none-found mcp_url, verbatim from the file: none **Command line** No CLI found by the 2026-09-27 harvest across vendor docs, npm, PyPI, Homebrew and GitHub. That is a probe result, not proof of absence. **Access gate** - **Gate bucket**: Paid, self-serve - **Can a solo operator reach it**: Yes, by paying, no sales call api_gate, verbatim from the file: paid (the API is an add-on to the Business plan which starts at $249/mo, with request tiers at $1,000/mo for 1,000 requests, $2,000/mo for 5,000 and $4,000/mo for 25,000, so the real solo-operator floor is about $1,249/mo; commercial or product-embedded use needs custom pricing) **API documentation** No documentation URL recorded. 727 of 1252 entries are in the same position. Blank is legal and it is published as blank. **GitHub health** Not measured. github_url, github_stars, github_last_commit and github_archived are null on every entry in this build. The refresh rail specced in SPEC section 7.2 has not been run. An unstamped star count is a lie, so nothing is shown rather than something stale. **On GitHub** No GitHub organisation could be tied to explodingtopics.com with evidence on 2026-09-08. Recorded by the harvest: github candidates were seen but none passed the evidence rules. 1 candidate account seen and rejected by the evidence rules: explodingtopics. A name match alone is never accepted; the account has to point at the vendor domain. **Jobs it can do** No job tag on this entry. Reason recorded by the tagging pass: no-job-fits. Trend and topic velocity detection. It is not mention monitoring and it is not an account signal, so monitor-social-mentions would be wrong. Candidate new job: detect-emerging-topic. 981 of 1,252 entries are untagged. An empty list here means nobody has tagged this, not that the tool does nothing. The vocabulary is closed, so a tool whose job is genuinely not in it stays blank rather than being forced into the nearest tag. **Sources** - [https://explodingtopics.com/pricing](https://explodingtopics.com/pricing) - [https://explodingtopics.com/feature/et-api](https://explodingtopics.com/feature/et-api) 2 source URLs. Raw sources field, verbatim: https://explodingtopics.com/pricing, https://explodingtopics.com/feature/et-api **Notes, verbatim from the file** Confirmed current ownership - the pricing page footer states "Exploding Topics is a Trademark of Semrush Inc," and pricing links route through semrush.com, confirming the product is now sold as "Exploding Topics Pro" within Semrush's portfolio rather than as an independent company. Checked GitHub and PulseMCP - no MCP server found. [api_gate 2026-08-25] Reclassified unknown -> paid from the vendor's own page (https://explodingtopics.com/feature/et-api): the API is an add-on to the Business plan which starts at $249/mo, with request tiers at $1,000/mo for 1,000 requests, $2,000/mo for 5,000 and $4,000/mo for 25,000, so the real solo-operator floor is about $1,249/mo; commercial or product-embedded use needs custom pricing. 2026-09-02: re-checked explodingtopics.com (no llms.txt), the official MCP registry (no entry) and a web search. Parent Semrush publishes an official MCP (https://www.semrush.com/mcp/) over its Trends and Standard APIs, but neither that page nor developer.semrush.com names Exploding Topics data as exposed, so none-found stands for this product. **Provenance** - **Entry id**: 15-exploding-topics - **Source file**: 15-community-dark-social.md - **Source line**: 216 - **Tier**: RESEARCHED - **last_checked**: 2026-09-02 - **Data baked**: 2026-09-27 Every field above is rendered from directory.json exactly as the build produced it. Nothing is summarised and nothing is dropped. The one change made at render time is typographic and it is disclosed on the [methodology page](../methodology.md).