com.mambabuilt/mcp-publication-cadence-tracker
NPM · @MAMBALABSDEV/MCP-PUBLICATION-CADENCE-TRACKER · SCANNED OCT 1
How often a company publishes long-form work, and whether that rate is rising or falling.
Available components
How this component scores in each security and reliability category. Every signal is checked automatically from public evidence about the published package, including repeated runs of it in an isolated sandbox, and we only credit what we can confirm. How we score → Why this is hard to score →
Supply Chain Security98
- No malware found by supply-chain analysis.Pass
- No known CVEs affecting this package version or its production dependencies.Pass
- No install/post-install scripts declared.Pass
- 31 of 93 dependencies flagged as unhealthy. View diagnostics → Partial
Provenance & Transparency48
- Source repository is publicly reachable at the declared URL. View diagnostics → Pass
- Provenance check failed: no build-provenance attestation is published. See how to fix → View diagnostics → Fail
- Clear OSI-approved license (MIT).Pass
- Actively maintained (last published 49 days ago).Pass
- Publishes a security disclosure policy (SECURITY.md).Pass
Schema Quality & AI Usability63
- AI-judged instruction clarity (excellent).Pass
- Context-footprint check failed: tool/resource definitions use about 575 tokens (~575/item across 1 items; 1 tools + 0 resources), over budget; trim descriptions and params. See how to fix → Fail
- Usage-examples check failed: none of the tools include examples. See how to fix → Fail
Stability & Change Management93
- Stability observed for 28 of 30 days with no destabilising changes; credit accrues until the full window elapses.Partial
Tool Coverage100
- 100% of tools have a non-trivial description (not blank, and not just the tool's name).Pass
- 100% of tool parameters carry a description.Pass
Tool Safety100
- No prompt-injection markers were found in the server instructions, tool names or descriptions we captured.Pass
- We read all 1 captured tool definition(s), and no name or description among them implies an irreversible operation.Pass
- An AI judge read all 1 captured unit(s) of tool text and found none that tries to manipulate the model reading it.Pass
Capabilities100
- Implements a supported MCP spec version (2025-11-25); the latest is 2026-07-28.Pass
How do I install the com.mambabuilt/mcp-publication-cadence-tracker server?
com.mambabuilt/mcp-publication-cadence-tracker runs locally as an npm package, launched with npx -y @mambalabsdev/mcp-publication-cadence-tracker. Ready-made configuration for Claude, Cursor, VS Code, Codex and 5 more is on this page, copied from each client's own documentation.
npm · @mambalabsdev/mcp-publication-cadence-tracker
claude mcp add com-mambabuilt-mcp-publication-cadence-tracker -- npx -y @mambalabsdev/mcp-publication-cadence-tracker
{
"mcpServers": {
"com-mambabuilt-mcp-publication-cadence-tracker": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-publication-cadence-tracker"
]
}
}
} {
"servers": {
"com-mambabuilt-mcp-publication-cadence-tracker": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-publication-cadence-tracker"
]
}
}
} codex mcp add com-mambabuilt-mcp-publication-cadence-tracker -- npx -y @mambalabsdev/mcp-publication-cadence-tracker
{
"$schema": "https://opencode.ai/config.json",
"mcp": {
"com-mambabuilt-mcp-publication-cadence-tracker": {
"type": "local",
"command": [
"npx",
"-y",
"@mambalabsdev/mcp-publication-cadence-tracker"
],
"enabled": true
}
}
} openclaw mcp add com-mambabuilt-mcp-publication-cadence-tracker --command npx --arg -y --arg @mambalabsdev/mcp-publication-cadence-tracker
mcp_servers:
com-mambabuilt-mcp-publication-cadence-tracker:
command: "npx"
args: ["-y", "@mambalabsdev/mcp-publication-cadence-tracker"] {
"McpServers": {
"com-mambabuilt-mcp-publication-cadence-tracker": {
"Transport": "stdio",
"Command": "npx",
"Arguments": [
"-y",
"@mambalabsdev/mcp-publication-cadence-tracker"
]
}
}
} assistant mcp add com-mambabuilt-mcp-publication-cadence-tracker -t stdio -c npx -a -y @mambalabsdev/mcp-publication-cadence-tracker
{
"mcpServers": {
"com-mambabuilt-mcp-publication-cadence-tracker": {
"command": "npx",
"args": [
"-y",
"@mambalabsdev/mcp-publication-cadence-tracker"
]
}
}
} Every change we have recorded for this component, newest first. Security-relevant changes are always shown. ▲ marks a change for the better, ▼ a change for the worse; unmarked changes are neutral.
- 29 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 28 Sept 26 −2
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 27 Sept 26 0
- Stability: 0.97 → pass security
- 26 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 93 to 97. That category is still filling its 30-day observation window: 28 days of observed history at the previous scan, 29 at this one. The score rises as the window fills, whether or not the server changes.
- 25 Sept 26 0
- We updated how we score, so this day's move reflects our rubric, not a change to the server See what changed → functional
- 23 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 83 to 87. That category is still filling its 30-day observation window: 25 days of observed history at the previous scan, 26 at this one. The score rises as the window fills, whether or not the server changes.
- 21 Sept 26 +1
No change was recorded against any check on this day. Stability & Change Management went from 77 to 80. That category is still filling its 30-day observation window: 23 days of observed history at the previous scan, 24 at this one. The score rises as the window fills, whether or not the server changes.
- 20 Sept 26 −3
- Stability: pass → 0.77 functional
Diagnostic detail from the automated scan of this channel: what the scanner observed at each step, so you can see exactly where a check passed or failed. It is informational only and never changes the trust score.
Captured 1 Oct 2026 · Analysed npm/@mambalabsdev/mcp-publication-cadence-tracker@1.1.1
Provenance No attestation
The registry publishes no build provenance for this version, so there is nothing to verify.
| Result | No attestation |
|---|---|
| Ecosystem | npm |
Background: How many MCP packages publish verified provenance →
Dependencies 93 packages
| Packages resolved | 93 |
|---|---|
| Stale | 31 |
| Tree resolution | Complete |
Background: SBOMs and build attestations, explained →
The tools this component advertises to a client, with an estimated token cost for each. Expand a tool to see its parameters and schema. The per-tool counts are indicative and are not scored directly; the schema's total context footprint is one signal in Schema Quality & AI Usability. A tool's description is untrusted text the model reads on every call, which is what makes this list a security surface and not just an inventory: how tool poisoning works →
track_publication_cadence Track Publication Cadence ~575
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.
| Name | Type | Req | Description |
|---|---|---|---|
| batchSize | integer | – | How many domains to analyze concurrently. Default 2. |
| domain | string | – | A single company domain, e.g. zapier.com. Provide either domain or domains. |
| domain_time_budget_ms | integer | – | Hard wall-clock ceiling per domain, default 75000. When it is nearly spent the crawl stops and the row is returned with partial_result true and reduced confidence rather than timing out. |
| domains | array | – | Batch mode: several company domains analyzed in one call. Takes precedence over domain. |
| max_pages_to_date | integer | – | How many post pages to fetch per domain for dating. Default 400. Above this cap the counts are estimated from an even sample across the archive and counts_are_estimate is set true. Raise it for a tig… |
| max_sitemap_fetches | integer | – | Cap on how many sitemap files are fetched per domain. Lower it to bound run time on sites with deeply nested sitemap indexes. |
| page_concurrency | integer | – | How many pages are fetched concurrently within one domain. |
| request_timeout_ms | integer | – | Per-HTTP-request timeout in milliseconds. |
| skipCache | boolean | – | Force a fresh crawl and ignore the 3 day result cache. |
No output schema declared.
No examples provided.
What is the com.mambabuilt/mcp-publication-cadence-tracker server?
com.mambabuilt/mcp-publication-cadence-tracker is listed in the public MCP registry as com.mambabuilt/mcp-publication-cadence-tracker. How often a company publishes long-form work, and whether that rate is rising or falling. This page covers its npm package (@mambalabsdev/mcp-publication-cadence-tracker).
Is the com.mambabuilt/mcp-publication-cadence-tracker server safe to use?
com.mambabuilt/mcp-publication-cadence-tracker scores 81 out of 100 on VerifyMCP. We found no known CVEs affecting it as of 1 October 2026. It declares no install or post-install scripts. That is a record of what we were able to check automatically, not an endorsement. The category breakdown on this page shows every signal behind the number, including the ones we could not confirm.
What tools does the com.mambabuilt/mcp-publication-cadence-tracker server expose?
com.mambabuilt/mcp-publication-cadence-tracker exposes 1 tool: track_publication_cadence. Their descriptions and schemas cost roughly 575 tokens of context every time the server is loaded.
Is the com.mambabuilt/mcp-publication-cadence-tracker server still maintained?
com.mambabuilt/mcp-publication-cadence-tracker is still listed as active in the MCP registry. We last reached this channel on 1 October 2026. Those dates come from our own scans of the registry and the channel itself, not from anything the publisher announced.
What licence is the com.mambabuilt/mcp-publication-cadence-tracker server under?
com.mambabuilt/mcp-publication-cadence-tracker declares the MIT licence, which is OSI-approved. That covers the source only, and says nothing about the cost of any service it calls.