modelcontextprotocol/registry
Watch
1
0
Fork
You've already forked registry
 0
Code Issues Pull requests Projects Releases Packages Wiki Activity Actions

docs: Fix errors and typos in public documentation

Browse source 
- Fix `--private-key-file` to `--private-key` in `github-actions.mdx`
  DNS authentication example (the CLI expects hex-encoded key data, not
  a file path)
- Add missing `./` prefix to `mcp-publisher` command in PAT
  authentication example
- Fix typo `verfication` to `verification` in troubleshooting table
- Remove duplicate word `authentication` in `quickstart.mdx`
  prerequisites
- Fix `name` to `identifier` field in JSON examples in `versioning.mdx`
- Fix `PyPi` to `PyPI` (correct capitalization) in
  `moderation-policy.mdx`

Co-Authored-By: Claude Opus 4.5 <noreply@anthropic.com>
This commit is contained in:
Jonathan Hefner 2026-01-21 09:58:53 -06:00
commit 9d30456d48
1 changed files with 7 additions and 9 deletions
Download patch file Download diff file Expand all files Collapse all files

2
docs/modelcontextprotocol-io/moderation-policy.mdx
View file

@ -15,7 +15,7 @@ Subregistries may have their own moderation policies. If you have questions abou
The MCP Registry **does not** make guarantees about moderation, and consumers should assume minimal-to-no moderation.
The MCP Registry is a community supported project, and we have limited active moderation capabilities. We largely rely on upstream package registries (like NPM, PyPi, and Docker) or downstream subregistries (like the GitHub MCP Registry) to do more in-depth moderation.
The MCP Registry is a community supported project, and we have limited active moderation capabilities. We largely rely on upstream package registries (like NPM, PyPI, and Docker) or downstream subregistries (like the GitHub MCP Registry) to do more in-depth moderation.
This means there may be content in the MCP Registry that should be removed under this policy, but which we haven't yet removed. Consumers should treat scraped data accordingly.