MCP registry optimization: keyword targeting for official registry, Smithery, Glama, mcp.so

[lbesecker195]

Research across the Official MCP Registry, Smithery, Glama, PulseMCP, mcp.so and
GitHub's own topic system to make the new MCP server rank for relevant searches.
Key finding: the official registry's search only substring-matches the name
field (not description), so the domain-verified namespace string is the single
highest-leverage lever available there.

• Publish under a domain-verified com.seriouslysimpleanalytics/* namespace
  instead of io.github.*, since the domain and /.well-known/mcp-registry-auth
  proof path already exist.
• Add server.json at repo root with a keyword-front-loaded description
  (100-char limit on the official registry) and a remotes entry for the
  Streamable HTTP endpoint.
• Refresh GitHub topics: drop redundant/low-value tags, add mcp, mcp-server,
  model-context-protocol and related ones (~29k repos are tagged
  mcp-server, and this repo had none of the three highest-signal tags).
• Tighten a few MCP tool descriptions and the MCP landing page copy to match
  how competitors (PostHog, Plausible, Amplitude, Mixpanel MCP servers) are
  described on these directories.
• Document the remaining human-required steps (mcp-publisher domain login,
  Smithery/Glama/mcp.so account-bound claims).

---

Pages affected:

• SeriouslySimpleAnalytics -- free, cookieless web analytics with one script tag.
• Analytics MCP Server -- the page this optimization work targets directly.
• AI Analytics (llms.txt) -- usage analytics for AI agents, MCP servers and CLIs.
• Getting Started -- API key creation for MCP clients.
• Integration Guide -- the event API contract served as an MCP resource.