compositional.mle
An MLE package rebuilt around composable solvers, then renamed to match.
A side-by-side editorial comparison of mcptools and tidycmprsk — release velocity, themes, recent moves, and the top alternatives to consider.
R became a deployable MCP server, not just a local one.
mcptools lets R act as an MCP server exposing tools to LLM clients, and lets those clients reach into running R sessions. It reached 1.0.0 in mid-2026 after a rename from acquaint and a reversal of its dependency relationship with btw. The trajectory of its releases tracks the MCP specification closely — transport options, protocol version negotiation, and content types have each arrived as the spec settled them.
Competing-risks modelling that now moves only when its neighbours do.
tidycmprsk wraps competing risks regression and cumulative incidence estimation in tidy-style output, so results slot into gtsummary tables and ggsurvfit plots. The last two releases are small: 1.1.2 sorts tidy.tidycuminc() output by stratum, 1.1.1 is an HTML5 documentation update for CRAN. The substantive work in the window is 1.1.0, which reorganised the gtsummary relationship.
mcptools lets R act as an MCP server exposing tools to LLM clients, and lets those clients reach into running R sessions. It reached 1.0.0 in mid-2026 after a rename from acquaint and a reversal of its dependency relationship with btw. The trajectory of its releases tracks the MCP specification closely — transport options, protocol version negotiation, and content types have each arrived as the spec settled them.
The package has moved outward along two axes: transport, from stdio to HTTP to a hosted Posit Connect engine, and content, from text-only tool results to inline images and structured JSON. The most recent release turns to the problems that only appear once something is deployed — choosing the right R session among several, and isolating IPC per user. That shift from capability to multi-user correctness is what a package looks like after it starts being run somewhere other than a developer's laptop.
Expect authentication to be addressed on the HTTP transport, which the notes explicitly flag as authless, and continued tracking of MCP protocol revisions as they are published.
tidycmprsk wraps competing risks regression and cumulative incidence estimation in tidy-style output, so results slot into gtsummary tables and ggsurvfit plots. The last two releases are small: 1.1.2 sorts tidy.tidycuminc() output by stratum, 1.1.1 is an HTML5 documentation update for CRAN. The substantive work in the window is 1.1.0, which reorganised the gtsummary relationship.
The package has spent its releases handing responsibilities to neighbouring packages rather than growing its own surface. Plotting was deprecated then made defunct in favour of ggsurvfit::ggcuminc(), and 1.1.0 moved the regression table methods so that gtsummary could drop tidycmprsk as a dependency. What remains is the estimation core plus the S3 methods that let other packages consume it, which is a deliberate narrowing.
Expect releases to continue tracking changes in gtsummary and the broader tidy survival stack rather than adding estimation features.
Other Analytics products tracked by Sparkpulse, ranked by recent ship velocity. Each card links to a full editorial trajectory and lets you pivot into a head-to-head comparison with either mcptools or tidycmprsk.
An MLE package rebuilt around composable solvers, then renamed to match.
nabla dropped its C++ engine to chase exact derivatives at any order.
Eight months from first release to keyring caching and workload identity.
A research-project workflow package where the interesting work is in the plumbing.
A cyclomatic complexity checker that ships once every couple of years, and lands when it does.
Extreme value sampling in pure upkeep mode, mostly answering to Rcpp and CRAN.
See all mcptools alternatives → · See all tidycmprsk alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
Both compete on the same themes — r-package — within Analytics. mcptools is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. See the at-a-glance table above for a side-by-side breakdown of velocity, recent sparks, and editorial themes.
Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. mcptools is currently shipping more aggressively (velocity 2.5 vs 0.0), with 0 editorial sparks in the last 30 days against 0. For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top mcptools alternatives in Analytics are ranked by recent ship velocity. Browse the "mcptools alternatives" section above for the current picks, or visit /alternatives/mcptools for the full list with editorial commentary on each.
Top tidycmprsk alternatives in Analytics are ranked by recent ship velocity. Browse the "tidycmprsk alternatives" section above for the current picks, or visit /alternatives/tidycmprsk for the full list with editorial commentary on each.