Mcp Client Protected Resource Metadata logo

Mcp Client Protected Resource Metadata

Organization
RedHatProductSecurity
mcp-client-protected-resource-metadata

Enforce use of OAuth 2.0 Protected Resource Metadata in MCP clients for discovering authorization servers. Use when building or reviewing MCP client authentication flows and authorization server discovery.

Overview

PublisherRedHatProductSecurity
Repositoryprodsec-skills
Skill namemcp-client-protected-resource-metadata
Stars
56
Forks
9
Bundled files
Instructions only
LicenseApache-2.0
Links
  • 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 Mcp Client Protected Resource Metadata AI skill in TypingMind to use it with any LLM, or drop it into another agent that reads SKILL.md.

1

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.

  1. Open the app and go to Plugins → Skills.
  2. Choose "Install from GitHub".
  3. Paste the skill folder URL below and confirm.
    https://github.com/RedHatProductSecurity/prodsec-skills/tree/main/module/skills/mcp-client-protected-resource-metadata
  4. Enable the skill in any chat where you want it available.
Plugins → Skills → Add skill → From GitHub URL, then paste the folder URL and press Continue.
2

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/mcp-client-protected-resource-metadata .claude/skills/mcp-client-protected-resource-metadata
Restart Claude Code after copying so it picks up the new skill.

Use it in TypingMind

Enable Mcp Client Protected Resource Metadata 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 Mcp Client Protected Resource Metadata 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 Mcp Client Protected Resource Metadata 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.

Protected Resource Metadata Usage in MCP Clients

Security Requirement

MCP clients MUST use OAuth 2.0 Protected Resource Metadata (RFC 9728) to discover the authorized authorization servers for any MCP server they connect to. Clients MUST NOT hardcode or manually configure authorization server URLs when the MCP server provides Protected Resource Metadata.

Discovery Flow

1. MCP client attempts to access MCP server resource
2. MCP server returns 401 with WWW-Authenticate header
3. MCP client fetches /.well-known/oauth-protected-resource from MCP server
4. Extract authorization_servers list from the metadata
5. Use the authorization server(s) listed for token acquisition
6. Authenticate with the authorization server and obtain token
7. Retry the original request with the obtained token

Metadata Fields to Consume

FieldUsage
authorization_serversList of trusted authorization server URLs to use
scopes_supportedAvailable scopes to request during authorization
bearer_methods_supportedHow to present the bearer token (e.g., header)

Implementation Checklist

  • On 401 response, fetch /.well-known/oauth-protected-resource from the MCP server
  • Parse the authorization_servers field and select appropriate server
  • Use scopes_supported to inform scope requests
  • Respect bearer_methods_supported when presenting tokens
  • Cache the metadata with appropriate TTL to avoid repeated lookups
  • Re-fetch metadata when authorization fails after token refresh

Frequently asked questions

What does the Mcp Client Protected Resource Metadata AI skill do?

Enforce use of OAuth 2.0 Protected Resource Metadata in MCP clients for discovering authorization servers. Use when building or reviewing MCP client authentication flows and authorization server discovery.

Why use Mcp Client Protected Resource Metadata on TypingMind?

Because you install it once and use it with any model. Mcp Client Protected Resource Metadata 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 Mcp Client Protected Resource Metadata in TypingMind?

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

Which AI models can use Mcp Client Protected Resource Metadata?

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 Mcp Client Protected Resource Metadata?

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

Is the Mcp Client Protected Resource Metadata 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

Set up your own AI workspace now

Get notified about new features and future giveaways by subscribing to our newsletter 👇