---
title: "Check OAuth requirement"
method: POST
path: "/projects/{projectId}/servers/{serverId}/check-oauth"
tags: ["Server diagnostics"]
---

# Check OAuth requirement

`POST /projects/{projectId}/servers/{serverId}/check-oauth`

Lightweight, no MCP connection: reports whether the server is configured to require an OAuth grant.

## Path parameters

- `projectId` string, required
- `serverId` string, required

## Request body

- object

## Response `200`

OAuth requirement for the server.

- CheckOAuthResult
  - `useOAuth` boolean, required — Whether the server is configured to require an OAuth grant.
  - `serverUrl` string, nullable, required — The server's URL, or `null` for non-HTTP transports.

## Other responses

- `400` — Malformed body or parameters.
- `401` — Missing, invalid, revoked, or orphaned key (`UNAUTHORIZED`) — or the **target MCP server** needs an OAuth grant (`OAUTH_REQUIRED`), which is a property of the server, not your key.
- `403` — Key is valid but not allowed to do this.
- `404` — Unknown project, server, or resource.
- `429` — Per-key rate limit exceeded (60 requests/minute sustained, bursts up to 10). Honor `Retry-After` and back off with jitter.
- `500` — Something failed on MCPJam's side.

---

[API](https://skmtc.net/mcpjam/apis/mcpjam-api.md) · [All operations](https://skmtc.net/mcpjam/apis/mcpjam-api/llms.txt) · [OpenAPI document](https://skmtc-service-staging.skmtc.workers.dev/v1/apis/mcpjam/mcpjam-api/versions/b767df188d0c/schema)