client-metadata-support
/client-metadata-support
Support OAuth Client ID Metadata Documents in authorization servers. Use when building or reviewing authorization server client validation and registration mechanisms for MCP ecosystems.
- Author
- redhatproductsecurity ↗
- Repository
- prodsec-skills ↗
- Licence
- Apache-2.0
- Last repository change
- 15.07.2026
Assessment and security
- Files in this package
- 1
- Scripts
- 0
- HTML comments
- 0
- URLs in SKILL.md
- 1
No signals detected. Repository changed on 15.07.2026, without references to retired models or APIs.
Apache-2.0, otwarta: można używać i zmieniać, z zachowaniem licencji i informacji o zmianach.
What it does and when to use it
Support OAuth Client ID Metadata Documents in authorization servers. Use when building or reviewing authorization server client validation and registration mechanisms for MCP ecosystems.
Original author description
Support OAuth Client ID Metadata Documents in authorization servers. Use when building or reviewing authorization server client validation and registration mechanisms for MCP ecosystems.
How it works
- Security Recommendation
- How It Works
- Validation Rules
- Implementation Checklist
SKILL.md preview
--- name: client-metadata-support description: Support OAuth Client ID Metadata Documents in authorization servers. Use when building or reviewing authorization server client validation and registration mechanisms for MCP ecosystems. category: "secure_development" subcategory: "authorization-server" --- # OAuth Client ID Metadata Document Support in Authorization Servers ## Security Recommendation Authorization servers SHOULD support OAuth Client ID Metadata Documents. This mechanism allows clients (including MCP clients) to present their identity and configuration without requiring pre-registration, by hosting a metadata document at their `client_id` URL. ## How It Works 1. Client presents a `client_id` that is an HTTPS URL (e.g., `https://mcp-client.example.com/client-metadata`) 2. Authorization server fetches the metadata document from that URL 3. Authorization server validates the client's configuration from the document 4. Authorization server uses the metadata for the OAuth flow ## Validation Rules When fetching and processing client metadata documents, the authorization server MUST: | Rule | Details | |---|---| | Fetch over HTTPS | Only retrieve metadata from HTTPS URLs | | Verify `client_id` match | The `client_id` in the document must match the URL it was fetched from | | Validate `redirect_uris` | Ensure redirect URIs are valid and use HTTPS | | Check grant types | Only allow grant types the server supports | | Apply security policies | Enforce server-side policies on client configurations | ## Implementation Checklist - [ ] Accept `client_id` values that are HTTPS URLs - [ ] Fetch client metadata documents from the `client_id` URL - [ ] Validate the `client_id` field in the document matches the fetch URL - [ ] Validate `redirect_uris` for security (HTTPS, no wildcards) - [ ] Apply rate limiting on metadata document fetches - [ ] Cache fetched metadata with appropriate TTL - [ ] Reject metadata documents that fail validation - [ ] Log client metadata fetch attempts for audit
Versions
The database has no other skills named client-metadata-support.
Database snapshot: 13.11.2026 · package version d86c4269e42b (SHA-256 digest of the entire package)
Downloads in the last 30 days: 0 · ranking
Report a problem with this skill: harmful content, incorrect descriptions or an author’s removal request.
Similar skills
- 100mcp-client-client-metadata-support
Support OAuth Client ID Metadata Documents in MCP clients. Use when building or reviewing MCP client registration and identity presentation to authorization servers. - 100dynamic-client-registration
Support OAuth 2.0 Dynamic Client Registration in authorization servers. Use when building or reviewing authorization server client management for MCP ecosystems. - 100mcp-oauth-setup
Implement MCP server authentication with OAuth Dynamic Client Registration (RFC 7591), Authorization Server Metadata Discovery (RFC 8414), and generalized per-agent credential support. This skill should be used when building admin UIs that let users connect to third-party MCP… - 100oauth
Expert OAuth 2.0 / 2.1 protocol assistance covering Authorization Code Flow with PKCE, Client Credentials, and token exchange. Use when implementing third-party logins, securing API endpoints, or configuring OAuth servers. - 100spring-authorization-server
Spring Authorization Server for building OAuth 2.1 and OpenID Connect providers. USE WHEN: user mentions "OAuth2 server", "authorization server", "OIDC provider", "token endpoint", asks about "how to implement OAuth2", "create authorization server", "issue JWT tokens", "custom… - 100oauth-2-0-setup
Implement OAuth 2.0 authentication flows including authorization code with PKCE, client credentials, and device code for secure API integration. Use when the user requests oauth 2 0 setup or provides relevant inputs for this workflow.