Health Endpoint

44 Quality Score

Active Installs

16/30

With about 3,000 active installs and a narrow, infrastructure-focused use case, the plugin occupies a small but stable niche rather than a mainstream audience.

Update Freshness

7/25

The plugin was updated on 9 March 2025 and is tested against WordPress 6.7.5, which signals active upkeep, though the very small surface area means there is relatively little to maintain.

User Rating

6/15

A perfect 100/100 comes from only 2 ratings, which is not enough feedback to draw confident conclusions about real-world reliability.

Support Health

8/15

There are zero support threads and zero resolutions on the WordPress.org forums, indicating either very few problems or very low community engagement around the plugin.

WP Compatibility

8/15

It requires WordPress 3.5 or higher and lists no specific PHP version, which keeps compatibility broad but also means PHP requirements are left to chance rather than being declared.

Scores higher than 1% of indexed plugins

About

Creates a /health endpoint that returns a 200 OK HTTP status code while WordPress is performing correctly.

Active Installs 3k+

Rating ★★★★★ 5/5

Last Updated 2025-03-09 3:40pm GMT

Requires WordPress 3.5+

Tested Up To 6.7.7

✓ No known vulnerabilities

What It Does

Health Endpoint registers a custom /health URL on a WordPress site that responds with a 200 OK HTTP status code when the application is reachable and responding normally. External uptime and infrastructure monitoring tools can then ping this URL on a schedule to confirm the site is online without needing to scrape or parse full HTML pages.

Who It's For

This plugin is aimed at site owners and operators who use external uptime monitoring, load balancers, or status pages to track availability of WordPress installations, including managed hosting providers, SaaS platforms, and agencies running critical client sites. It suits environments where automated infrastructure tooling needs a lightweight, predictable endpoint that is cheaper to probe than a full front-end page load.

Who Should Skip It

If you already have monitoring tools that can handle full-page checks, or if your host provides built-in health probes, this plugin adds little value. Casual bloggers and small sites that do not rely on automated uptime alerting will not gain much from adding another endpoint to maintain.

The Bottom Line

Health Endpoint does exactly one small thing, and it appears to do it well, with recent updates and clean compatibility. The quality score of 47.37/100 reflects limited popularity, scarce user feedback, and an absence of public support activity rather than broken functionality. For teams that need a dedicated probe endpoint and prefer a minimal, single-purpose plugin, it is a reasonable choice, but anyone wanting richer health data, versioned history, or community support should look elsewhere.

Related Plugins

Disable WP REST API 81/100

Pick this instead if your priority is locking down WordPress REST access rather than exposing a monitoring endpoint.

Mailgun for WordPress 81/100

Pick this instead if your operational concern is reliable transactional email delivery rather than HTTP uptime checks.

WPGet API – Connect to any external REST API 80/100

Pick this instead if you need to pull data from third-party APIs into WordPress rather than expose a status endpoint to them.

WP REST Cache 80/100

Pick this instead if the bottleneck you care about is REST API response speed, not availability monitoring.

APCu Manager 79/100

Pick this instead if you want to tune object cache performance for monitoring or scaling rather than add a separate health route.