Skip to content

feat(mcp): add official registry server packet - #33

Merged
aryasaatvik merged 1 commit into
mainfrom
seo/m6-mcp-registry-packet-20260901
Sep 1, 2026
Merged

feat(mcp): add official registry server packet#33
aryasaatvik merged 1 commit into
mainfrom
seo/m6-mcp-registry-packet-20260901

Conversation

@aryasaatvik

Copy link
Copy Markdown
Contributor

Summary

  • add the official MCP Registry server.json for Samva
  • correct repository provenance to the canonical SamvaHQ/samva repository and pin its GitHub ID
  • document domain authentication, validation, and the explicit publish gate

Validation

  • bunx --package ajv-cli ajv validate -s <(curl -LfsS https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json) -d server.json
  • bun run format:check
  • bun run validate:agent-plugin
  • HTTP reachability checks for documentation, icon, and protected-resource metadata
  • gh api repos/SamvaHQ/samva provenance check

Publish boundary

This PR intentionally does not run mcp-publisher publish or submit to the external registry. The future DNS-authenticated command is documented in docs/mcp-registry.md and requires an explicit approval gate.

@github-actions

github-actions Bot commented Sep 1, 2026

Copy link
Copy Markdown

Tegami

This repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under .tegami/ before merging.

Create a changelog → · Changelog format

No changelogs yet

This PR has no pending changelog files. If your changes require a release, add a changelog before merging.

Run bun run tegami locally to create a changelog interactively.

Managed by Tegami.

@greptile-apps

greptile-apps Bot commented Sep 1, 2026

Copy link
Copy Markdown

Greptile Summary

The PR adds the official MCP Registry packet for Samva’s hosted server and documents its validation, DNS authentication, and explicitly gated publication process.

  • Declares the canonical server identity, repository provenance, icon, documentation, and streamable HTTP endpoint.
  • Documents local validation and keeps external registry publication out of ordinary CI and review workflows.

Confidence Score: 5/5

The PR appears safe to merge with no concrete blocking or independently actionable non-blocking issues identified.

The new manifest aligns with existing repository documentation and endpoint conventions, while publication remains a deliberate manual operation protected by an explicit approval gate.

Important Files Changed

Filename Overview
server.json Adds a registry manifest whose endpoint, transport, documentation, and repository metadata are consistent with the repository’s existing MCP configuration.
docs/mcp-registry.md Adds clear validation and DNS-authenticated publication instructions with an explicit prohibition against publishing during routine CI or review.

Reviews (1): Last reviewed commit: "feat(mcp): add official registry server ..." | Re-trigger Greptile

@aryasaatvik
aryasaatvik merged commit 98ba424 into main Sep 1, 2026
3 checks passed
@aryasaatvik
aryasaatvik deleted the seo/m6-mcp-registry-packet-20260901 branch September 1, 2026 08:32
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