feat(mcp): add official registry server packet - #33
Conversation
TegamiThis repository uses Tegami to manage releases. When your changes affect published packages, add a changelog file under Create a changelog → · Changelog format No changelogs yetThis PR has no pending changelog files. If your changes require a release, add a changelog before merging. Run Managed by Tegami. |
Greptile SummaryThe PR adds the official MCP Registry packet for Samva’s hosted server and documents its validation, DNS authentication, and explicitly gated publication process.
Confidence Score: 5/5The 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.
|
| 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
Summary
server.jsonfor SamvaSamvaHQ/samvarepository and pin its GitHub IDValidation
bunx --package ajv-cli ajv validate -s <(curl -LfsS https://static.modelcontextprotocol.io/schemas/2025-12-11/server.schema.json) -d server.jsonbun run format:checkbun run validate:agent-plugingh api repos/SamvaHQ/samvaprovenance checkPublish boundary
This PR intentionally does not run
mcp-publisher publishor submit to the external registry. The future DNS-authenticated command is documented indocs/mcp-registry.mdand requires an explicit approval gate.