Unable to detect timestamp validity on tokens that use the "expires_in" vs "expires_at" Oauth response

[yinzara]

When using the mcp-remote tool and getting an oauth token issued back. I keep getting the following error printed in the logs and it ends up not ever refreshing the token even when expired.

⚠️ WARNING: Invalid expires_at detected while reading tokens ⚠️

The actual access token looks like this:

{
  "access_token": "my-very-secret-token",
  "token_type": "Bearer",
  "expires_in": 28800,
  "scope": "prism"
}

My very secret token also has an exp claim that is valid and in the future.

[d96litz]

Can confirm. I'm getting the same trying to connect to the atlassian mcp server

[geelen]

Yeah that was some vibe-coded debugging that generated the wrong name. It's all cleaned up in #96, but that's blocked upstream. Will try to hurry that along and get this all tidied.