Client Metadata Support

Organization

RedHatProductSecurity

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.

Overview

Publisher	RedHatProductSecurity
Repository	`prodsec-skills`
Skill name	`client-metadata-support`
Stars	56
Forks	9
Bundled files	Instructions only
License	Apache-2.0
Links	Skill source Repository

Markdown instructions
A SKILL.md file the model loads on demand, so it only costs tokens when a request actually matches.
Works with any LLM
AI skills are plain Markdown, not provider-specific code, so this works with GPT, Claude, Gemini, Grok, or a local model.
Self-contained
Everything the model needs lives in the instructions — no extra files to sync.
Open source
Published by RedHatProductSecurity on GitHub. Read the source before you install it.

Installation

Install the Client Metadata Support AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

Install in TypingMind

TypingMind installs a skill straight from its GitHub folder — it reads SKILL.md, bundles the resource files, and stores the result locally.

Open the app and go to Plugins → Skills.
Choose "Install from GitHub".
Paste the skill folder URL below and confirm.
https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/client-metadata-support
Enable the skill in any chat where you want it available.

Store

Installed

Skills

Add skills

Import one or more skills from a public GitHub folder or a local .skill or .zip archive, or SKILL.md file.

From GitHub URLFrom .skill, .zip, or SKILL.md

GitHub repo or folder

https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/client-metadata-support

Points to a single skill folder, or any folder that contains multiple skills. Public repos only.

CancelContinue

Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.

Install in another agent

Any agent that reads the Agent Skills format can use this skill — copy the folder into that agent's skills directory.

Claude Code — .claude/skills

git clone --depth 1 https://github.com/RedHatProductSecurity/prodsec-skills.git /tmp/prodsec-skills
mkdir -p .claude/skills
cp -r /tmp/prodsec-skills/module/skills/client-metadata-support .claude/skills/client-metadata-support

Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Client Metadata Support in any TypingMind chat and the model takes it from there. Its name and description sit in the system prompt, and the moment a request matches, the model loads the full instructions itself — you never invoke it by hand, and it costs no tokens until it is actually used.

The model loads Client Metadata Support on its own as soon as a request matches it.

Works with any AI model

AI skills are plain Markdown instructions rather than provider-specific code, so Client Metadata Support is not tied to the model it was written for. Install it once in TypingMind and use it with GPT-5, Claude, Gemini, Grok, DeepSeek, Mistral, Llama, or a local model you run yourself — all on your own API keys.

Loaded only when it is needed
The system prompt carries just the name and description. The instructions are fetched on the first matching request, so an idle skill costs nothing.
Switch models mid-chat
Because the skill is instructions rather than code, changing model does not break it — the next model reads the same SKILL.md.

Skill instructions

This is the SKILL.md content the model loads. Read it before installing — a skill is instructions your model will follow.

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

Client presents a client_id that is an HTTPS URL (e.g., https://mcp-client.example.com/client-metadata)
Authorization server fetches the metadata document from that URL
Authorization server validates the client's configuration from the document
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

Frequently asked questions

What does the Client Metadata Support AI skill do?

Support OAuth Client ID Metadata Documents in authorization servers. Use when building or reviewing authorization server client validation and registration mechanisms for MCP ecosystems.

Why use Client Metadata Support on TypingMind?

Because you install it once and use it with any model. Client Metadata Support is plain Markdown rather than provider-specific code, so the same skill runs on GPT-5, Claude, Gemini, Grok, or a local model — and you can switch model mid-chat without it breaking. TypingMind runs on your own API keys, so you pay providers directly instead of a per-seat subscription, and your skills and chats stay in your own storage.

How do I install Client Metadata Support in TypingMind?

Open Plugins → Skills → Install from GitHub in TypingMind and paste https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/client-metadata-support. TypingMind reads its SKILL.md and installs it as a skill you can enable per chat.

Which AI models can use Client Metadata Support?

Any model you connect in TypingMind. AI skills are plain Markdown instructions rather than provider-specific code, so GPT, Claude, Gemini, Grok, and local models can all load this skill when a request matches it.

How many AI models can I use with Client Metadata Support?

As many as you like. As long as a model supports skills, you can use Client Metadata Support with it — GPT, Claude, Gemini, Grok, DeepSeek, Mistral, Llama and more — all on TypingMind with your own API keys.

Is the Client Metadata Support AI skill free?

Yes. It is published on GitHub by RedHatProductSecurity under the Apache-2.0 license. You only pay your own AI provider for the tokens you use.

What are AI skills?

An AI skill is a reusable instruction bundle that teaches an AI model how to do one specific task. It follows the open Agent Skills format: a SKILL.md file with a name and description, plus any scripts, templates or reference files the model may need. The model reads the instructions only when your request matches the skill, so an installed skill costs nothing until it is used.

How are AI skills different from plugins or MCP servers?

A plugin or MCP server gives a model new tools to call — code that runs somewhere and returns a result. An AI skill gives the model knowledge and process instead: how to approach a task, which steps to follow, what good output looks like. Skills are plain Markdown, so they need no server, no API key and no runtime, and they work with any model.

View all

Antigravity Cli

NousResearch

OrganizationPopular

Operate the Antigravity CLI (agy): plugins, auth, sandbox.

Backend Code Review

Use only when the user explicitly requests a review or audit of backend code under `api/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for implementation-only requests,…

Frontend Code Review

Use only when the user explicitly requests a review or audit of frontend code under `web/` or `packages/dify-ui/`. Supports pending-change, file-focused, and pasted-diff reviews. Do not use for…

Command Development

This skill should be used when the user asks to "create a slash command", "add a command", "write a custom command", "define command arguments", "use command frontmatter", "organize commands", "create…

Overview

Installation

Install in TypingMind

Install in another agent

Use it in TypingMind

Works with any AI model

Skill instructions

OAuth Client ID Metadata Document Support in Authorization Servers

Security Recommendation

How It Works

Validation Rules

Implementation Checklist

Frequently asked questions

Related AI Skills

Set up your own AI workspace now