Plugin profile · observed daily since 16 Aug 2026
PW Feed Readiness Audit for WebMCP
PluginsPedia reports published data and observable changes. It does not rate plugin quality or safety, infer intent, or make recommendations. These are observations rather than a verdict. How this works
Ownership
Held by pwfeedtr throughout, with no change of ownership observed since daily tracking began on 16 Aug 2026.
Full observed history, including every field transition
Committing accounts
Read from the plugin’s public release log, so these predate this registry. A committing account is not an owner. Thirty accounts commit to WooCommerce and it has never changed hands.
| Account | Releases | First | Last |
|---|---|---|---|
| pwfeedtr | 1 | 11 Aug 2026 | 11 Aug 2026 |
This registry did not observe a transfer; it read these names off a public log. Whether that reflects a change of ownership is not something the directory publishes.
Adoption
How widely the plugin is installed, and what the people running it think of it. WordPress.org rounds install figures to one significant digit, so they describe an order of magnitude rather than a headcount.
Very early-stage: fewer than 10 active installs. Too few installs to read anything into adoption. That is a gap in the evidence, not a mark against the plugin.
2 downloads a day over the last 7 days, steady against the 7 days before. Downloads are counted exactly and without a ceiling, so they show movement the rounded install figure cannot.
Daily record
Every field we record, one column per observation. Fields that never moved are named once rather than repeated across every column. A row of identical numbers would be padding.
| Field | 18 Oct | 19 Oct | 20 Oct | 21 Oct | 22 Oct | 23 Oct | 24 Oct | 25 Oct | 26 Oct | 27 Oct | 28 Oct | 29 Oct | 30 Oct | 31 Oct |
|---|---|---|---|---|---|---|---|---|---|---|---|---|---|---|
| Downloads that day | — | 0 | 11 | 0 | 0 | 0 | 0 | 0 | 11 | 0 | 0 | 0 | 0 | 0 |
Unchanged throughout: ratings total (0) · active installs (0+) · version (1.0.3) · support threads (0) · threads resolved (0)
77 days of observation, most recent 14 shown.
Maintenance
When it was last released, and how far its declared compatibility has drifted from current WordPress.
Is anyone still maintaining this?
- Last released 11 Aug 2026, 89 days ago.
- Declares compatibility only up to WordPress 7.0.8, while 7.1 is current. The author has not confirmed it runs on the last 1 release.
- The same account maintains 2 other plugins; the most recent update to any of them was 06 Aug 2026.
A plugin that does one thing correctly may need no changes for years; a long gap is not, by itself, evidence of neglect.
History
Everything dated that this registry holds about the plugin, most recent first. Releases carry the author’s own release date; everything else is dated to when it was observed.
- 16 Aug 20263 months agoFirst observed by PluginsPediaDaily snapshots of this plugin’s directory record begin here. Everything above this line is observed; anything before it comes from fields the API itself reports.
- 11 Aug 20263 months agoVersion 1.0.3 released
- 11 Aug 20263 months agoAdded to the WordPress.org directoryReported by the plugin API as the date this plugin was added.
What we know, and what we don’t
Everything on this page in one place, including the gaps, so that nothing here is mistaken for a clean bill of health.
What we know
- It has been held by pwfeedtr for all 77 days we have observed it.
- It was last released 3 months ago (11 Aug 2026).
- Its author declares it tested up to WordPress 7.0.8; WordPress is now on 7.1.
- WordPress.org reports fewer than 10 active installs.
What we don’t know yet
- Nobody has rated it. The first rating that arrives shows up here.
- No forum threads were open in the two months we measure, so how responsive its support is cannot be said. One new thread starts answering that.
Every record on this site, this one included, works under the same limits. We read what WordPress.org publishes about a plugin, never the plugin’s own code, so nothing here says whether a plugin is well built or safe. Install counts reach us already rounded; a change smaller than a band step doesn’t show. We don’t track security advisories yet. For anything older than our first observation we rely on the plugin’s public release log, where one exists. What this registry can and cannot see
Similar plugins
Plugins that share this one’s tags and talk about the same things in their own descriptions. Distinctive tags count for far more than broad ones. Sharing hover means something, sharing woocommerce does not, and a plugin that never mentions the subject matter is left out however its author tagged it. Among close matches, more widely installed plugins are listed first. This is a grouping rather than a ranking of quality.
Owner-controlled AI access to your public content: llms.txt, a read-only MCP endpoint, and opt-in WebMCP tools for agents in the browser.
Make your WordPress site natively AI-agent friendly via WebMCP, REST/OpenAPI, and a remote MCP endpoint for Claude.
Publish WordPress content, forms and WooCommerce tools for AI agents through MCP and WebMCP, with owner review and approval for changes.
Add privacy-first WebMCP tools, diagnostics, and live testing for WordPress and WooCommerce AI-agent workflows.
Audit whether a WordPress site is discoverable, understandable, and safely operable by AI agents, with evidence for every finding.
Prepare WordPress for AI agents with an agentic readiness dashboard, llms.txt, WebMCP-style form metadata, read-only discovery tools, accessibility ch …
Grouped from the tags each author chose for their own plugin, so the grouping is only as good as those tags.
Reach out about this record
Corrections, missing context, or anything else about PW Feed Readiness Audit for WebMCP: a person reads every submission, and corrections get a reply within 5 business days.