@upstash/context7-mcp@4.4.0

upstash/context7@upstash/context7-mcp@4.4.0Oct 13, 2026by github-actions[bot]

Upgrading?

AI Summary

A minor release introducing a new OAuth enforcement mode and improvements to token verification.

Key Highlights

  • Added `foreign` mode to OAuth audience enforcement on hosted HTTP transport.
  • Improved Microsoft Entra token signature verification.
  • Updated Next.js examples to version 16.

New Features

  • New `foreign` mode for OAuth audience enforcement.

Full Release Notes

### Minor Changes

- 2d57b23: Add a `foreign` mode to the OAuth audience check on the hosted HTTP transport. `MCP_OAUTH_AUDIENCE_ENFORCEMENT=foreign` answers HTTP 401 (`WWW-Authenticate: Bearer error="invalid_token"`, "This token was issued for another server. If you connect through a gateway or proxy, use a Context7 API key instead.") to a Clerk OAuth JWT whose `aud` names another server, and still admits a token with no `aud`, which grants authorized before Clerk's "Include Audience" setting carry on every refresh. `observe` (the default) and `required` are unchanged. The query string of an audience on an allowed host is ignored, since Cursor writes the configured MCP URL (`https://mcp.context7.com/mcp?client=codex`) into `resource`; on any other host it is kept. The `audienceMismatch` log line now carries `outcome=accepted|rejected` and is written at most once per token per hour instead of every ten minutes.

### Patch Changes

- 2882596: Verify Microsoft Entra token signatures before looking up the audience, and cap the Entra config cache.
- 615e72b: Update the Next.js examples in the tool descriptions, the CLI rule and the bundled skill: the version example is now `/vercel/next.js/v16.2.9`, and the prompts use Next.js 16.

Related Repositories