Drata .well Known API
The .well Known API from Drata — 4 operation(s) for .well known.
Work with this as data
Every API here is available over the APIs.io API and to AI agents over MCP.
MCP server
One button, every client — Claude, Cursor, VS Code and the rest.
https://apis.io/mcp
Tools for apis
7 MCP tools reach this
find_apisBrowse and filter every API in the catalog.get_api_artifactsOne API's artifacts, grouped by type.get_openapiThe primary OpenAPI for this API.find_similar_apisAPIs that look like this one.apis_io_searchSTART HERE — APIs, providers and tags for one query, each with its total.resolveTurn a domain, URL or GitHub org into the provider it belongs to.find_cohortsEvery scored population of providers in the catalog.
Call it yourself
curl for this page
This API
curl "https://apis.io/api/v1/apis/drata:drata-well-known-api"
All apis
curl "https://apis.io/api/v1/apis?limit=25"Discovery needs no key. Ratings and market analysis are Pro.
Get an API key
Free tier, no form to fill in. Signing in shares your email address with us — we store it to create your key and to recognise you if you sign in with another provider. See our Privacy Policy and Terms.
A second provider on the same verified email joins the account you already have.
OpenAPI Specification
openapi: 3.2.0
info:
title: Fast .well Known API
version: 0.1.0
tags:
- name: .well Known
paths:
/.well-known/openid-configuration:
get:
summary: Oauth Authorization Server
description: 'Root-level OAuth authorization server metadata.
Some MCP clients look for OIDC configuration at the root level.
This proxies Auth0''s configuration with our modified authorization_endpoint.
Matches TypeScript implementation in mcp.controller.ts.'
operationId: oauth_authorization_server__well_known_openid_configuration_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
options:
summary: Options Handler
description: Handle OPTIONS requests for CORS preflight.
operationId: options_handler__well_known_openid_configuration_options
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
/.well-known/oauth-authorization-server/mcp:
get:
summary: Oauth Authorization Server
description: 'Root-level OAuth authorization server metadata.
Some MCP clients look for OIDC configuration at the root level.
This proxies Auth0''s configuration with our modified authorization_endpoint.
Matches TypeScript implementation in mcp.controller.ts.'
operationId: oauth_authorization_server__well_known_oauth_authorization_server_mcp_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
options:
summary: Options Handler
description: Handle OPTIONS requests for CORS preflight.
operationId: options_handler__well_known_oauth_authorization_server_mcp_options
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
/.well-known/oauth-authorization-server:
get:
summary: Oauth Authorization Server
description: 'Root-level OAuth authorization server metadata.
Some MCP clients look for OIDC configuration at the root level.
This proxies Auth0''s configuration with our modified authorization_endpoint.
Matches TypeScript implementation in mcp.controller.ts.'
operationId: oauth_authorization_server__well_known_oauth_authorization_server_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
options:
summary: Options Handler
description: Handle OPTIONS requests for CORS preflight.
operationId: options_handler__well_known_oauth_authorization_server_options
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
/.well-known/oauth-protected-resource:
get:
summary: Oauth Protected Resource
description: 'OAuth Protected Resource metadata endpoint.
This is the primary discovery endpoint that MCP clients (like mcp-remote) use
to discover OAuth requirements. It points clients to our Auth0 proxy as the
authorization server.
See: RFC 9728 (OAuth 2.0 Protected Resource Metadata)'
operationId: oauth_protected_resource__well_known_oauth_protected_resource_get
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
options:
summary: Options Handler
description: Handle OPTIONS requests for CORS preflight.
operationId: options_handler__well_known_oauth_protected_resource_options
responses:
'200':
description: Successful Response
content:
application/json:
schema: {}
tags:
- .well Known
x-provenance:
method: harvested
publisher: Drata
source: https://mcp.drata.com/openapi.json
note: split by refine-openapis from the provider's own published document, verified by fetch (openapi/_original/*.fetch.json);
stamped by stamp-openapi-provenance.py (roadmap#793)