Skip to content

MCP install routes, server.json metadata and audit checks - #1

Merged
rome2o merged 1 commit into
mainfrom
improve/mcp-install-and-metadata
Oct 30, 2026
Merged

rome2o merged 1 commit into
mainfrom
improve/mcp-install-and-metadata

Conversation

@rome2o

@rome2o rome2o commented Oct 30, 2026

Copy link
Copy Markdown
Contributor

Adds what we learned publishing devkindhq MCP servers.

  • New reference mcp-install-and-metadata.md: package types and their ownership checks (npm, PyPI, NuGet, Cargo, OCI, MCPB), namespace and auth, server.json fields (100 char description cap, websiteUrl), README install routes per client, listing files (smithery.yaml, manifest.json), org visibility.
  • SKILL.md Step B and the registry checklist point to it.
  • check_repo_seo.py now checks server.json (namespace, description length, websiteUrl) and the OCI label.
  • New Docker/OCI quality eval and changelog entry.

Registry facts verified against the official docs on 2026-10-31. Per-client install steps come from a live server README and are labelled observed.

🤖 Generated with Claude Code

Co-Authored-By: Claude Sonnet 5.5 <noreply@anthropic.com>
@rome2o
rome2o merged commit 6042ca2 into main Oct 30, 2026
3 checks passed
@superkindhq

superkindhq Bot commented Oct 31, 2026

Copy link
Copy Markdown

post-merge audit — github-seo-skill #1 — MCP install routes, server.json metadata and audit checks

Bucket B (zero reviews at merge; repo's first PR; merged 2026-10-30 21:29 UTC at 6042ca2). Docs/skill-only — no executable code.

🟢 clean, one nit

  • New references/mcp-install-and-metadata.md is well-disciplined: registry facts carry a verification date (2026-10-31) and [verified]/[observed] labels; the observed _meta-vs-websiteUrl gap is stated as unknown rather than asserted. SKILL.md wiring and evals.json quality case updated consistently; CHANGELOG entry present.
  • 🟡 nit: the OCI supported-hosts list (Docker Hub, ghcr.io, GAR, *.azurecr.io, mcr.microsoft.com) is pinned to one date — worth a dated re-check before relying on it, since the registry is a moving target.

No findings to carry forward.

Sign up for free to join this conversation on GitHub. Already have an account? Sign in to comment

Labels

None yet

Projects

None yet

Development

Successfully merging this pull request may close these issues.

1 participant