[MCP-DIST-001] Publish ReplyNodes MCP to Glama

[replynodes-ai]

Parent Epic: #8

Goal

Publish and verify ReplyNodes MCP on Glama end-to-end so developers and AI agents can discover ReplyNodes by capability, not only by brand name.

Canonical inputs

• Production MCP endpoint: https://mcp.replynodes.com/mcp
• Repository: https://github.com/replynodes/replynodes-mcp
• Official Registry namespace: com.replynodes/mcp

Required work

1. Research Glama's current MCP submission and ownership-claim process first.
2. Submit ReplyNodes using the best supported listing type for a production remote MCP server.
3. Use the existing public GitHub repo where required.
4. Claim/verify ownership where supported.
5. Complete all useful metadata, categories, tags, links, and install/connect instructions.
6. Optimize metadata for capability discovery, including relevant terms such as:
   • web search MCP
   • web scraping MCP
   • website crawl MCP
   • Reddit MCP
   • YouTube MCP
   • App Store MCP
   • brand intelligence MCP
   • public web data MCP
   • context API for AI agents
7. Run Glama health/security checks if available.
8. Fix reasonable repo/listing metadata issues that block publication.
9. Verify the public listing is live.
10. Test Glama search using multiple non-brand capability queries, not only ReplyNodes.
11. Record the final public Glama listing URL and verification evidence in this issue.

Base description

Use/adapt this where appropriate:

ReplyNodes is a read-only MCP server for AI agents that provides Web Search, Web Scraping, Website Crawling, Reddit, YouTube, App Store, Brand Intelligence, and other public web/data APIs through one MCP endpoint.

Do not invent capabilities that are not live in production.

Agent autonomy

Complete all actions autonomously using available browser/GitHub access. Only ask the owner when Glama requires an action that cannot reasonably be delegated, such as:

• OAuth/login approval
• CAPTCHA
• DNS verification
• account ownership confirmation
• organization-owner permission

When blocked, ask for exactly one concrete owner action and then continue.

Definition of Done

• Public Glama listing exists
• Listing points to the correct production MCP/repository
• Ownership is claimed/verified where supported
• Relevant metadata/categories/tags are complete
• Health/security checks pass, or non-blocking warnings are documented
• Listing has been tested with non-brand capability searches
• Final Glama URL is posted in this issue

Do not mark complete merely because the submission form was sent. Completion requires verifying the live Glama listing.