[mrkeyiano]

Adds one MCP server: Nova Research (CIVAI), under knowledge.

One server per PR, as CONTRIBUTING asks.

Checks

• node scripts/validate-catalog.mjs : Validated 44 MCP server entries.
• node scripts/generate-readme.mjs : Generated README.md with 10 populated categories. Regenerated README committed.

Folder path, slug and category field all agree: servers/knowledge/nova-research-civai/server.json.

On the license field

Set to Proprietary (hosted service; private source), following the precedent already in the catalog. The linked repository is MIT, but that covers packaging metadata only (README, llms-install.md, LICENSE, icon, server.json, mcp.json); the server implementation runs on CIVAI's backend and is not public. Writing plain MIT here would overstate what is open, which is a mistake another directory's maintainer rightly called out on a sibling submission.

Against the review standards

• Public and reachable. tools/list answers without credentials, so you can verify it right now:

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"}'

Returns exactly the 4 tools listed in the entry. A tools/call without a credential returns 401, so a user knows what they are connecting to and what it will ask for.

• Documented. Homepage plus a repo with endpoint, both auth paths, per-client config and an llms-install.md.
• Specific enough to evaluate before connecting. The tool names are in the entry rather than a vague summary.
• Verifiable from public information. Official MCP Registry entry co.civai.nova/research-agent, namespace ownership proven by domain auth at https://nova.civai.co/.well-known/mcp-registry-auth. Also on Smithery as civai/research-agent.

First-party: CIVAI Technologies operates the Nova service. If you would rather see this in data or elsewhere, say so and I will move the folder and the field together.