Title: SysDoctor
Author: syswppro
Published: <strong>November 18, 2026</strong>
Last modified: November 18, 2026

---

Search plugins

![](https://ps.w.org/sysdoctor/assets/banner-772x250.png?rev=3809899)

![](https://ps.w.org/sysdoctor/assets/icon-256x256.png?rev=3809899)

# SysDoctor

 By [syswppro](https://profiles.wordpress.org/syswppro/)

[Download](https://downloads.wordpress.org/plugin/sysdoctor.1.4.0.zip)

 * [Details](https://wordpress.org/plugins/sysdoctor/#description)
 * [Reviews](https://wordpress.org/plugins/sysdoctor/#reviews)
 *  [Installation](https://wordpress.org/plugins/sysdoctor/#installation)
 * [Development](https://wordpress.org/plugins/sysdoctor/#developers)

 [Support](https://wordpress.org/support/plugin/sysdoctor/)

## Description

SysDoctor is a **read-only** connector that links your WordPress site to the Site
Doctor monitoring service (by SysWP, at https://sitedoctor.syswp.pro), so you can
see what is wrong with a site without ever giving a plugin write access to it.

This WordPress.org edition is **monitoring only**. It never modifies, cleans, edits,
or logs into your site, and never changes your content, files or settings. It reads
the metadata needed to spot problems and reports it to the Site Doctor service, 
where it becomes findings you read in your dashboard. It also keeps its own **security
activity log** (logins, administrator changes, plugin/theme/option changes) in its
own database table — the same idea as activity-log plugins — so those events show
on your timeline. Metadata only: never passwords, secrets or content.

Built for agencies and freelancers who maintain many client WordPress sites and 
need a fast, trustworthy answer to “what is going on with this site?” without handing
control to a plugin.

#### What it monitors (read-only)

 * **Uptime and downtime** — checked from outside the site, with the likely root
   cause when it goes down.
 * **Outdated and known-vulnerable plugins and themes** — matched offline against
   a mirror of the Wordfence vulnerability database.
 * **Security changes** — new administrator accounts, modified core files, and unexpected
   changes (detection and alerting, not removal).
 * **Performance** — render-blocking scripts and the real cause of slow page loads.
 * **Contact forms** — checked from outside by the Site Doctor service, so you learn
   if a form stops submitting.
 * **Scheduled tasks** — whether WP-Cron is actually firing.
 * **Change tracking** — what changed on the site, and when.

#### What it does NOT do

 * It **never changes your site**. No fixes, no cleanups, no file edits, no auto-
   login, no edits to your content, themes or settings. (It does keep its own security
   activity log, in its own table — standard activity-log behavior.)
 * It does **not** send your secrets. This edition transmits plugin and theme versions,
   vulnerability matches, uptime, performance and change metadata — not `wp-config`
   constants, passwords, or post content.
 * It is **not** a firewall or a malware remover. It detects and reports; you decide
   what to do and apply any change yourself from wp-admin.

#### How it works

 1. Create a free Site Doctor account and add your site.
 2. Install this plugin and paste the connection key shown in your Site Doctor dashboard.
 3. The Site Doctor service reads only the metadata it needs and shows the findings.
    You review them in your dashboard; nothing is ever changed on your site.

#### Who it is for

 * **Agencies and freelancers** — keep an eye on many client sites from a single
   dashboard.
 * **Site owners** — find out the moment something breaks, and why.
 * **Maintainers** — a read-only second opinion that cannot itself break the site.

SysDoctor is a connector to an external service, like Akismet. It requires a Site
Doctor account, and the exact data it sends is documented in the “External services”
section below. Service details and plans are at https://sitedoctor.syswp.pro.

### How to use

Once a site is connected, you work with it through the Site Doctor service in one
of two ways:

#### 1. Use Doc, the built-in assistant

Doc is the AI assistant inside your Site Doctor dashboard. Ask it about any connected
site in plain language and it reads the live, read-only data to answer — no extra
setup beyond connecting the site.

#### 2. Connect your own AI

Site Doctor also exposes an MCP (Model Context Protocol) server, so you can plug
it into your own AI client (for example Claude) and let the assistant you already
use query your sites directly. Same read-only data, driven from your own AI.

Either way the plugin on your site never changes your content, files or settings:
it only answers signed requests from the service and keeps its own security activity
log.

#### What to ask

Site Doctor is not only for security. A few examples of what you can ask Doc (or
your own AI):

 * **Security:** “Is this site compromised? Any new administrator accounts or modified
   core files?”
 * **Vulnerabilities:** “Which plugins or themes here are outdated or have known
   vulnerabilities?”
 * **Performance:** “Why is this site slow, and what is the single biggest thing
   hurting load time?”
 * **Uptime:** “Has this site gone down this month, and what was the likely cause?”
 * **Database health:** “Is the database bloated? Any huge autoloaded options slowing
   every page?”
 * **Maintenance:** “Is WP-Cron actually firing? Any scheduled tasks stuck?”
 * **Change tracking:** “What changed on this site in the last few days?”
 * **Fleet overview:** “Across all my sites, which ones need attention this week?”

### External services

This plugin connects to the **Site Doctor** monitoring service at https://sitedoctor.
syswp.pro. The service is required for the plugin to do anything useful: you opt
in by creating a Site Doctor account and pasting the connection key it gives you
under **Settings  SysDoctor**. This is the same model as Akismet and other service-
connected plugins.

This edition makes **no outbound calls of its own**, with one optional exception:
the core file integrity check (see “WordPress.org core checksums” below). It runs
no background tasks and never contacts the Site Doctor service on a schedule or 
on a page load — it only **responds** to the Site Doctor service when that service
sends it an authenticated request.

#### Monitoring reads (the service requests, your site responds)

 * **When:** when the Site Doctor service sends an authenticated request to your
   site at `https://your-site/?syswp_site_doctor_probe=...`. Each request is signed
   with HMAC-SHA256 using the secret derived from your connection key, with a single-
   use nonce and a ±5-minute timestamp window; unsigned, replayed or stale requests
   are rejected.
 * **Data returned to the service:** WordPress, PHP and plugin/theme names and versions;
   known-vulnerability matches; a list of administrator accounts (login, role and
   email _domain_ only — never the full address — to flag unexpected admins); indicators
   of modified or suspicious files and options; performance timings; whether WP-
   Cron runs; recent server-log digests; and change metadata (what changed and when).
 * **Data NOT sent:** `wp-config.php` constants, database passwords, authentication
   keys/salts, API keys, full email addresses, cookies, session tokens, or post/
   page content.
 * **Legal basis:** legitimate interest in site monitoring and security (LGPD Art.
   7º IX / GDPR Art. 6(1)(f)). The site owner is the data controller; disclosure
   guidance is at https://sitedoctor.syswp.pro.

#### WordPress.org core checksums (optional, on by default)

 * **Service:** api.wordpress.org — the official WordPress.org service, the same
   one WordPress core uses for updates and checksums.
 * **When:** only when the Site Doctor service requests a core integrity check, 
   and only while the **“Check core file integrity against WordPress.org”** option
   is enabled under Settings  SysDoctor. It is on by default; turn it off to keep
   this site fully outbound-free.
 * **What is sent:** your WordPress version and locale, to fetch the official core
   file checksums. No site data, credentials or content is sent. The plugin then
   compares your core files locally and reports which ones differ from the official
   release.
 * Terms: https://wordpress.org/about/privacy/ (WordPress.org).

#### Service links

 * Service URL: https://sitedoctor.syswp.pro
 * Privacy policy: https://sitedoctor.syswp.pro/privacy
 * Terms of service: https://sitedoctor.syswp.pro/terms

Updates to this plugin are delivered through WordPress.org, not from the Site Doctor
service. You can stop all monitoring at any time from **Settings  SysDoctor  Disconnect**,
or by deactivating the plugin.

## Screenshots

[⌊Settings → SysDoctor — paste your connection key to connect the site (read-only).⌉⌊
Settings → SysDoctor — paste your connection key to connect the site (read-only)
.⌉[

Settings  SysDoctor — paste your connection key to connect the site (read-only).

[⌊Settings → SysDoctor — connected. The site responds to the Site Doctor service
read-only; disconnect at any time.⌉⌊Settings → SysDoctor — connected. The site responds
to the Site Doctor service read-only; disconnect at any time.⌉[

Settings  SysDoctor — connected. The site responds to the Site Doctor service read-
only; disconnect at any time.

## Installation

 1. Install the plugin via **Plugins  Add New  Search “SysDoctor”**, or upload the `.
    zip` through **Plugins  Add New  Upload Plugin**.
 2. Activate the plugin in **Plugins**.
 3. Go to **Settings  SysDoctor**.
 4. Paste the **connection key** shown in your Site Doctor dashboard at https://sitedoctor.
    syswp.pro.
 5. Save. The site is now connected and read-only monitoring begins. You can disconnect
    at any time from the same screen.

Don’t have an account yet? Create one free at https://sitedoctor.syswp.pro — add
your site and the dashboard shows your connection key.

## FAQ

### Is it really read-only?

Toward your site, yes. It never modifies your content, files, themes or settings—
no fixes, cleanups, file edits or auto-login. You apply any change yourself, from
your own wp-admin. The one thing it writes is its own **security activity log** (
see below), in its own database table — the same as activity-log plugins such as
WP Activity Log or Simple History.

### What is the security activity log?

To put security events on your Site Doctor timeline, the plugin records them to 
its own table (`{prefix}syswp_site_doctor_events`): logins and failed logins, new
or changed administrators, plugin and theme activation/switch, and changes to sensitive
options (site URL, admin email, who can register, default role). It stores **metadata
only** — event type, the actor’s login, an IP, and the object changed — never passwords,
secrets, full email addresses or content. It only records while the site is connected,
and the log is removed when you uninstall the plugin.

### What data leaves my site?

Plugin and theme names and versions, known-vulnerability matches, uptime status,
performance timings, whether WP-Cron runs, and change metadata (what changed and
when). It does **not** send `wp-config` constants, passwords, API keys, or post 
content. The full, itemized list is in the “External services” section below.

### Do I need a Site Doctor account?

Yes. The plugin is a connector; it does nothing until you paste a connection key
from your Site Doctor account. This is the same model as Akismet and other service-
connected plugins.

### Does it slow down my site?

No. The plugin makes no outbound calls and runs no background tasks or cron. It 
does nothing on your visitors’ page views; it only responds when the Site Doctor
service sends it a signed request, so there is no added page-load cost.

### How do I stop it / disconnect?

Go to **Settings  SysDoctor** and click Disconnect, or deactivate the plugin. Deleting
the plugin removes its stored settings via the bundled `uninstall.php`.

### Does it work for multiple sites?

Yes. Install it on each site and paste that site’s connection key. All sites then
appear together in your Site Doctor dashboard — built for agencies maintaining many
client sites.

## Reviews

There are no reviews for this plugin.

## Contributors & Developers

“SysDoctor” is open source software. The following people have contributed to this
plugin.

Contributors

 *   [ syswppro ](https://profiles.wordpress.org/syswppro/)

[Translate “SysDoctor” into your language.](https://translate.wordpress.org/projects/wp-plugins/sysdoctor)

### Interested in development?

[Browse the code](https://plugins.trac.wordpress.org/browser/sysdoctor/), check 
out the [SVN repository](https://plugins.svn.wordpress.org/sysdoctor/), or subscribe
to the [development log](https://plugins.trac.wordpress.org/log/sysdoctor/) by [RSS](https://plugins.trac.wordpress.org/log/sysdoctor/?limit=100&mode=stop_on_copy&format=rss).

## Changelog

#### 1.4.0

 * Added a security posture check (XML-RPC, debug flags, registration, file permissions
   and more) and an administrator audit (admin accounts, last login and detected
   2FA plugin). Read-only, metadata only, no outbound call.

#### 1.3.0

 * Added a heuristic malware scan: checks plugin, theme and uploads files for suspicious
   code signatures (eval, obfuscation, webshell markers, PHP files in uploads) and
   reports suspects for review. Read-only, bounded, no outbound call.

#### 1.2.0

 * Added a core file integrity check: compares your WordPress core files to the 
   official api.wordpress.org checksums to spot modified or injected files. Gated
   by a Settings toggle (on by default; turn it off to stay fully outbound-free).
 * Added reporting of available plugin, theme and core updates (read from WordPress’
   own update data; no outbound call).

#### 1.1.0

 * Added a security activity log: records security-relevant events (logins, administrator
   changes, plugin/theme/option changes) to the plugin’s own database table, metadata
   only, so they appear on your Site Doctor timeline. Removed on uninstall.

#### 1.0.2

 * Polished the SysDoctor logo with a neon glow; refreshed the banner and icon.
 * Fixed the version number shown on the Settings screen.

#### 1.0.1

 * Added a “Connect to Site Doctor” button for guided sign-up (pre-fills this site).
 * New SysDoctor logo.
 * Added a “How to use” section with example questions for Doc or your own AI.

#### 1.0.0

 * Initial WordPress.org release. Read-only monitoring connector for the Site Doctor
   service: uptime, vulnerable plugins/themes, performance, WP-Cron and change tracking.
   No write operations.

## Meta

 *  Version **1.4.0**
 *  Last updated **1 hour ago**
 *  Active installations **Fewer than 10**
 *  WordPress version ** 5.6 or higher **
 *  Tested up to **7.1.5**
 *  PHP version ** 7.2 or higher **
 * Tags
 * [maintenance](https://wordpress.org/plugins/tags/maintenance/)[monitoring](https://wordpress.org/plugins/tags/monitoring/)
   [performance](https://wordpress.org/plugins/tags/performance/)[security](https://wordpress.org/plugins/tags/security/)
   [uptime](https://wordpress.org/plugins/tags/uptime/)
 *  [Advanced View](https://wordpress.org/plugins/sysdoctor/advanced/)

## Ratings

No reviews have been submitted yet.

[Your review](https://wordpress.org/support/plugin/sysdoctor/reviews/#new-post)

[See all reviews](https://wordpress.org/support/plugin/sysdoctor/reviews/)

## Contributors

 *   [ syswppro ](https://profiles.wordpress.org/syswppro/)

## Support

Got something to say? Need help?

 [View support forum](https://wordpress.org/support/plugin/sysdoctor/)