gMCPLite
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
A side-by-side editorial comparison of admiralonco and qualtRics — release velocity, themes, recent moves, and the top alternatives to consider.
The oncology ADaM helper is dissolving into admiral core, one deprecation at a time.
admiralonco is the oncology companion to admiral, and it ships response-criteria recipes rather than code: RECIST, iRECIST, IMWG, GCIG and PCWG3 each arrive as a vignette plus an ADaM template. Cadence is one or two releases a year, each adding a criteria vignette. The 1.4.0 release began deprecating most of the package's own exported functions in favour of generic admiral equivalents.
qualtRics moved its contact functions onto XM Directory days before the old endpoints died.
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
admiralonco is the oncology companion to admiral, and it ships response-criteria recipes rather than code: RECIST, iRECIST, IMWG, GCIG and PCWG3 each arrive as a vignette plus an ADaM template. Cadence is one or two releases a year, each adding a criteria vignette. The 1.4.0 release began deprecating most of the package's own exported functions in favour of generic admiral equivalents.
The package is converging on a documentation-and-templates model: reusable derivation logic moves upstream into admiral, and admiralonco keeps only the oncology-specific know-how. Every release since 1.0.0 has added a criteria vignette rather than new exported functions, and 1.4.1 extends that by making the template set browsable from the Get Started menu. The surface users program against is shrinking while the guidance they read is growing.
Expect the deprecation cycle started in 1.4.0 to advance through its warning and error phases across the next one or two releases, with new work arriving as another response-criteria vignette rather than new functions.
qualtRics is the R client for the Qualtrics v3 API — fetching survey responses, definitions, distributions, and contact lists into tidy data frames. Version 3.3.0 migrated all_mailinglists() and fetch_mailinglist() from the deprecated Research Core Contacts endpoints to XM Directory, ahead of Qualtrics retiring the old ones on June 30, 2026. Authentication and directory discovery are handled automatically, but the new endpoints return a different data shape, so column names changed. Before that, releases had been steady maintenance for two years, mostly around how survey response archives are unpacked.
This package's roadmap is set by Qualtrics, not by its maintainers, and the release history reads as a sequence of accommodations — endpoint changes, retired APIs, and edge cases in exported files. The team's own recurring theme is reducing surprise: caching was removed from fetch_survey() in 3.2.0 so results are never stale, error handling was standardized on retry semantics, and column mappings were made inspectable via extract_colmap(). Feature additions, when they come, are new endpoints wrapped rather than new abstractions.
With the Contacts migration complete, the next likely work is bringing the remaining Research Core-era functions onto XM Directory equivalents before Qualtrics retires more of the old surface.
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 admiralonco or qualtRics.
gMCPLite exists to be gMCP without Java, and its releases guard that boundary rather than extend it.
Extracted from Quarto's CLI, typst-gather learned to explain a dependency tree before fetching it.
naijR is assembling the Nigerian reference data R analysts otherwise hand-code every time.
RBesT is teaching its Bayesian decision rules to answer two-sided questions.
graphicalMCP is a narrow statistical tool being hardened rather than grown.
rtflite stopped being an RTF writer and became the conversion layer for clinical table output.
See all admiralonco alternatives → · See all qualtRics alternatives →
Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.
They serve adjacent needs but don't currently overlap on shipped themes. admiralonco and qualtRics are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). 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. admiralonco and qualtRics are shipping at a similar cadence (velocity 0.0 vs 0.0, both within Sparkpulse's "active" band). For your specific use case, the alternatives sections above list other Analytics products to evaluate alongside.
Top admiralonco alternatives in Analytics are ranked by recent ship velocity. Browse the "admiralonco alternatives" section above for the current picks, or visit /alternatives/admiralonco for the full list with editorial commentary on each.
Top qualtRics alternatives in Analytics are ranked by recent ship velocity. Browse the "qualtRics alternatives" section above for the current picks, or visit /alternatives/qualtrics for the full list with editorial commentary on each.