Publish to MCP directories: MCP Registry, Smithery, Glama, PulseMCP

[seokmogu]

Goal

Publish vessel-traffic-mcp to public MCP discovery surfaces after the release gate is clean.

Surfaces

• Official MCP Registry
• Smithery
• Glama
• PulseMCP / MCPServers / awesome-MCP style lists

Starting points

• server.json contains MCP Registry metadata for io.github.tools-mcp/vessel-traffic-mcp.
• glama.json contains Glama maintainer metadata using the tools-mcp organization identity.
• docs/runbooks/public-sharing.md contains the launch checklist and listing copy.

Safety boundary

Do not upload .env, credential profiles, API keys, cookies, HAR files, raw captures, browser sessions, or provider secrets. Keep npm publication blocked until maintainers explicitly approve flipping package.json#private.

[seokmogu]

Status update: README now has a top-level Public Access / 배포 상태 section in 384a0d0. MCP Registry metadata validates with mcp-publisher validate server.json. npm package name is available, but publication is blocked on npm auth on this machine (npm whoami => ENEEDAUTH). Next operator step: run npm adduser, then decide whether to flip package.json private guard and publish the package before MCP Registry submission.

[seokmogu]

Update 2026-05-19:

• npm login now works locally (npm whoami returns seokmogu).
• package.json is publication-ready: private removed, publishConfig.access=public, and prepublishOnly runs lint/test/build.
• Verification passed before push: git diff --check, npm run lint, npm run build, npm test (840 tests, 838 pass, 2 skipped), npm pack --dry-run, and mcp-publisher validate server.json.
• Commit pushed: 83a6856 Prepare npm publication metadata.

Remaining blocker before npm publish: publishing the unscoped vessel-traffic-mcp package under the current npm login will likely expose that npm username as a public maintainer. Decide whether to publish as-is or first create/use an npm org/scope such as @tools-mcp.

[seokmogu]

Update 2026-05-19:

• Switched npm package metadata to the organization scope: @tools-mcp/vessel-traffic-mcp.
• Updated server.json package identifier to the same scoped npm package.
• Updated README/runbooks/tests so future publication and MCP Registry submission use the npm tools-mcp org scope.
• Verification passed: git diff --check, tmp/bin/mcp-publisher validate server.json, npm pack --dry-run, npm run lint, npm run build, and npm test (840 tests, 838 pass, 2 skipped).
• Commit pushed: 35ccb6e Switch npm package to tools-mcp scope.

Remaining blocker: create or verify the npm tools-mcp organization in npmjs.com, then rerun npm org ls tools-mcp. Once that no longer returns Scope not found, publish with npm publish --access public and submit server.json to the MCP Registry.

[seokmogu]

Update 2026-05-20:

• npm publication is complete: @tools-mcp/vessel-traffic-mcp@0.1.0 is public and latest points to 0.1.0.
• Published commit state: 2ef701e fixed npm canonical bin paths; 851bfb3 documents npm publication status.
• Verified after publication: npm view @tools-mcp/vessel-traffic-mcp name version dist-tags.latest --json, targeted metadata/release tests, and mcp-publisher validate server.json.
• MCP Registry login succeeded, but mcp-publisher publish server.json failed with 403 because the authenticated GitHub user can publish io.github.seokmogu/*, while this server is io.github.tools-mcp/vessel-traffic-mcp. The registry says publishing under the GitHub org requires public GitHub organization membership for tools-mcp or another approved registry identity.

Remaining blocker for MCP Registry: decide whether to make GitHub membership in tools-mcp public, or use a different registry identity/namespace. Directory submissions can proceed using the now-public npm package URL.

[seokmogu]

Update 2026-05-20:

• GitHub tools-mcp organization membership was made public so MCP Registry can verify io.github.tools-mcp/* ownership.
• MCP Registry publication completed successfully: io.github.tools-mcp/vessel-traffic-mcp@0.1.0.
• npm remains public: @tools-mcp/vessel-traffic-mcp@0.1.0, latest -> 0.1.0.
• Documentation updated and pushed in b12a892 (Document MCP Registry publication).
• Verification after publication: mcp-publisher validate server.json, npm view @tools-mcp/vessel-traffic-mcp name version dist-tags.latest --json, and release/discoverability tests all pass.

Remaining directory work: submit/update Smithery, Glama, and PulseMCP listings using the public GitHub repo, npm package, and MCP Registry metadata.

[seokmogu]

Update 2026-05-20:

• Added a public HTTP directory metadata endpoint: GET /.well-known/mcp/server-card.json.
• The server card exposes package, Streamable HTTP transport, tool, and provenance metadata without bearer tokens or provider credentials.
• Aligned the card with Smithery-style fields: serverInfo, top-level authentication, tools, resources, and prompts.
• Added tests that compare the server-card tool list against the actual MCP tools/list response.
• Updated README and runbooks for directory status, Smithery HTTPS requirements, and reverse-proxy handling for the server-card endpoint.
• Verification passed: npm run lint, npm test (841 tests: 839 pass, 2 skipped), tmp/bin/mcp-publisher validate server.json, and npm view @tools-mcp/vessel-traffic-mcp name version dist-tags.latest --json.
• Pushed commits: 7f49e1c Add HTTP server-card metadata and 4c81fcb Align server card with Smithery fields.

Remaining directory work:

• Glama/PulseMCP: monitor automatic ingestion from the official MCP Registry listing.
• Smithery: submit after a stable public HTTPS Streamable HTTP URL is available; localhost is intentionally not suitable.

[seokmogu]

Update 2026-05-20:

• Added overseas launch kit under docs/marketing/.
• Prepared directory submission fields, Hacker News / Reddit / DEV / Hashnode / Lobsters / Indie Hackers drafts, Product Hunt copy, and safety notes.
• Added launch screenshot: docs/marketing/assets/map-ui-ever-given.png.
• README and public-sharing runbook now link to the marketing kit.
• Pushed commit: 2de1260 Add overseas launch marketing kit.
• Created a tools-mcp fork branch for appcypher/awesome-mcp-servers: tools-mcp:add-vessel-traffic-mcp.
• PR creation to appcypher/awesome-mcp-servers is blocked by the current GitHub token permissions. Manual compare URL: appcypher/awesome-mcp-servers@main...tools-mcp:awesome-mcp-servers:add-vessel-traffic-mcp

Verification:

• git diff --check passed.
• npm run lint passed.
• node --test test/open-source-release.test.js test/discoverability-metadata.test.js passed.

Remaining posting work:

• Submit Glama, FindMCP, MCP.Directory, mcpservers.org, Product Hunt, HN, Reddit, DEV/Hashnode with the prepared copy.
• Smithery still waits for a stable public HTTPS /mcp endpoint.

[seokmogu]

Update 2026-05-23 KST:

• Created the public GitHub release: https://github.com/tools-mcp/vessel-traffic-mcp/releases/tag/v0.1.0
• Created the public GitHub Discussion announcement: Vessel Traffic MCP v0.1.0 is public #6
• Added Korean/community outreach drafts and a live outreach status tracker in docs/marketing/community-posts.md and docs/marketing/outreach-status.md.
• Documented current traction evidence: GitHub traffic API reports 602 clones / 172 unique cloners in the available 14-day window; npm reports 59 downloads for 2026-05-15..2026-05-21.
• Verification passed before push: npm run lint, npm test (841 tests: 839 pass, 2 skipped), and npm run build.
• Pushed commit: 5f07f36 (Make outreach follow-up reproducible). CI passed: https://github.com/tools-mcp/vessel-traffic-mcp/actions/runs/26296984227

Remaining blockers:

• Glama still does not index tools-mcp/vessel-traffic-mcp; its server page/API/badge currently return 404. This continues to block the open punkpeye/awesome-mcp-servers PR, which is labeled missing-glama.
• Smithery still needs a stable public HTTPS Streamable HTTP endpoint before submission.
• Broader community posts are drafted and ready, but each external community post requires a logged-in account and final submit action on that site.

[seokmogu]

Follow-up 2026-05-23 KST:

• Fixed directory-facing license detection by moving the not-for-navigation warning from LICENSE into NOTICE.
• GitHub community profile now recognizes the repository license as MIT instead of NOASSERTION.
• Pushed commit: 1eec449 (Expose a standard MIT license for directories).
• Verification passed locally: git diff --check, npm run lint, npm test (841 tests: 839 pass, 2 skipped), npm run build, and npm pack --dry-run.
• CI passed for the pushed commit: https://github.com/tools-mcp/vessel-traffic-mcp/actions/runs/26297265969

Remaining blocker stays the same: Glama still requires maintainer-authenticated submission for tools-mcp/vessel-traffic-mcp; once Glama indexes the server and exposes the score badge, the blocked awesome-mcp-servers PR can be updated.

[seokmogu]

Follow-up 2026-05-23 KST:

• Reworked README for launch traffic: language selector, status badges, map screenshot, direct npm/npx MCP install path, provider model, current distribution table, and Star History chart.
• Pushed commit: af5c055 (Make the README credible for launch traffic).
• Verification passed locally: git diff --check, targeted README/discoverability/client tests (68 pass), npm run lint, npm test (841 tests: 839 pass, 2 skipped), npm run build, and npm pack --dry-run.
• CI passed: https://github.com/tools-mcp/vessel-traffic-mcp/actions/runs/26297666898

Remaining: continue Glama submission and community posting from the refreshed README landing page.

[seokmogu]

Follow-up 2026-05-23 KST:

• Added the authenticating GitHub maintainer username to glama.json for Glama organization-repository verification.
• Included glama.json in the npm package allowlist and updated discoverability/runbook docs plus the metadata test contract.
• Pushed commit: 8037744 (Make Glama ownership verifiable).
• Verification passed locally: git diff --check, node --test test/discoverability-metadata.test.js test/open-source-release.test.js, npm run lint, and npm pack --dry-run.
• CI passed: https://github.com/tools-mcp/vessel-traffic-mcp/actions/runs/26298092331

Remaining: Glama still requires interactive submission/OAuth; API lookup returns not_found until the server is submitted/indexed.

[seokmogu]

Follow-up 2026-05-24 KST:

• Confirmed Glama is still not complete: API returns not_found, the badge URL returns 404, and the open punkpeye PR remains blocked by missing-glama.
• Ran mcp-submit --dry-run only; it found eligible lanes but several integrations are detection-only/pending, so it should not be run unfiltered.
• Submitted to MCP Find via PR: Add: Vessel Traffic MCP MCPFind/mcp-find#47
  • Current status: open, with fork workflow checks marked action_required pending maintainer approval. The visible Vercel failure is an authorization gate, not a YAML validation failure.
• Submitted to mcp.so via issue: [Submit] Vessel Traffic MCP - Read-only maritime AIS and schedule tools chatmcp/mcpso#2482
• Updated the directory submission tracker and outreach status docs.
• Pushed commits: e56133f (Track the usable outreach lanes) and d676a05 (Record the public directory submissions).
• CI passed for the latest tracker commit: https://github.com/tools-mcp/vessel-traffic-mcp/actions/runs/26336112763

Remaining:

• Glama still needs interactive Glama/GitHub login or maintainer-side indexing before the awesome-mcp-servers PR can be unblocked.
• MCP Find needs maintainer approval for fork workflows/review.
• Smithery still waits for a stable public HTTPS /mcp endpoint.