← Back to home
Comparison · Analytics

graphicalMCP vs webmockr

A side-by-side editorial comparison of graphicalMCP and webmockr — release velocity, themes, recent moves, and the top alternatives to consider.

graphicalMCP vs webmockr: at a glance

FeaturegraphicalMCPwebmockr
SectorAnalyticsAnalytics
Velocity score0.00.0
Sparks · 30d00
Top themesclinical-trials, multiple-comparisons, biostatistics, r-languagehttp-mocking, testing, httr2, ropensci
Last editorial update2h ago1h ago
WebsiteVisit →Visit →

What is graphicalMCP?

graphicalMCP is a narrow statistical tool being hardened rather than grown.

graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.

Read the full graphicalMCP trajectory →

What is webmockr?

The stubbing library added httr2 support, then spent a year cutting itself free of everything else

webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.

Read the full webmockr trajectory →

graphicalMCP vs webmockr: editorial side-by-side

G
graphicalMCP
ANALYTICS
0.0

graphicalMCP is a narrow statistical tool being hardened rather than grown.

◆ Current state

graphicalMCP implements graphical multiple comparison procedures — the method used to control family-wise error across several endpoints in a clinical trial. The package moved under the openpharma organisation in 0.2.6, picked up Hochberg tests and internal validation in 0.2.8, and its most recent release fixes a case where graph testing by closure disagreed with the rejection-based path. Releases are roughly annual and short.

◆ Where it's heading

The changelog reads as a package settling into reference-implementation status: procedure coverage widened once, then the work turned to proving the two computational routes through the same graph agree with each other. That agreement is the whole promise of this kind of tool, since the closure-based calculation is the definition and the rejection-based one is the fast path everyone actually runs. The openpharma move points the same direction — shared maintenance rather than a single author's project.

◆ Prediction

The entries show no feature roadmap, only correctness and validation work, so the next release is most likely another consistency or precision fix rather than a new procedure.

W
webmockr
ANALYTICS
0.0

The stubbing library added httr2 support, then spent a year cutting itself free of everything else

◆ Current state

webmockr intercepts HTTP requests in R tests and returns stubbed responses, and since 1.0.0 it covers all three clients that matter — httr, httr2 and crul. The releases through 2025 have been about shedding dependencies: internal R6 classes unexported in 2.1.0, crul demoted from Imports to Suggests in the same release, and the mutual dependency with vcr severed in 2.2.0. The package now installs and runs without pulling in the rest of the rOpenSci HTTP stack.

◆ Where it's heading

Two arcs run in sequence. The first is coverage — multiple queued responses in 0.7.0, basic auth mocking, async through crul, then httr2 — building out what can be stubbed. The second, starting with 2.0.0, is correctness and independence: stubs are now deleted if an error occurs mid-construction rather than lingering half-built, partial matching arrives for bodies and queries, and the dependency graph is pruned release by release. The 2.2.0 split from vcr landed within a minute of crul's release taking mocking control into its own clients.

◆ Prediction

RequestPattern is documented as still exported in 2.1.0 but slated for removal, so the next major release is where that lands. Expect continued dependency pruning rather than new client support — the three clients that exist are already covered.

Alternatives to graphicalMCP and webmockr

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 graphicalMCP or webmockr.

See all graphicalMCP alternatives → · See all webmockr alternatives →

Recent activity from graphicalMCP and webmockr

Latest ship moves from both products, interleaved chronologically. ⚡ = editorial spark.

  1. 4mo agographicalMCPClosure-based and rejection-based graph tests now agree
  2. 1y agowebmockrvcr dependency severed
  3. 1y agowebmockrInternal classes unexported; crul becomes an optional dependency
  4. 1y agographicalMCPHochberg tests and internal validation added
  5. 1y agowebmockrFailed stub construction cleans up; partial matching extends to bodies and queries
  6. 1y agographicalMCPRepository moved to the openpharma organisation
  7. 2y agowebmockrhttr2 joins httr and crul as a supported client
  8. 2y agographicalMCPCRAN resubmission housekeeping
  9. 2y agographicalMCPFirst release of the graphical MCP implementation
  10. 3y agowebmockrQueued responses, body matching and integer status codes fixed
  11. 3y agowebmockrRegex URI matching fixed

Frequently asked questions

What is the difference between graphicalMCP and webmockr?

They serve adjacent needs but don't currently overlap on shipped themes. graphicalMCP and webmockr 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.

Is graphicalMCP better than webmockr?

Sparkpulse doesn't pick a winner — we score release velocity, not feature parity. graphicalMCP and webmockr 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.

What are the best alternatives to graphicalMCP?

Top graphicalMCP alternatives in Analytics are ranked by recent ship velocity. Browse the "graphicalMCP alternatives" section above for the current picks, or visit /alternatives/graphicalmcp for the full list with editorial commentary on each.

What are the best alternatives to webmockr?

Top webmockr alternatives in Analytics are ranked by recent ship velocity. Browse the "webmockr alternatives" section above for the current picks, or visit /alternatives/webmockr for the full list with editorial commentary on each.