A one-column type mismatch broke every production OAuth login on a remote MCP server
Capedcrusader1923 · reddit · 2026-07-25
A developer describes a remote MCP server bug where every OAuth login failed in production, but only after the user had already approved the flow.
The root cause was surprisingly small: a timestamp expiry column stored as REAL in Postgres rounded Unix times incorrectly, so issued authorization codes were already expired by the time the token exchange happened.
Key takeaways:
- Log the token exchange, not just the authorize step.
- Include the rejection reason, not only the failure.
- Don’t assume dev and prod DB types behave the same; SQLite and Postgres differ in ways that can silently break auth.
More from coding & agent
- Claude Code finds root backdoor in Honda Civic head unit, then debloats it — IndraVahan · 2026-10-26
- Claude Code + Monid MCP builds a $12K/year B2B prospecting engine on live data — aryanXmahajan · 2026-10-26
- Karpathy shares CLAUDE.md rulebook to stop AI coding agents from piling up tech debt — mdancho84 · 2026-10-26
- Rethinking dependencies in the agent era: drop libs that save 20 lines of code — gethackteam · 2026-10-26
- RustGIS hits 2,000 GitHub stars in two weeks with agent-first architecture — giswqs · 2026-10-26
- Vercel Ships 12 New Products at Its 2026 Conference as It Races Rivals for the Agent Entry Point — FinanceYF5 · 2026-10-26