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

docs: fix server lookup instructions in publishing guide (#411)

Browse source 
The publishing guide incorrectly suggested users could verify their
server by directly accessing `/servers/{server-name}` or
`/v0/servers/{server-name}`, but the API only supports:

1. **Search by name**: `GET /v0/servers?search={server-name}`
2. **Get by UUID**: `GET /v0/servers/{uuid}`

This PR updates the documentation to show the correct verification
method using the search endpoint.

Fixes #410
This commit is contained in:
adam jones 2025-09-10 09:32:18 -07:00 • committed by GitHub
commit 91b3e414ec
No known key found for this signature in database
GPG key ID: B5690EEEBB952194
1 changed files with 6 additions and 12 deletions
Download patch file Download diff file Expand all files Collapse all files

14
docs/guides/publishing/publish-server.md
View file

@ -318,24 +318,18 @@ mcp-publisher publish
You'll see output like:
```
✓ Validating server.json
✓ Checking package ownership
✓ Publishing to registry
✓ Server published successfully!
Your server is now available at:
https://registry.modelcontextprotocol.io/servers/io.github.yourname/weather-server
✓ Successfully published
```
## Step 6: Verify Publication
Check that your server appears in the registry:
Check that your server appears in the registry by searching for it:
```bash
curl https://registry.modelcontextprotocol.io/servers/io.github.yourname/weather-server
curl "https://registry.modelcontextprotocol.io/v0/servers?search=io.github.yourname/weather-server"
```
You should see your server metadata returned as JSON.
You should see your server metadata returned in the JSON response.
## Troubleshooting