Unblock: Glama listing blocked — holding up awesome-mcp-servers PR

[bmdhodl]

Summary

AgentGuard47's Glama listing is blocked, which is holding up the awesome-mcp-servers PR. Both are 90-day milestones (by June 25, 2026).

Target registries:

• ✅ MCP Official Registry — LIVE (io.github.bmdhodl/agentguard47, confirmed April 2)
• ❌ Glama — blocked (root cause: Smithery/Docker metadata issue)
• ❌ awesome-mcp-servers — PR open, waiting on Glama badge before merge

What's blocking Glama

Glama requires Smithery/Docker metadata in the repo root and/or package. The metadata was set up but the Glama badge is still not being issued. Root cause unclear — needs direct investigation on the Glama submission page.

Investigation steps

1. Go to glama.ai and check the submission status for agentguard47
2. Review what metadata Glama specifically requires (check their docs)
3. Inspect the repo root and pyproject.toml / setup.py for missing Smithery/Docker fields
4. Re-submit or update the listing if needed
5. Once Glama badge is live, unblock the awesome-mcp-servers PR

Why this matters

• Distribution: Glama + awesome-mcp-servers are high-traffic discovery surfaces for Python devs
• Downloads: 6,400+ PyPI downloads already — a Glama listing accelerates this
• Credibility: being listed validates AgentGuard as a production-grade MCP tool

Kill criteria

Glama badge appears on the AgentGuard repo README. awesome-mcp-servers PR merged.