WPVibes

Gajendra Singh

<p>MCP Tracker is an admin-only WordPress plugin designed to monitor and log MCP (Model Context Protocol) requests made to the Abilities API on your WordPress site.<br />
If you are using the Abilities API to power AI-driven tools or MCP-based integrations, MCP Tracker gives you complete visibility into how those tools interact with your REST endpoints â€” without modifying or interfering with request flow.<br />
The plugin automatically detects MCP requests (identified via the <code>Mcp-Session-Id</code> header), records detailed request and response data, and presents everything in a structured, filterable interface inside WordPress Admin.<br />
Whether you’re debugging Abilities API integrations, auditing MCP tool usage, or analyzing response behavior, MCP Tracker provides the observability layer you need.</p>
<h4>Features</h4>
<ul>
<li><strong>Automatic MCP Detection</strong><br />
Identifies MCP requests related to Abilities API using the <code>Mcp-Session-Id</code> header.</li>
<li><strong>Comprehensive Logging</strong><br />
Logs route, method, headers, request payload, response status, and response body.</li>
<li><strong>User Attribution</strong><br />
Displays which WordPress user (or guest) initiated the MCP request.</li>
<li><strong>Advanced Filtering</strong><br />
Filter logs by date range, tool name, and user for targeted analysis.</li>
<li><strong>Formatted JSON Inspection</strong><br />
View complete request and response data in a structured format.</li>
<li><strong>Privacy Focused</strong><br />
All logs remain stored in your WordPress database. No external transmission or telemetry.</li>
<li><strong>Performance Optimized</strong><br />
Efficient logging using native WordPress REST hooks and optimized queries.</li>
</ul>
<h4>Use Cases</h4>
<ul>
<li>Debug Abilities API integrations  </li>
<li>Monitor MCP-based AI tool usage  </li>
<li>Analyze REST response patterns  </li>
<li>Audit MCP activity on production sites  </li>
<li>Investigate failed or unexpected tool executions  </li>
</ul>
<h4>Technical Details</h4>
<ul>
<li>Uses WordPress REST API hooks for non-intrusive logging  </li>
<li>Custom indexed database table for efficient storage  </li>
<li>Admin-only access with capability checks  </li>
<li>Nonce verification for secure actions  </li>
<li>Prepared SQL statements for database safety  </li>
<li>Self-healing table creation on activation</li>
</ul>


MCP Tracker


I love to use this plugin when working or building something around MCP. It a great an light weight plugin to track your MCP request 


Simple but an effective one

Records and displays MCP-related REST API requests made to your WordPress site.

Pedro Matias

<p><strong>Modules Insight</strong> helps WordPress developers and site managers audit installed plugins, assess the risk of upgrading PHP, and export complete reports — all from a single on-demand scan.</p>
<h3>PHP Upgrade Risk Evaluator</h3>
<p>Planning a server PHP upgrade? MI queries the <strong>WordPress.org API</strong> for each installed plugin and produces a colour-coded risk table showing how likely each plugin is to break on your target PHP version.</p>
<p>Each plugin is rated <strong>Low</strong>, <strong>Medium</strong>, <strong>High</strong>, or <strong>Not on WP.org</strong> based on two signals:</p>
<p><strong>1. Last Updated</strong> — how recently the plugin received a release on WordPress.org.<br />
<strong>2. Minimum PHP Declared</strong> — the <code>Requires PHP</code> field set by the plugin author.</p>
<p>Risk is assigned as follows:</p>
<ul>
<li><strong>High</strong> — Not updated in over 3 years, or declares a minimum PHP below 7.0. These carry the greatest risk of breaking on PHP 8.x and should be investigated before upgrading.</li>
<li><strong>Medium</strong> — Falls between High and Low. Test on a staging environment before upgrading production.</li>
<li><strong>Low</strong> — Updated within the last 12–18 months and declares PHP 7.4 or higher as its minimum. Likely compatible, but a quick smoke test after upgrading is still recommended.</li>
<li><strong>Not on WP.org</strong> — Not found in the WordPress.org directory (premium plugins, custom code). Compatibility must be verified manually with the vendor.</li>
</ul>
<p><strong>Important:</strong> risk ratings are based on publicly available metadata, not code analysis. A Low-rated plugin could still have incompatibilities; a High-rated plugin might work perfectly. Use the table as a triage guide, not a guarantee. Always test on a staging environment before upgrading PHP on a live server.</p>
<p>Results from the WordPress.org API are cached per plugin for 24 hours to avoid unnecessary external requests.</p>
<h3>Plugin List and Reports</h3>
<p>MI lists all installed plugins (active, inactive, and network-active on multisite) with version numbers, author details, and descriptions. It also reports the active WordPress version and active theme.</p>
<p>Reports can be exported as <code>.json</code> or <code>.csv</code>. Both formats include the PHP compatibility data if a check has been run prior to export.</p>
<p>Tested and fully compatible with <strong>WordPress 7.0</strong>.</p>
<h3>Key Features</h3>
<ul>
<li>PHP upgrade risk evaluation via the WordPress.org API</li>
<li>Colour-coded risk table: Low / Medium / High / Not on WP.org</li>
<li>Lists all installed plugins with status, version, author, and URIs</li>
<li>Reports WordPress version and active theme</li>
<li>Export as JSON or CSV (includes compat data when available)</li>
<li>Dashboard widget and <code>[plugin_list]</code> shortcode</li>
<li>Scan-on-demand — nothing runs automatically on page load</li>
<li>100% read-only — safe for production use</li>
</ul>
<h3>Use Cases</h3>
<ul>
<li>Assessing risk before upgrading PHP on a server</li>
<li>Managing multiple WordPress sites and keeping plugins audited</li>
<li>Client-facing reports on installed plugins</li>
<li>Pre-deployment or pre-update plugin audits</li>
</ul>
<h3>Credits</h3>
<p>Made with ❤️ by Pedro Matias for WordPress developers and admins.</p>


Modules Insight

Audit installed plugins, assess PHP upgrade risk via the WordPress.org API, and export full reports as JSON or CSV.

MCP Tracker vs Modules Insight