%s
. */
__( 'The wpb-access-control library (%s) is not loaded. Per-server MCP access-control rules are inactive and all tool calls will pass (fail-open). Install or activate the library to enforce saved rules.', 'acrossai-mcp-manager' ),
'WPBoilerplate\\AccessControl\\AccessControlManager'
),
'type' => 'warning',
'source' => __( 'MCP Manager', 'acrossai-mcp-manager' ),
);
}
if ( (bool) get_option( 'acrossai_mcp_npm_login_enabled', false ) ) {
$auth_url = \AcrossAI_MCP_Manager\Public\Partials\FrontendAuth::get_base_url();
$notices[] = array(
'id' => 'acrossai_mcp_manager_cli_auth_cache_exclusion',
'title' => __( 'Exclude CLI auth URL from page cache', 'acrossai-mcp-manager' ),
'message' => sprintf(
/* translators: %s: the frontend CLI authorization URL, wrapped in . */
__( 'The npm / npx CLI connection flow is enabled. The frontend authorization page at %s contains time-sensitive auth codes and nonces. If your hosting, CDN, or caching plugin caches this URL, authentication will silently fail. Exclude this path from all page-caching rules.', 'acrossai-mcp-manager' ),
'' . esc_url( $auth_url ) . ''
),
'type' => 'warning',
'source' => __( 'MCP Manager', 'acrossai-mcp-manager' ),
);
}
// ── F095: OAuth operational warnings ────────────────────────────────
// Ported from the companion. Each is a soft warning about a hosting
// condition that silently degrades OAuth rather than breaking it
// loudly — which is exactly the kind of failure an operator will not
// otherwise connect back to this plugin.
if ( ! is_ssl() && ! ( defined( 'FORCE_SSL_ADMIN' ) && \FORCE_SSL_ADMIN ) ) {
$notices[] = array(
'id' => 'acrossai_mcp_manager_oauth_https_missing',
'title' => __( 'HTTPS is not configured', 'acrossai-mcp-manager' ),
'message' => __( 'OAuth tokens will be issued over plaintext HTTP — passive network attackers can intercept them. Configure SSL / FORCE_SSL_ADMIN before exposing the OAuth endpoints to production traffic.', 'acrossai-mcp-manager' ),
'type' => 'warning',
'source' => __( 'Connectors/Integrations', 'acrossai-mcp-manager' ),
);
}
// Gated on there being something to clean (#56). DISABLE_WP_CRON is the
// default in Local by Flywheel, WP Studio and most CI images, so on a
// development site with no OAuth clients this notice fired on every
// admin page load, forever, to report that a no-op would not run
// automatically. A permanent warning about nothing is how an operator
// learns to stop reading our notices — including the ones that matter.
//
// Sites with real OAuth state still get it: there, the rows genuinely
// accumulate. The Troubleshoot screen reports the same condition on
// demand either way, with the count.
if ( defined( 'DISABLE_WP_CRON' ) && true === \DISABLE_WP_CRON && self::has_oauth_data() ) {
$notices[] = array(
'id' => 'acrossai_mcp_manager_wp_cron_disabled',
'title' => __( 'WP-Cron is disabled', 'acrossai-mcp-manager' ),
'message' => __( 'DISABLE_WP_CRON=true prevents the daily OAuth cleanup from running automatically — expired access tokens and auth codes will accumulate. Either remove the DISABLE_WP_CRON constant, or configure a real cron entry to run wp cron event run acrossai_mcp_manager_oauth_cleanup daily.', 'acrossai-mcp-manager' ),
'type' => 'warning',
'source' => __( 'Connectors/Integrations', 'acrossai-mcp-manager' ),
);
}
// Wordfence per-IP throttling silently rate-limits bursty MCP polling
// and OAuth token exchanges. Any of the three knobs set to something
// other than DISABLED is enough.
if ( class_exists( '\\wfConfig' ) ) {
foreach ( array( 'maxGlobalRequests', 'maxRequestsHumans', 'maxRequestsCrawlers' ) as $wf_key ) {
$wf_val = \wfConfig::get( $wf_key, 'DISABLED' );
if ( 'DISABLED' !== $wf_val && '' !== $wf_val ) {
$notices[] = array(
'id' => 'acrossai_mcp_manager_wordfence_rate_limit_enabled',
'title' => __( 'Wordfence rate limiting may throttle Connectors traffic', 'acrossai-mcp-manager' ),
'message' => __( 'Wordfence per-IP rate limiting is enabled and can silently throttle bursty MCP polling from AI assistants plus OAuth token exchanges. Add /wp-json/mcp/* and /wp-json/acrossai-mcp-manager/v1/oauth/* under Wordfence → Firewall → Rate Limiting → Whitelisted URLs. Dismiss this notice once configured.', 'acrossai-mcp-manager' ),
'type' => 'warning',
'source' => __( 'Connectors/Integrations', 'acrossai-mcp-manager' ),
);
break;
}
}
}
// Full-page caches serve stale OAuth responses, which carry
// per-request nonces, client_ids and bearer tokens. CacheHeaders sends
// no-store on those responses and most caches respect it; excluding
// the paths outright is the belt-and-braces posture. WP_CACHE is the
// reliable signal — core only loads advanced-cache.php when it is
// truthy, so every plugin-based cache sets it. Edge and host caches
// cannot be detected this way and are covered in the docs instead.
if ( defined( 'WP_CACHE' ) && true === \WP_CACHE ) {
$notices[] = array(
'id' => 'acrossai_mcp_manager_page_cache_exclusions_required',
'title' => __( 'Page cache detected — exclude OAuth + REST URLs', 'acrossai-mcp-manager' ),
'message' => __( 'A full-page cache is enabled on this site (WP_CACHE=true). MCP and OAuth responses carry per-request state (nonces, client_ids, bearer tokens) and MUST NOT be served from cache. Add /wp-json/* and /.well-known/* to your cache plugin\'s do-not-cache list. Dismiss this notice once configured.', 'acrossai-mcp-manager' ),
'type' => 'warning',
'source' => __( 'Connectors/Integrations', 'acrossai-mcp-manager' ),
);
}
// A competing OAuth discovery implementation claims the same
// .well-known URLs. DiscoveryConflictGuard disables it; this explains
// why, because the symptom otherwise looks like our bug.
if ( \AcrossAI_MCP_Manager\Includes\OAuth\DiscoveryConflictGuard::conflict_detected() ) {
$conflict_source = \AcrossAI_MCP_Manager\Includes\OAuth\DiscoveryConflictGuard::conflicting_plugin_name();
if ( '' === $conflict_source ) {
$conflict_source = __( 'Another active plugin', 'acrossai-mcp-manager' );
}
$notices[] = array(
'id' => 'acrossai_mcp_manager_oauth_discovery_conflict',
'title' => __( 'Another plugin also serves OAuth discovery', 'acrossai-mcp-manager' ),
'message' => sprintf(
/* translators: %s: name of the conflicting plugin. */
__( '%s bundles its own MCP OAuth server, which claims the same /.well-known/oauth-protected-resource and /.well-known/oauth-authorization-server URLs. Its documents advertise a single hardcoded server and no registration_endpoint, so AI assistants could not register against your MCP servers. This plugin has taken discovery back. To opt out, add add_filter( \'acrossai_mcp_manager_take_over_oauth_discovery\', \'__return_false\' );.', 'acrossai-mcp-manager' ),
$conflict_source
),
'type' => 'warning',
'source' => __( 'Connectors/Integrations', 'acrossai-mcp-manager' ),
);
}
// Firefox Enhanced Tracking Protection. Confirmed in the field
// (salon.hvacb.com, 2026-09-11): adding a custom connector in Claude
// failed repeatedly in Firefox and succeeded immediately once
// protections were switched off for the site. ETP partitions and
// blocks cross-site state, and the connector handshake crosses
// between the assistant's origin and this one, so the sign-in can be
// dropped part-way with no error either side can show.
//
// Registered only for the browser affected, and keyed off the request
// rather than anything stored: the same administrator switching to
// Chrome should not keep seeing it. The shared renderer dismisses by
// a fingerprint of the registered ids, so a Firefox-only entry never
// disturbs what another browser's session has already dismissed.
//
// Adopted from acrossai-pro 0.9.16 when the connector stack moved
// here: the condition it reports is a property of connecting an
// assistant, which is this plugin's feature now.
if ( self::is_firefox() ) {
$notices[] = array(
'id' => 'acrossai_mcp_manager_firefox_tracking_protection',
'title' => __( 'Firefox tracking protection can block AI assistants from connecting', 'acrossai-mcp-manager' ),
'message' => __( 'You are viewing this page in Firefox. Its Enhanced Tracking Protection can stop an AI assistant part-way through connecting to this site — the connector is added, sign-in opens, and then nothing completes, usually with no error to explain it.
If a connection fails: click the shield icon to the left of the address bar, then switch Enhanced Tracking Protection off for this site and connect again. Firefox remembers the choice per site and it does not affect any other site you visit. You can switch it back on afterwards — the protection only interferes while the connection is being set up, not once it is working.', 'acrossai-mcp-manager' ),
'type' => 'info',
'source' => __( 'Connectors/Integrations', 'acrossai-mcp-manager' ),
);
}
return $notices;
}
/**
* Whether the CURRENT REQUEST comes from Firefox or a Firefox-derived
* browser.
*
* Deliberately a request-scoped check on the User-Agent rather than
* anything persisted. The condition being reported is a property of the
* browser reading the page, not of the site, so it has to be re-evaluated
* per request — the same administrator on Chrome must not see it.
*
* Matches Firefox on desktop and Android (`Firefox/`), Firefox on iOS
* (`FxiOS/`, a WebKit shell that still ships ETP), and the Gecko forks
* that inherit the same protection stack — LibreWolf and Waterfox both
* keep `Firefox/` in their User-Agent. SeaMonkey carries `Firefox/` in
* some builds without shipping ETP, so it is excluded.
*
* A spoofed or absent User-Agent simply means no notice. That is the
* right failure direction: this is advisory, it costs nothing to miss,
* and showing it to someone who is not in Firefox would be confusing.
*
* @param string|null $user_agent Override for tests. Defaults to the
* current request's User-Agent.
* @return bool
*/
public static function is_firefox( ?string $user_agent = null ): bool {
if ( null === $user_agent ) {
// phpcs:ignore WordPress.Security.NonceVerification.Recommended -- Read-only browser sniff for an advisory notice.
$user_agent = isset( $_SERVER['HTTP_USER_AGENT'] )
? sanitize_text_field( wp_unslash( $_SERVER['HTTP_USER_AGENT'] ) )
: '';
}
if ( '' === $user_agent ) {
return false;
}
if ( false !== stripos( $user_agent, 'Seamonkey/' ) ) {
return false;
}
return ( false !== stripos( $user_agent, 'Firefox/' ) )
|| ( false !== stripos( $user_agent, 'FxiOS/' ) );
}
/**
* Does this site hold any OAuth state the daily cleanup would act on?
*
* Memoized for the request: this runs on every admin page load, and the
* answer cannot change within one.
*
* Counts are capped at one row per table — the question is existence, and
* the notice does not quote a number. The Troubleshoot screen's
* `wp_cron` check does quote one, and counts properly for that reason.
*
* @return bool
*/
private static function has_oauth_data(): bool {
static $has = null;
if ( null !== $has ) {
return $has;
}
$has = false;
$queries = array(
'\\AcrossAI_MCP_Manager\\Includes\\Database\\OAuthClients\\Query',
'\\AcrossAI_MCP_Manager\\Includes\\Database\\OAuthTokens\\Query',
'\\AcrossAI_MCP_Manager\\Includes\\Database\\OAuthAuthCodes\\Query',
);
foreach ( $queries as $query_class ) {
if ( ! class_exists( $query_class ) ) {
continue;
}
$rows = $query_class::instance()->query(
array(
'number' => 1,
'fields' => 'ids',
)
);
if ( ! empty( $rows ) ) {
$has = true;
break;
}
}
return $has;
}
}