Replies: 3 comments
|
The registry entry looks generally complete, but I noticed that the repository's current There is also a small metadata mismatch:
I would update mcp-publisher validate server.jsonEven if the official Registry already contains Once it appears on |
|
Thanks for the review, @stefisha — the metadata drift you flagged is fixed. PR #335 corrected and permanently synchronized Could GitHub continue the curation/onboarding review for |
|
Thanks for confirming and fixing the metadata issue! Since the issue identified in my response is now resolved, would you mind marking it as the accepted answer? The discussion can remain open while GitHub continues the curation/onboarding review. |
Uh oh!
There was an error while loading. Please reload this page.
Onboarding request:
io.github.bruchris/canvas-lms-mcpfor github.com/mcpio.github.bruchris/canvas-lms-mcpThe server is already published on the official MCP registry (npm-verified package, GitHub OIDC namespace auth) and has been kept in sync with every release since. Following the pattern in #1257 and #2844, opening this as a Q&A request since I understand initial onboarding to github.com/mcp is still manual curation on your end — happy to provide anything else needed (repo topics, README format, etc.).
Thanks for maintaining the registry!
All reactions