Orium R&D · 2026
An MCP server that scopes a Stripe API upgrade with cited evidence — for the coding agent already open in your repo. It never writes.
- Client
- Orium R&D
- Role
- Creator · sole author
- Year
- 2026
Outcomes
Context
Stripe ships breaking API changes on a release train, and most integrations don't know which release they're really on. Portage answers four questions for the coding agent: which release the code is actually on, which breaking changes touch it (file:line plus changelog), what to write instead, and what proves each change was handled.
What I built
- 01
A read-only MCP server over stdio, in TypeScript with Zod-validated tools, backed by the Stripe CLI's docs.
- 02
A catalogue of 51 stable breaking changes with authored remediation specs, and a verify step that separates new failures from pre-existing ones.
- 03
Validation on four open-source codebases nobody on the team chose (documenso, formbricks, Ghost, cal.com); all 8 defects it surfaced were closed.