Vendor: https://explodingtopics.com · entry id 15-exploding-topics · source 15-community-dark-social.md line 216
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-08-24 and has not been re-fetched since.
mcp_status, verbatim from the file:
none-found
mcp_url, verbatim from the file:
none
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)
No documentation URL recorded.
263 of 293 entries are in the same position. Blank is legal and it is published as blank.
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.
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.
22 of 293 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.
2 source URLs. Raw sources field, verbatim:
https://explodingtopics.com/pricing, https://explodingtopics.com/feature/et-api
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.