feat(mcp-dist): make ReplyNodes submit-ready for Smithery + correct stale listing claim - #20
Open
replynodes-ai wants to merge 1 commit into
Open
replynodes-ai wants to merge 1 commit into
replynodes-ai wants to merge 1 commit into
Conversation
… stale listing claim - Add deploy: remote block to smithery.yaml pointing at the canonical https://mcp.replynodes.com/mcp so the repo is submit-ready the moment a Smithery auth token is available. The existing stdio startCommand is retained so the primary install path stays unchanged. - Correct README distribution table: Smithery is NOT a live listing (https://smithery.ai/server/@replynodes/mcp returns a 188-byte 404 catch-all page), so mark it 'Not listed (blocked) — see issue #12'. - Add artifacts/issue-12-smithery-submission-evidence.md with full research: Smithery auth blocker evidence, MCP endpoint verification, capability discovery surface, and the one concrete owner action. Co-Authored-By: Hermes Agent (Solar Pro4) <hi@hermes.general>
7 tasks
This file contains hidden or bidirectional Unicode text that may be interpreted or compiled differently than what appears below. To review, open the file in an editor that reveals hidden Unicode characters.
Learn more about bidirectional Unicode characters
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Add this suggestion to a batch that can be applied as a single commit.This suggestion is invalid because no changes were made to the code.Suggestions cannot be applied while the pull request is closed.Suggestions cannot be applied while viewing a subset of changes.Only one suggestion per line can be applied in a batch.Add this suggestion to a batch that can be applied as a single commit.Applying suggestions on deleted lines is not supported.You must change the existing code in this line in order to create a valid suggestion.Outdated suggestions cannot be applied.This suggestion has been applied or marked resolved.Suggestions cannot be applied from pending reviews.Suggestions cannot be applied on multi-line comments.Suggestions cannot be applied while the pull request is queued to merge.Suggestion cannot be applied right now. Please check back later.
Summary
deploy:remote block pointing at the canonicalproduction endpoint
https://mcp.replynodes.com/mcpso the repo issubmit-ready the moment a Smithery auth token is available. The existing
stdio
startCommandis retained — the primary install path (Claude Desktop /Codex / Cursor / Windsurf via
npx -y @replynodes/mcp) is unchanged.—
https://smithery.ai/server/@replynodes/mcpreturns a 188-byte Next.jscatch-all 404 page, not a real server listing. Changed the row to "Not listed
(blocked) — see issue [MCP-DIST-003] Publish ReplyNodes MCP to Smithery #12".
artifacts/issue-12-smithery-submission-evidence.mdwith the fullresearch record.
Closes #12.
Test
smithery.yamlis valid YAML; containsdeploy.type: remoteanddeploy.url: https://mcp.replynodes.com/mcp; existingstartCommandintact.README.mdno longer claims a live Smithery listing.initialize+tools/list(verified live;see evidence artifact).
Smithery submission status (from the evidence artifact)
Research done 2026-09-16 against the live Smithery platform:
PUT /namespaces,PUT /servers/...,PUT /servers/.../releases), CLI (smithery auth loginsmithery mcp publish), and web UI (sign-in gated). All return401 Missing authentication tokenwithout a Smithery session.com.replynodesdoes not exist on Smithery. Servercom.replynodes/mcpdoes not exist.https://mcp.replynodes.com/mcpis live and scan-friendly(
initialize+tools/listboth return 200, no auth required).search, web scraping, brand intelligence, app store, context api for ai agents,
data api for ai agents) all have competitors indexed, confirming the discovery
value once a listing exists.
Blocker: submission requires an owner Smithery account/session (OAuth/login,
possibly CAPTCHA). One concrete owner action is documented in
artifacts/issue-12-smithery-submission-evidence.mdand in issue #12.This PR makes the repo submit-ready; it does not perform the authenticated
submission, which cannot be done headless.
🤖 Generated with Hermes Agent