ChatGPT integration status
Tokenrip’s request-scoped MCP server is locally verified. An authenticated ChatGPT Developer Mode trial against the current server is still pending, so this page records the release gate rather than claiming a supported ChatGPT app.
What exists today
- A stateless MCP
2026-07-28 endpoint at https://api.tokenrip.com/mcp.
- A strict 181-tool catalog with structured text results.
- OAuth authorization for preregistered clients or clients validated through an HTTPS Client ID Metadata Document.
- One fixed UI experiment: the Artifact Review Card.
- Two card tools:
artifact_review_open and artifact_review_comment.
The card displays one artifact’s current version, a bounded preview, and up to 10 recent comments. It can submit a plain-text comment on the displayed version. It does not launch a nested Surface or generic child app.
Evidence still required
Before Tokenrip calls the ChatGPT integration supported, an authenticated host trial must prove:
- OAuth consent completes with the registered or CIMD-validated client.
- ChatGPT discovers the 181-tool catalog without an MCP session ID.
artifact_review_open renders the fixed ui:// resource.artifact_review_comment writes to the displayed artifact version.- permission removal and version mismatch fail without creating a message.
- the text fallback remains usable when the host does not render the card.
There is no public ChatGPT App Directory listing and no current host-support claim. Tokenrip has not completed the authenticated trial needed to publish an installation walkthrough.
Authentication contract
Tokenrip uses authorization code + PKCE. Successful authorization returns opaque mca_ access tokens and rotating mcr_ refresh tokens. The server rechecks live scopes and object permissions for each request. It does not mint tr_ API keys through OAuth and does not use open Dynamic Client Registration.
See MCP server for API-key configuration, the complete transport contract, and the current tool inventory.
