Status is the screen to open when something is not working. It runs a set of checks against your actual install and reports what passed, what failed and what to do about each failure.
Most connection problems come from a small number of causes: the endpoint is not reachable, the account is not enabled, the token has expired, a permalink rewrite has not flushed, or a security plugin is blocking REST requests. Status checks those directly rather than leaving you to reason about them.
Open NIBWP and go to Status. Anything failing is listed with the reason and the fix. Start there before you start guessing.
Answers, not symptoms
A diagnostic screen is worth having because the symptoms all look the same:
- One place to look — Endpoint, authentication, access, permalinks and environment in a single view.
- Real checks — Each one runs against this install, not against a general idea of a healthy site.
- Named fixes — A failure says what to do, not only that something is wrong.
- Before you file a ticket — Most problems answer themselves here, and the ones that do not are easier to describe.
- After an upgrade — A quick way to confirm nothing shifted when WordPress or a plugin updated.
- Safe to run — Every check reads. Nothing on this screen changes your site.
What a failure looks like
A failed check names the cause and the fix:
Status · 21 checks
✓ endpoint reachable
✓ REST API responding
✗ account not enabled for NIBWP
Fix: NIBWP → User Access → enable this account
✓ permalinks flushedThat is usually the whole diagnosis. The account was never switched on, and nothing else was ever wrong.
What it checks
The checks group into a few areas:
Connection
That the MCP endpoint resolves, answers, and is reachable over HTTPS.
Authentication
That credentials are present and valid, and that tokens have not expired.
Access and scopes
That the account is enabled for NIBWP and holds the scopes it is trying to use.
Environment
PHP version, REST availability, permalinks, and plugins known to block requests.
How it stays safe
- Read only — Every check reads. None of them changes a setting or writes content.
- No secrets shown — It reports whether credentials are valid, not what they are.
- Safe to share — A screenshot of Status can be sent to support without leaking a token.
Getting started
- Open Status — In WordPress, go to NIBWP and open Status.
- Read the failures first — Passing checks are reassuring; the failing ones are the answer.
- Fix and re-run — The checks are cheap, so re-run after each change.
- Then look at the audit log — If Status is clean and something still misbehaves, the log shows what was actually called.