PW Feed Readiness Audit for WebMCP provides a local, administrator-initiated static audit of WebMCP implementations delivered by your WordPress pages.<\/p>\n\n
This is an independent PW Feed compatibility and readiness tool. It is not affiliated with, endorsed by, or an official product of the WebMCP project or its maintainers.<\/p>\n\n
The validator reviews:<\/p>\n\n
toolname<\/code>, tooldescription<\/code>, toolparamdescription<\/code>, and toolautosubmit<\/code>.<\/li>\n- Imperative registrations using
document.modelContext.registerTool()<\/code>.<\/li>\n- Required tool contract fields such as name, description, input schema, and execution handler.<\/li>\n
- Deprecated
navigator.modelContext<\/code> usage.<\/li>\n- Recommended name, description, and parameter character budgets.<\/li>\n
- Duplicate names, missing form-control names, semantic labels, and completion paths.<\/li>\n
- Security annotation hints and cross-origin iframe tool delegation.<\/li>\n
- HTTPS and HTTP response readiness.<\/li>\n<\/ul>\n\n
The report includes a readiness score, detailed findings, a tool inventory, clipboard summary, and a downloadable JSON export.<\/p>\n\n
Privacy: page content is processed on your WordPress server. The plugin does not send page content, scan results, or usage data to PW Feed or any third party.<\/p>\n\n
WebMCP is an experimental proposed web standard and may change. This plugin performs static source analysis; it cannot observe tools that appear only after runtime interaction or state changes.<\/p>\n\n
PW Feed also publishes resources for wordpress plugin<\/a> users and Turkish wordpress eklentileri<\/a> users.<\/p>\n\n\n\n- Upload the
pw-feed-readiness-audit<\/code> folder to \/wp-content\/plugins\/<\/code>, or install the ZIP from Plugins > Add New > Upload Plugin.<\/li>\n- Activate PW Feed Readiness Audit for WebMCP<\/strong>.<\/li>\n
- Open PW Feed Readiness Audit for WebMCP<\/strong> in the WordPress admin menu.<\/li>\n
- Enter a public page URL on the same WordPress site and select Run validation<\/strong>.<\/li>\n<\/ol>\n\n\n
\nDoes this plugin add WebMCP tools to my site?<\/h3><\/dt>\nNo. It is a validator and does not change front-end markup or register tools.<\/p><\/dd>\n
Does it send my page source to an external service?<\/h3><\/dt>\nNo. The WordPress server fetches a public same-origin URL and analyzes the returned source locally.<\/p><\/dd>\n
Can it validate tools registered after a click or login?<\/h3><\/dt>\nNot from static source alone. The report clearly identifies this limitation. Runtime-only registrations may not appear in a scan.<\/p><\/dd>\n
Why can I only scan this WordPress site's URLs?<\/h3><\/dt>\nSame-origin restrictions reduce server-side request forgery risk and keep the plugin focused on auditing the site where it is installed.<\/p><\/dd>\n
Is WebMCP a finalized standard?<\/h3><\/dt>\nNo. WebMCP is experimental and under active development. The validator follows current public documentation and should be updated as the proposal evolves.<\/p><\/dd>\n
Is the plugin translation-ready?<\/h3><\/dt>\nYes. English is the source language, and all user-facing strings use the pw-feed-readiness-audit<\/code> text domain. WordPress.org language packs can provide additional languages through Translate.WordPress.org.<\/p><\/dd>\n\n<\/dl>\n\n\n1.0.3<\/h4>\n\n\n- Renamed the plugin to PW Feed Readiness Audit for WebMCP.<\/li>\n
- Changed the directory slug and translation domain to
pw-feed-readiness-audit<\/code>.<\/li>\n- Clarified that the plugin is an independent compatibility tool and is not an official WebMCP project product.<\/li>\n<\/ul>\n\n
1.0.2<\/h4>\n\n\n- Updated the original display name and aligned its directory slug and translation domain.<\/li>\n<\/ul>\n\n
1.0.1<\/h4>\n\n\n- Added the supplied PW logo as an optimized dashboard and compact menu asset.<\/li>\n
- Improved WordPress.org readme metadata and translation documentation.<\/li>\n
- Made the clipboard report template translatable.<\/li>\n<\/ul>\n\n
1.0.0<\/h4>\n\n\n- Initial release.<\/li>\n
- Added declarative and imperative WebMCP static analysis.<\/li>\n
- Added security, quality, accessibility, and deprecation checks.<\/li>\n
- Added JSON export and privacy-first same-origin scanning.<\/li>\n<\/ul>","raw_excerpt":"Audit WordPress pages for declarative and imperative WebMCP tools, quality issues, and current security recommendations.","jetpack_sharing_enabled":true,"_links":{"self":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin\/351748","targetHints":{"allow":["GET"]}}],"collection":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin"}],"about":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/types\/plugin"}],"replies":[{"embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/comments?post=351748"}],"author":[{"embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wporg\/v1\/users\/pwfeedtr"}],"wp:attachment":[{"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/media?parent=351748"}],"wp:term":[{"taxonomy":"plugin_section","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_section?post=351748"},{"taxonomy":"plugin_tags","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_tags?post=351748"},{"taxonomy":"plugin_category","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_category?post=351748"},{"taxonomy":"plugin_contributors","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_contributors?post=351748"},{"taxonomy":"plugin_business_model","embeddable":true,"href":"https:\/\/pcd.wordpress.org\/plugins\/wp-json\/wp\/v2\/plugin_business_model?post=351748"}],"curies":[{"name":"wp","href":"https:\/\/api.w.org\/{rel}","templated":true}]}}