Mcp Memory Resource Metadata

GET /.well-known/oauth-protected-resource/mcp/memory

The memory door’s own RFC 9728 document (D-5304).

A generic client fetches the metadata for the URL it was handed and requires the resource inside to be that URL — which is precisely what makes the memory product connectable as a thing of its own rather than an alias of the general surface.

No credential

This operation is public: it authenticates by its own mechanism — a webhook signature or a channel token — rather than by a platform credential.

Responses

Status	Description	Body
200	Successful Response	—

Only the success paths are declared

Any operation may also answer any status in the error catalogue, and every failure body is the platform envelope — including the 422 this document types as HTTPValidationError.

Example

curl -X GET https://your-deployment.example.com/.well-known/oauth-protected-resource/mcp/memory