Show the protected-resource metadata for a connector's MCP endpoint
const url = 'http://127.0.0.1:8080/.well-known/oauth-protected-resource/mcp/example';const options = {method: 'GET'};
try { const response = await fetch(url, options); const data = await response.json(); console.log(data);} catch (error) { console.error(error);}curl --request GET \ --url http://127.0.0.1:8080/.well-known/oauth-protected-resource/mcp/examplePublic and not versioned. The RFC 9728 metadata for /mcp/{connector}, at the path-inserted URL that the endpoint’s bearer challenges name in resource_metadata. The document is the same for every well-formed connector id and never reads the database; a malformed id is 404 not_found. authorization_servers is absent on purpose, as in the root document. Readable cross-origin and cached for an hour.
Parameters
Section titled “Parameters”Path Parameters
Section titled “Path Parameters”The upstream’s connector name (mcp.upstreams.<name>), or a connector id (con_…) from S16.
Responses
Section titled “Responses”The metadata document.
RFC 9728 protected-resource metadata. authorization_servers is absent on purpose in v1: Deedglass v1 takes pre-issued API keys as bearer tokens and has no authorization server to list; v2 adds the org’s issuer.
object
The resource identifier (the API’s base URL
Example
{ "resource": "https://api.deedglass.com/mcp/con_01k67c04kxevyex3pjyqe0t45d", "resource_name": "Deedglass Gate", "bearer_methods_supported": [ "header" ], "scopes_supported": [ "actions:execute" ], "resource_documentation": "https://docs.deedglass.com/mcp/authorization"}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
default
Section titled “default”An error. Every error has this envelope; doc_url explains the code.
object
object
One or more calm sentences with the next step.
The request field, query parameter or header the error is about.
On policy_invalid only. Each problem with its line, code and hint.
One finding about a policy file, with its position and the next step. Codes are stable and listed in docs/POLICY_ERRORS.md. In the policy_invalid error envelope each diagnostic also carries object: policy_diagnostic. The full PolicyDiagnostic schema is in openapi.yaml.
object
One agent action. Its sections mirror the deed’s. status is the one field an agent needs; state is the exact lifecycle state (docs/GATE.md). The Gate’s own responses (POST /v1/actions and its result report) add execution.result and witness.reasons; lists leave both out. The full Action schema is in openapi.yaml.
object
On undo_unavailable only. Every check of the undo, each with its fix. Additive (S23).
One of the twelve safety checks (S23 §3.3). Available means no check failed. The full UndoCheck schema is in openapi.yaml.
object
Example
{ "error": { "type": "invalid_request_error", "code": "not_found", "message": "There's no endpoint at GET /v1/helth. Did you mean /v1/health?", "param": null, "request_id": "req_01j9zr3m5k8q2w7x4t6v0b1c9d", "doc_url": "https://docs.deedglass.com/errors/not_found" }}Headers
Section titled “Headers”This request’s id. Quote it to support; it matches error.request_id.
The API version this response follows.