⌘K
NextBlock™ CMS Just submitted our application for **NextBlock CMS**! 🚀 NextBlock is an open-source, full-stack CMS framework built natively for **Next.js 16 (App Router + RSC)** and **Supabase (PostgreSQL JSONB)**. We’ve focused on: * **Zero-Config 1-Click Deploy:** Automated Supabase database migrations on build. * **100/100 Lighthouse Defaults:** Tiptap visual editor renders PostgreSQL JSONB directly into React Server Components, eliminating client hydration overhead and HTML sanitization taxes. * **Cortex AI & Native MCP:** Model Context Protocol server support (`/api/mcp`) for deterministic, schema-constrained block synthesis. * **GitHub:** https://github.com/nextblock-cms/nextblock * **Live Sandbox:** https://cms.nextblock.dev Looking forward to the review process and collaborating with the Vercel DX team! 🧱
Axyl1410 Hi! I applied for the Summer 2026 Vercel OSS Program, but I’m not sure whether my application was successfully submitted. I also didn’t receive a confirmation email. Is there any way for applicants to verify whether their application was received, or is there normally no confirmation email after submitting the form? I’d like to avoid submitting a duplicate application if my original submission went through. Thanks!
Amy Egan It looks like you already found the solution, but sharing here in case it helps anyone else who stumbles on this post https://community.vercel.com/t/what-to-do-when-your-team-is-paused-or-blocked/45069
Amy Egan Coming back to share some info about the new flat rate CDN option in case it helps you or anyone else who sees this post. Flat Rate CDN gives you a fixed monthly price. It covers traffic spikes for CDN Requests, Fast Data Transfer, Blob Data Transfer, and Observability events generated by CDN requests to prevent surprise bills. https://vercel.com/blog/introducing-flat-rate-cdn
system There's another community post with 404 debugging tips that might be helpful. Please give these solutions a try and let us know how it goes. https://community.vercel.com/t/debugging-404-errors/437 A human should be around soon to offer more advice. But you can also get helpful information quickly by asking v0.
Joakim 5043 Not helpful.
Joakim 5043 I have now tested the exact documented endpoint: https://mcp.vercel.com Authentication: OAuth. No path or trailing slash. ChatGPT Work still returns: “Dynamic client registration failed: registration endpoint returned 400 (invalid_redirect_uri: The provided redirect URIs are not approved for use by this authorization server.)” The same registration failure therefore occurs on the standard endpoint. Please investigate which callback URI ChatGPT Work submits and why it is rejected. Separately, please verify the authenticated identity and effective team/project permissions behind the existing connector’s 403/404 failures with explicit, verified IDs. Please provide a private channel for any account details or diagnostic information you need.
