Onboarding request: co.civai.nova (24 servers) for github.com/mcp

[mrkeyiano]

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.nova namespace, which I understand is the prerequisite before manual curation.

First-party: CIVAI TECHNOLOGIES operates the Nova service at nova.civai.co and publishes these endpoints.

Registry details

• Namespace: co.civai.nova
• Registry IDs: co.civai.nova/{slug} for each of the 24 slugs below
• Namespace ownership: proven by domain auth at https://nova.civai.co/.well-known/mcp-registry-auth
• Transport: Streamable HTTP for every server
• Auth: OAuth 2, discovery at https://nova.civai.co/.well-known/oauth-authorization-server and per-server protected resource metadata at https://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:

Registry ID	Endpoint	Tools
co.civai.nova/research-agent	https://nova.civai.co/mcp/agents/research-agent	4
co.civai.nova/pdf-agent	https://nova.civai.co/mcp/agents/pdf-agent	6
co.civai.nova/slidegen-agent	https://nova.civai.co/mcp/agents/slidegen-agent	4

The 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:

curl -s -X POST https://nova.civai.co/mcp/agents/research-agent \
  -H 'Content-Type: application/json' \
  -H 'Accept: application/json, text/event-stream' \
  -d '{"jsonrpc":"2.0","id":1,"method":"tools/list"}'

290 tools across the 24 servers. tools/call without a credential returns 401 with a message pointing at the sign-in and API-key paths.

Also:

• Unauthenticated server card per server: https://nova.civai.co/.well-known/mcp/agents/{slug}/server-card.json
• Per-server listing repo: https://github.com/civai-technologies/{slug}-mcp-by-nova-civai (MIT)
• Also published on Smithery as 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.