mcp-auth-exploitation SKILL.md skillB
mcp-auth-exploitation from dreadnode/capabilities is an agent skill: a SKILL.md folder an AI agent loads when a task calls for it.
mdr add dreadnode/capabilities/mcp-auth-exploitation@git:20260529.0ab6ab0Pins git:20260529.0ab6ab0 in mdr.lock. Pin the fingerprint instead.
- Audit grade
- B, 16 of 17 checks passed
- Kind
- SKILL.md skill
- Repository
- dreadnode/capabilities
- Path
capabilities/web-security/skills/mcp-auth-exploitation/SKILL.md- Versions recorded
- 3
- Latest version
- git:20260529.0ab6ab0, committed May 29, 2026
- First version recorded
- May 4, 2026
- Size
- 9,795 bytes
- Repository stars
- 22
- License
- MIT
Exploit MCP authorization flows — CIMD SSRF via client_manifest_uri/logo_uri/jwks_uri, Dynamic Client Registration abuse, token scope inflation in multi-agent chains, confused deputy attacks. Use when target exposes MCP authorization, OIDC Dynamic Client Registration (RFC 7591), or multi-agent token delegation.
Collected from public GitHub. Every version is saved exactly as it was and never changes. Install it at an exact version with the mdr tool, and every file is checked before it reaches your agent. The main file is checked against the SHA-256 fingerprint recorded here, and the others against the fingerprints GitHub keeps for its source commit. The automatic checks below grade the latest version, and the same checks always give the same file the same grade.
What the file says
# MCP Authorization & Dynamic Client Registration Exploitation Covers two related attack surfaces: (1) MCP's Client Identity Metadata Documents (CIMD) architecture where authorization servers fetch attacker-controlled manifests, and (2) RFC 7591 Dynamic Client Registration (DCR) abuse on any OAuth/OIDC stack. Both share the same core primitive: the server makes outbound requests to attacker-specified URLs and trusts attacker-supplied metadata. ## When to Use - `/.well-known/openid-configuration` exposes a `registration_endpoint` - Target implements MCP authorization with `client_manifest_uri` support - Multi-agent/tool architecture where tokens pass across service boundaries - OAuth server accepts `client_metadata` or `client_metadata_uri` parameters - Any OIDC provider with open or semi-open dynamic registration ## 1. Reconnaissance: Find Registration Surfaces ### OIDC Discovery ```bash # Check for registration_endpoint in OIDC config curl -s https://TARGET/.well-known/openid-configuration | jq '.registration_endpoint, .grant_types_supported, .token_endpoint' # Also check OAuth-specific metadata …
Read the whole file at its exact version.
How to install
mdr add dreadnode/capabilities/mcp-auth-exploitation@sha256:9300596c527d3da5The line at the top of this page pins the label git:20260529.0ab6ab0, which is what most people want. This one pins the sha256 fingerprint of the contents instead, so it survives a label being moved. Either way the exact version is written to mdr.lock, and mdr install downloads and checks those contents again, so it installs them exactly or stops with an error.
[](https://markdownregistry.com/a/art_dzwo24ayif4zo7js)
3 badge image fetches in 30 days. What the badge shows.
Versions
The registry has recorded 3 versions of this file, between May 4, 2026 and May 29, 2026, about one every 13 days.
| version | committed | commit | size | audit | |
|---|---|---|---|---|---|
| git:20260529.0ab6ab0 latest | 2026-05-29 | 0ab6ab0 | 9,795 B | B | view · diff |
| git:20260529.8f6ea0e | 2026-05-29 | 8f6ea0e | 10,256 B | B | view · diff |
| git:20260504.2a64374 | 2026-05-04 | 2a64374 | 10,185 B | B | view |
Audit of the latest version
- fail: No link to a raw IP address (matched: http://169.254.169.254)
- pass: Frontmatter block present
- pass: Frontmatter declares a name
- pass: Frontmatter declares a description
- pass: Size between 200 bytes and 200 KB (9795 bytes)
- pass: No zero-width or bidi control characters
- pass: No instruction hidden inside an HTML comment
- pass: No link to an exfiltration or paste host
- pass: No credential-shaped string
- pass: No instruction to send local credentials anywhere
- pass: No text hidden with inline styles
- pass: No prompt-injection phrasing
- pass: No curl or wget piped into a shell
- pass: No recursive delete of root, home or parent
- pass: No instruction to read or print local credentials
- pass: No base64 blob over 200 characters
- pass: No script tag
Starting a new one? Use a template for SKILL.md on mdpantry, which passes every one of these checks and says what to change in it.
Source
dreadnode/capabilities · 22 stars · license MIT · pushed 2026-11-02 · branch main
API
GET https://markdownregistry.com/api/v1/artifacts/art_dzwo24ayif4zo7js GET https://markdownregistry.com/api/v1/resolve?ref=dreadnode/capabilities/mcp-auth-exploitation GET https://markdownregistry.com/api/v1/blob/9300596c527d3da576f9fbc111071a32e473fdb859f2bdf05dc44e463cc6bb0a
Your AI assistant does the legwork. You hear about the deals worth your word. Hand yours the standing instructions at modelranch.com and it joins the network that reads files like this one.
Guides: the SKILL.md format and its required fields · what to check before you install a skill · how to pin a skill to an exact version · where to find agent skills · keeping a team on the same skills · which agent file does what.