---
title: "Authorization Server Metadata"
method: GET
path: "/.well-known/oauth-authorization-server"
tags: ["mcp"]
---

# Authorization Server Metadata

`GET /.well-known/oauth-authorization-server`

## Request

- Base URL: `https://api.alert.camp` (the document declares no server; this is the origin it was published from)
- URL: `https://api.alert.camp/.well-known/oauth-authorization-server`
- Auth: none declared

What this server supports, so a client need not be told out of band.

Also answered at the RFC 8414 path-scoped location for the resource's
path: a client that treats the resource URL as the issuer asks for
``/.well-known/oauth-authorization-server/mcp``, and some stop at a 404
rather than retrying the root form.

## Query parameters

- `issuer_path` string

## Response `200`

Successful Response

- unknown

## Other responses

- `422`: Validation Error

---

[API](https://skmtc.dev/alert/apis/alertcamp.md) · [All operations](https://skmtc.dev/alert/apis/alertcamp/llms.txt) · [OpenAPI document](https://skmtc.dev/alert/apis/alertcamp/revisions/864c8c9ef833?raw)