Badge endpoint (/badge/[...id]) returns HTTP 500 site-wide

[kveita]

Summary

The badge endpoint at https://smithery.ai/badge/<namespace>/<slug> returns HTTP 500 for every server, every namespace, every URL variant tested. The response body is empty (Content-Length: 0) and the server returns a generic Vercel 500 page.

Impact

• Every README badge using https://smithery.ai/badge/... renders as a broken image
• Affects all MCP servers listed on Smithery that embed the badge
• Multiple repos are already working around this by replacing the badge: joaoh82/rustunnel#101, AIStoryHub/etincel#25, alexander-zuev/supabase-mcp-server@d674529

Reproduction

curl -sI https://smithery.ai/badge/misakanet/misakanet
# HTTP/2 500

curl -sI https://smithery.ai/badge/brave
# HTTP/2 500

Debug info from response headers

• x-matched-path: /badge/[...id] — the route is being hit
• x-vercel-cache: MISS — fresh invocation each time
• Content-Length: 0 — the function crashes before producing output
• content-type is absent — no error page is rendered either

Expected behavior

The endpoint should return an SVG image (e.g. image/svg+xml) showing the server's Kin score, similar to how https://smithery.ai/servers/misakanet/misakanet renders the score in the page.

Additional context

The server page at https://smithery.ai/servers/misakanet/misakanet works fine and shows "82 /100" as the Kin score. The badge endpoint at /badge/[...id] is a separate route in the Next.js application that appears to be crashing.