Refresh external listings after the repository transfer #16

Summary

The server has meaningful external awareness, but most directory listings still use the repository's former owner, stale documentation, or mirrored metadata. We should establish one canonical listing and update the highest-visibility references after the transfer to WordPress/trac-mcp.

Findings

• PulseMCP lists the server under James LePage and says its server.json is a temporary mirror. It estimates 1.9k visitors, including 189 during the week checked.
• Glama points to the live Worker but retains the old repository owner, outdated README, and outdated capability claims.
• Binate Thoughts demonstrated the server for WordPress triage.
• Skywork published a detailed review.
• courtneyr-dev/meta-trac adapted the project for seven WordPress Trac instances. The derivative appears on MCP.Directory and MCP Market.
• GitHub traffic for the 14 days checked showed 40 views from 15 unique visitors and 36 clones from 20 unique cloners.
• Public GitHub code search did not yet find references using the transferred repository URL or the exact Worker hostname.

Tasks

• Add and validate canonical server metadata for the official MCP registry.
• Publish the canonical metadata so directories no longer need to mirror it.
• Claim or update the PulseMCP listing with the current owner, repository, endpoint, and capabilities. (Deferred for now.)
• Claim or update the Glama listing and remove stale claims such as caching and unsupported query forms.
• Review the DXT listing for the same ownership and documentation drift.
• Ask the meta-trac derivative to link to the current upstream repository if it still points to the former owner.
• Add a short directory/discovery section to the README once canonical listings are current.
• Re-run web and GitHub code searches after the updates have been indexed.

Success criteria

• External listings identify WordPress/trac-mcp as the canonical upstream.
• Published endpoints and tool behavior match the current README and schemas.
• One maintainer-controlled metadata source feeds future directory updates.