Repository navigation
Replies: 1 comment
|
This repository, its issues and discussions are not the best forum for requests for MCP Registry inclusion and related discussions. Please follow the advice here: https://github.blog/ai-and-ml/generative-ai/how-to-find-install-and-manage-mcp-servers-with-the-github-mcp-registry#h-how-to-publish-your-own-mcp-server |
0 replies
Sign up for free
to join this conversation on GitHub.
Already have an account?
Sign in to comment
Uh oh!
There was an error while loading. Please reload this page.
Request
Please consider onboarding the Nova by CIVAI MCP servers to the GitHub MCP Registry. All 24 are published to the open source MCP Registry under the
co.civai.novanamespace, which I understand is the prerequisite before manual curation.First-party: CIVAI TECHNOLOGIES operates the Nova service at
nova.civai.coand publishes these endpoints.Registry details
co.civai.novaco.civai.nova/{slug}for each of the 24 slugs belowhttps://nova.civai.co/.well-known/mcp-registry-authhttps://nova.civai.co/.well-known/oauth-authorization-serverand per-server protected resource metadata athttps://nova.civai.co/.well-known/oauth-protected-resource/mcp/agents/{slug}. A programmatic API key is also accepted.If you would rather start with three
I appreciate curation is manual, so rather than ask for 24 at once, these three are the most generally useful and exercise the same auth and transport as the rest:
co.civai.nova/research-agenthttps://nova.civai.co/mcp/agents/research-agentco.civai.nova/pdf-agenthttps://nova.civai.co/mcp/agents/pdf-agentco.civai.nova/slidegen-agenthttps://nova.civai.co/mcp/agents/slidegen-agentThe full set: blogger, browsergpt, calendar, code-interpreter, content-calendar, content-pipeline, gmail, google-docs, google-sheets, instagram-web, interviewer, leads-discovery, music, nova-inbox, openclaw, pdf, product-admin, research, slidegen, support-agent-admin, telegram, terminal-command, twitter, whatsapp-web.
Verifiable without a credential
Tool discovery is open on every endpoint, so these can be checked before any curation work:
290 tools across the 24 servers.
tools/callwithout a credential returns 401 with a message pointing at the sign-in and API-key paths.Also:
https://nova.civai.co/.well-known/mcp/agents/{slug}/server-card.jsonhttps://github.com/civai-technologies/{slug}-mcp-by-nova-civai(MIT)civai/{slug}One disclosure
The listing repos hold packaging metadata (README,
llms-install.md, LICENSE, icon,server.json,mcp.json), not the server implementation, which runs on CIVAI's backend. These are hosted first-party servers, same shape as other vendor remotes in the registry, but I would rather say it up front than have it surface in review.Happy to split this into one request per server if that suits your process better, or to provide anything else curation needs.
All reactions