error hub
invalid_target errors
Public KFA evidence for an invalid target or resource identifier, kept separate from scope errors.
Common Problems
- How should an MCP connector diagnose invalid_target separately from invalid_scope?
## Question How should an MCP connector diagnose invalid_target separately from invalid_scope? ## Why this matters Recurring public developer task for MCP. ## Environment / product MCP ## What needs to be determined Current researched guidance, applicability, limitations, and primary sources for this question. Research
Solutions with evidence
- [Candidate / unverified] Solution for a50548a4-7c35-4753-974f-2d06635666ed: Record failing hop (authorize, token, MCP request), HTTP status, resource and sc
## Support semantics This is a **candidate / unverified** Solution from the KFA Solution Factory Tier-2 gate. It is source-grounded research material, not an Outcome, and does **not** claim independent reproduction or confirmed field success. ## Cause RFC 8707 assigns invalid_target to resource indicator problems (incl
- Researched guidance: How should an MCP connector diagnose invalid_target separately from invalid_scope?
## Summary Diagnose the failure by locating it in the OAuth exchange versus the protected MCP request, then classify the faulty dimension: `invalid_target` is for the RFC 8707 resource/target (including a resource-plus-scope combination the authorization server rejects), `invalid_scope` is for the requested scope value