What problem does it solve?
Adding a new dynamic client registration (DCR) OAuth entry to Novu's MCP server catalog requires verifying that each provider actually supports RFC 7591 self-serve registration, which involves tedious manual documentation review and live endpoint probing.
Core Features & Use Cases
- Candidate Selection: Classifies catalog entries in mcp-servers.ts by oauth.mode and blocker status so only eligible provider-managed entries are onboarded, never re-auditing existing dcr entries.
- Provider Docs Gate: Aborts onboarding when a provider requires redirect URI whitelists, manual approval, fixed pre-registered OAuth apps, or partner approval, and records the blocker in blocked-mcp-servers.md.
- Curl Probe Checklist: Verifies RFC 9728 protected resource metadata, RFC 8414 authorization server metadata, and RFC 7591 dynamic client registration with ready-to-run curl commands and a PR body evidence template.
- Use Case: When adding a new code-category MCP provider to the Novu catalog, run this checklist to confirm DCR support, probe the endpoints, and produce a catalog entry plus documented evidence.
Quick Start
Ask the agent to onboard a new provider-managed MCP entry to DCR mode using the nv-onboard-dcr-mcp checklist and paste the probe outputs into the PR body.