[Growth] List WorldMonitor MCP server in major MCP and AI plugin directories

## Summary

Submit the WorldMonitor MCP server to the major MCP registries and AI-client plugin directories so users can discover and connect it without finding the endpoint manually.

Canonical product server:

- Endpoint: `https://worldmonitor.app/mcp`
- Transport: Streamable HTTP
- Server card: `https://worldmonitor.app/.well-known/mcp/server-card.json`
- Documentation: `https://www.worldmonitor.app/docs/mcp-overview`
- Discovery is public; data-bearing calls require OAuth 2.1 with `scope=mcp` or an API key.

## Directories

- [ ] `registry.modelcontextprotocol.io`
- [ ] `platform.openai.com/plugins`
- [ ] `platform.claude.com/plugins`
- [ ] `cursor.directory`
- [ ] `mcpservers.org`
- [ ] `pulsemcp.com`
- [ ] `smithery.ai`
- [ ] `glama.ai`

## Submission work

For each directory:

1. Confirm its current submission format, ownership-verification requirements, review process, and whether remote Streamable HTTP servers are supported.
2. Reuse the canonical name, description, endpoint, auth model, documentation URL, logo, and repository metadata wherever the directory supports them.
3. Add or adapt any required manifest/configuration in this repository, keeping generated directory-specific metadata consistent with the live server card.
4. Validate anonymous discovery and OAuth connection from the directory or client before marking it complete.
5. Record the public listing URL, submission/review status, and any follow-up owner in this issue.

## Acceptance criteria

- WorldMonitor has a submitted or published entry in all eight directories above.
- Every published entry points to the canonical production endpoint and accurately describes Streamable HTTP plus OAuth/API-key authentication.
- Public listing URLs are recorded in this issue.
- Any directory that cannot accept the server has a documented blocker, evidence, owner, and next action rather than being silently checked off.
- The final pass verifies that directory metadata does not promise anonymous data access; only discovery/catalog operations are anonymous.

Start with the canonical server card, MCP documentation, and production endpoint listed in the issue, then review the submission requirements for each of the eight directories. Confirm support for remote Streamable HTTP, OAuth 2.1, and anonymous discovery before submitting. Done means every directory has a published or submitted listing, recorded URL and status, or documented blocker with an owner and next action.

Written by the indexing model from the issue text.