by KREISWOLKE 0 (0 reviews)

Kreiswolke Maintenance Agent Toolkit

Name: Kreiswolke Maintenance Agent Toolkit
Author: KREISWOLKE

The agent's toolkit for remote & safe WordPress maintenance: snapshots, updates, stack management, health checks, rollbacks, recovery, and hardening

Kreiswolke Maintenance Agent Toolkit ranks #21,266 among WordPress.org plugins with 50+ active installations, is #488 of 1,658 in the Performance category, and was last updated Sep 15, 2026. Data from WordPress.org, refreshed twice daily — see methodology.

Compatible with WP 7.1.4

v1.1.2 Current Version v1.1.2

Updated 1 month ago Last Update on 15 Sep, 2026

Refreshed 1 week ago Last Refreshed on

#488 of 1,658 in Performance Top 50% by installs Downloads -18% this week

View on WordPress.org

Rank

#21,266

— No change

Active Installs

50+

— No change

KW Avg Position

1 worse

Downloads

955

+1 today

Support Resolved

— No change

Rating

Review 0 out of 5

0 (0 reviews)

Next Milestone 60

Total Progress 30%

50+ 60+

2,317

Ranks to Climb

Growth Needed

8,000,000

Active Installs

Pro

Unlock Exact Install Count

See the precise estimated active installs for this plugin, calculated from real-time ranking data.

Exact install estimates within tiers
Track install growth over time
Milestone progress predictions

Upgrade to Pro

Need 7 more installs to reach 60+

Rank Changes

Current #21,266

Change

Best #

Upgrade to Pro

Unlock 30-day and 90-day rank history charts with a Pro subscription.

Upgrade Now

Active Installs Growth

Upgrade to Pro

Active Installs 0,000,000+

Growth +0.0%

Peak 0,000,000

Downloads Growth

Downloads

Growth

Peak

Upgrade to Pro

Unlock 30-day, 90-day, and yearly download history charts with a Pro subscription.

Upgrade Now

Reviews & Ratings

0.0

0 reviews

Overall 0%

0 (0%)

Track This Plugin

Get detailed analytics, keyword tracking, and position alerts delivered to your inbox.

Start Tracking Free

Plugin Details

Version: 1.1.2
Last Updated: Sep 15, 2026
Requires WP: 5.6+
Tested Up To: 7.1.4
PHP Version: 7.4 or higher
Author: KREISWOLKE

Support & Rating

Rating: ☆ ☆ ☆ ☆ ☆ 0
Reviews: 0
Support Threads: 0
Resolved: 0%

Keywords

backup maintenance rollback security updates

Upgrade to Pro

Unlock keyword rankings, search positions, and detailed analytics with a Pro subscription.

Upgrade Now

Similar Plugins

Adminify – White Label, Admin Menu Editor, Login Customizer

6K+ installs

#2,757

Master Addons for Elementor – Elementor Addons, Widgets, Mega Menu Builder, Popup Builder, Widget Builder & Template Kits

Wordfence Security – Firewall, Malware Scan, and Login Security

Speed Optimizer – The All-In-One Performance-Boosting Plugin

1M+ installs

#44

WP Fastest Cache – WordPress Cache Plugin

1M+ installs

#47

WP-Optimize – Cache, Compress images, Minify & Clean database to boost page speed & performance

View all Performance plugins

Frequently Asked Questions

Common questions about Kreiswolke Maintenance Agent Toolkit

Yes — that's what it's designed for. Every capability is a REST endpoint, registered with the WordPress Abilities API (WP 6.9+), so any MCP-capable client you trust — or plain curl — can discover and use them. Authentication is a standard WordPress Application Password; destructive operations are snapshot-first with on-disk verification. The plugin is useful to humans and to whatever tooling you already run.

Yes, fully. The app adds orchestration (the maintenance agent, scheduling, multi-site dashboards, reports); the plugin alone gives you the reports, rollback, careful updates, and hardening on a single site.

Not unless you connect it to the companion app, and then only as described under "External services". There is no telemetry, no tracking, no phone-home.

The emergency companion exists for exactly one scenario: a failed update breaks the main plugin (or the site), and you still need the heartbeat, the maintenance splash, and the restore tools to work. A regular plugin can't promise that — an MU-plugin can. It is written atomically (no half-written file can white-screen a site), updated only on activation/version change, and removed on uninstall.

Only when you enable an Apache-level hardening feature, and only inside one clearly marked block. The plugin backs up your .htaccess before every change, offers one-click restore, ships a kill-switch (create one file via FTP and all rules turn off), and removes the block fully on deactivation/uninstall. Blocking at the webserver is the point of these features: the request is rejected before PHP starts.

The gate puts a small PIN page in front of wp-login.php. It was built after watching bots hammer login pages on real servers: every attempt boots PHP, WordPress, and the database — a WordPress-layer rate limiter still pays that cost on each hit. The gate stops those requests at the webserver, before WordPress runs; bot/load protection is the primary purpose, the added login secrecy is a bonus. It is opt-in, requires a PIN before it can be enabled, and is built to fail open: if the plugin is removed by any means, the rule disables itself; a kill-switch file disables it instantly; logout/password-reset URLs are never blocked.

base64 encodes/decodes Ed25519 signature material and HTTP Basic auth — both are binary-to-text transports, not obfuscation; every site is commented. The single unserialize() reads WordPress's own Application Passwords usermeta and is hardened with allowed_classes => false. The error handler and shutdown hooks feed the plugin's own error log and let a restore endpoint return structured JSON even if a fatal occurs; the handler returns false so PHP's normal error flow is untouched.

The "Bad User-Agent Blocklist" hardening rule blocks requests whose User-Agent matches known scanner tooling — and that includes the default identity of Python (python-requests, Python-urllib) and Go (Go-http-client) HTTP clients, plus empty User-Agents. If your own script uses those defaults, every request gets a webserver-level 403, including REST API calls with valid credentials. Two fixes, either works: give your script a custom User-Agent header (good practice anyway), or add a distinctive part of its name to the rule's "Allowed user agents" list on the Hardening tab.

Everything except the Apache-level rules, which are detected as not applicable; for each, the plugin shows an equivalent nginx snippet to paste into your server config instead of pretending it worked.

No. The plugin is a deterministic toolkit — predictable, inspectable, no model calls. AI-assisted planning happens in the optional companion app, server-side, only for connected sites.