OAuth
Dynamic Client Registration
Dynamic Client Registration (RFC 7591) — required by MCP spec.
RFC 7591 §3.2.1 mandates HTTP 201 Created on success and that the response echo all registered metadata plus any server-provisioned fields (notably client_id_issued_at). Strict DCR clients (e.g. Smithery's) reject responses that don't match.
post/api/v1/oauth/register
Response
Successful Response
{"stackTrail":"paths:/api/v1/oauth/register:post:responses:201:content:application/json:schema","oasType":"schema","type":"unknown"}
Changes
No recorded changes to this endpoint across all 1 revision of this API.