Publication Cadence Tracker MCP Server
You can analyze company domains to measure their long-form editorial publication cadence and whether it is accelerating or declining.
Track one domain or a batch, returning 30-day/90-day/12-month post counts, monthly average, trend, percent change, recent post date, publication URL, format mix, author count, discovery method, confidence, and evidence.
Detect
accelerating,steady,declining,dormant, orunknownby comparing the last 90 days with the prior 275 days, normalized to posts per month.Find publication sections across hosts/locales and reject release/changelog feeds; dates come from post pages, not sitemap
lastmod.Check reliability flags: unreliable date source nulls counts; estimates and partial crawls are flagged.
Tune crawls with
max_pages_to_date,domain_time_budget_ms,batchSize, andskipCache; read-only, requiresAPIFY_TOKEN, and consumes Apify credits.
Click on "Deploy Server".
Wait a few minutes for the server to deploy. Once ready, it will show a "Started" state.
In the chat, type
@followed by the MCP server name and your instructions, e.g., "@Publication Cadence Tracker MCP Server What's the publication trend for openai.com?"
That's it! The server will respond to your query, and you can continue using it as needed.
Here is a step-by-step guide with screenshots.
Publication Cadence Tracker MCP Server
MCP server for the Mamba Labs Publishing Frequency Tracker actor on Apify.
Give it a company domain. It tells your agent how much long-form work that company publishes per month, and whether that rate is rising or falling.
Tool
track_publication_cadence
Returns a flat row per domain: posts_last_30d, posts_last_90d, posts_last_12m, avg_posts_per_month, cadence_trend (accelerating, steady, declining, dormant, unknown), trend_pct_change, most_recent_post_date, days_since_last_post, publication_url, formats_detected[], distinct_authors_count, discovery_method, confidence, and an evidence[] array of quotable strings.
Related MCP server: company-change-event-feed
Why the trend and not the count
Four pieces a month is unremarkable. Going from four to twelve in six months is a content operation outgrowing its staff. The comparison is stated rather than implied: the last 90 days against the prior 275 days, both normalized to posts per month, with accelerating and declining set at 25 percent either way.
This is editorial output volume, not changelog monitoring. A release feed is detected and rejected rather than counted as published work.
The number it refuses to give you
Publication dates come from the post pages, never from sitemap lastmod. Across 100 measured URL pairs, lastmod tracked the page's own dateModified and ran later than datePublished by a median of 151 to 1653 days on four of six sites. A cadence built on it would report a company that refreshed 200 old posts as a company that published 200 posts.
A page field can fail the same way, so it is checked against its own distribution and against the site's feed. When it fails, date_source_reliable comes back false and every count is nulled. Check that field before quoting a number.
Measured on nine live domains: a rate recovered on 5 of 6 publishers, 3 of 3 controls correctly returning nothing. The one miss is the guard refusing a site whose date field tracks edits.
track_publication_cadence
Input | Type | Notes |
| string | One company domain. |
| string[] | Batch. Takes precedence over |
| integer | Post pages fetched per domain, default 400. Above this the counts are estimated from an even sample. |
| integer | Hard per-domain wall-clock ceiling, default 75000. |
| integer | Concurrent domains, default 2. |
| boolean | Ignore the 3 day result cache. |
| integer | 1 to 16, default 8. Pages fetched at once within one domain. |
| integer | 4 to 40, default 18. Cap on sitemap files fetched per domain. |
| integer | 3000 to 20000, default 9000. Per HTTP request timeout. |
| number | Optional spending cap for this call, in USD. The actor stops before any charge that would take the run past this amount and keeps every row already charged. |
What it actually measures
Not whether a company has a blog. How much it published, when, and whether the rate moved.
Finding the blog is most of the work, and it is where a naive version fails. The blog often lives on a different host from the apex and the apex sitemap never mentions it (blog.hubspot.com). A homepage sometimes advertises only a changelog feed while linking to the real blog repeatedly (about.gitlab.com). Paths are often locale prefixed, so /en-uk/ and /bg-bg/ fragment the archive into forty pieces. All three are handled, and publication_url reports a locale-prefixed section as https://example.com/*/knowledge/.
Three fields to read before you trust a number. date_source_reliable false means the site's date field tracks edits rather than publication and every count has been nulled. counts_are_estimate true means the archive was larger than the page budget and the counts come from a scaled even sample, so two runs can differ by a few posts. partial_result true means the wall-clock budget stopped the crawl and the numbers are lower bounds.
Pricing
You pay per event on Apify, billed to your own Apify account. Prices from the live pricing record, read 2026-10-16:
Event | Price per event (USD) | Fires when |
| $0.00005 | Charged once when the run starts. |
| $0.004 on the Free plan, down to $0.0034 on higher Apify plans | Charged once per domain analyzed. Domains with no publication section, and domains whose date field turns out to track edits rather than publication, still count as analyzed and are charged. |
The actor's Apify page carries the current prices. Running this server consumes Apify credits.
Setup
{
"mcpServers": {
"mamba-publication-cadence-tracker": {
"command": "npx",
"args": ["-y", "@mambalabsdev/mcp-publication-cadence-tracker"],
"env": { "APIFY_TOKEN": "your-apify-token" }
}
}
}Get a token at console.apify.com/account/integrations. Read-only; consumes Apify credits per domain analyzed.
Also available
This tool is also exposed by the GTM Suite umbrella server, alongside the rest of the Mamba Labs GTM actors, if you would rather run one server than many.
Built by Mamba Labs.
Available Tools
1 tooltrack_publication_cadenceTrack Publication CadenceARead-onlyIdempotent
Given a company domain, measure how much long-form work that company publishes and whether the rate is rising or falling. Returns post counts for the last 30 days, 90 days and 12 months, a monthly average, and a cadence_trend of accelerating, steady, declining, dormant or unknown, plus the percent change behind it. The trend compares the last 90 days against the prior 275 days, both normalized to posts per month. Also returns the blog URL, the format mix (blog posts, guides, reports, case studies, whitepapers, podcasts, videos, press releases, research), the number of distinct bylines, and how the post list was discovered. This measures EDITORIAL output volume, not product changelogs: a release feed is detected and rejected rather than counted. Publication dates are read from the post pages themselves, because sitemap lastmod was measured to be a modification date that runs later than publication by a median of 151 to 1653 days. When a site's date field turns out to track edits rather than publication, date_source_reliable comes back false and every count is nulled rather than reported wrong, so check that field before quoting a number. Counts are a census when the archive fits the page budget and a scaled even sample otherwise, flagged by counts_are_estimate. Public sitemaps, feeds and pages only. Returns flat Clay-ready JSON. Read-only; requires an APIFY_TOKEN and consumes Apify credits per domain analyzed.
Inputs: domain, domains, batchSize, skipCache, +2 more.
Tool Schema Changelog
Recent tool additions, removals, and schema changes observed during successful MCP inspections.
Loading tool schema changelog…
TDQS
Scored across 1 tool
The server has only one tool, so there is no possibility of confusion between tools. The tool's purpose is clearly described, making selection unambiguous.
The single tool uses a clear verb_noun pattern ('track_publication_cadence') that matches the server's name, providing a consistent and predictable naming scheme.
With only one tool, the server feels slightly thin, but the tool is comprehensive in its function. This falls at the borderline for appropriate tool count.
The single tool thoroughly covers the domain of tracking publication cadence, including robust handling of date reliability, estimates, and format details. There are no obvious gaps in the stated purpose.
Maintenance
Related MCP Connectors
Public company research with 9 focused tools: technology, hiring intent, open jobs, job changes, Google Ads and published contacts. Get a qualifying four-signal company profile for $0.03, plus breakout_summary growth estimates. Start with the free labeled example.com sandbox, 10 free successful calls per agent per UTC day (subject to a shared network ceiling), or an eligible 25-call trial. Setup: https://gethirepulse.xyz/?ref=glama-b2b#start-b2b . Reconnect to https://gethirepulse.xyz/mcp for all 27 tools, including batch and footprint research. Growth signals are estimates.
AI visibility for your brand: scores, competitors, prompts, site health and articles.
Live market intelligence & AI content strategy: trends, competitor moves, content calendar.
Deterministic public-web change observation with evidence-bound commercial interpretation.
Related MCP Servers
- AlicenseNot gradedqualityDmaintenanceProvides deep, structured access to Substack publications with real-time content analysis, including sentiment analysis, readability metrics, and publishing patterns.13MIT
- AlicenseAqualityBmaintenanceMonitors a company domain for changes in hiring, tech stack, funding, firmographics, and social presence, returning only the deltas as typed change events.1355 npmMIT
- AlicenseAqualityBmaintenanceEnables users to track a list of company domains and retrieve only the job-board changes since the previous run, including new, closed, and reposted postings with full descriptions, stable posting keys, and 30-day hiring velocity per company. It runs on Apify and exposes this through a single tool call.1112 npmMIT
- AlicenseAqualityBmaintenanceEnables discovery of a company's public feature board (Canny, Featurebase, Frill, UserVoice, Productboard) from its domain and retrieval of its most-voted requests with votes, status, comments, and the integrations customers ask for. Supports monitoring runs that surface only new requests, status changes, and vote jumps since a prior run using a saved state key.1111 npmMIT