Medium
Sign-in metadata names another resource
MCPS-AUTH-005Why it mattersThe resource field must be the server's own address (RFC 9728, Section 3.3). Clients that follow the RFC throw the document away, and a mismatch is how one server gets passed off as another.
How to fixSet resource to this endpoint's exact address.
- Request
GET https://asset-management.mcp.cloudinary.com/.well-known/oauth-protected-resource- What we saw
resource: https://asset-management.mcp.cloudinary.com (expected https://asset-management.mcp.cloudinary.com/mcp)
Seen in the server's answer
SpecRFC 9728, Section 3.3 (Protected Resource Metadata Validation)
Low
No Strict-Transport-Security header
MCPS-HDR-001Why it mattersWithout it, an attacker can keep a browser on plain HTTP on any later visit. HSTS makes the browser use HTTPS only.
How to fixSend Strict-Transport-Security: max-age=31536000 on every HTTPS response.
return new Response(body, { headers: { 'Strict-Transport-Security': 'max-age=31536000; includeSubDomains' } })app.use((req, res, next) => { res.setHeader('Strict-Transport-Security', 'max-age=31536000; includeSubDomains'); next() })- Request
POST https://asset-management.mcp.cloudinary.com/mcp (initialize)- Answer
401- What we saw
no Strict-Transport-Security
Seen in the server's answer
SpecRFC 6797 (HTTP Strict Transport Security)
Low
No X-Content-Type-Options: nosniff
MCPS-HDR-002Why it mattersA browser may guess a response's type and render JSON or text as HTML or script.
How to fixSend X-Content-Type-Options: nosniff on every response.
res.setHeader('X-Content-Type-Options', 'nosniff')- Request
POST https://asset-management.mcp.cloudinary.com/mcp (initialize)- Answer
401- What we saw
no X-Content-Type-Options: nosniff
Seen in the server's answer
SpecFetch Standard, X-Content-Type-Options
Low
PKCE plain method offered
MCPS-AUTH-008Why it mattersWith plain, the challenge equals the secret, so anyone who sees the request sees the secret.
How to fixOffer S256 only.
- Request
GET https://asset-management.mcp.cloudinary.com/.well-known/oauth-authorization-server- What we saw
code_challenge_methods_supported: ["S256","plain"]
Seen in the server's answer
SpecRFC 9700, Section 2.1.1 (PKCE: S256)
Low
Issuer in the authorization response not advertised
MCPS-AUTH-011Why it mattersReturning iss (RFC 9207) lets a client tell which server answered, which stops mix-up attacks between servers. The MCP spec says SHOULD now and expects a future revision to make it MUST.
How to fixReturn iss in authorization responses and set authorization_response_iss_parameter_supported to true.
- Request
GET https://asset-management.mcp.cloudinary.com/.well-known/oauth-authorization-server- What we saw
authorization_response_iss_parameter_supported: null
Seen in the server's answer
SpecMCP 2026-07-28, Authorization: Authorization Response ValidationRFC 9207, Section 2.3
Low
Refresh tokens without an advertised revocation endpoint
MCPS-AUTH-012Why it mattersA long-lived refresh token that leaks keeps working until it expires.
How to fixPublish a revocation_endpoint (RFC 7009) and rotate refresh tokens.
- Request
GET https://asset-management.mcp.cloudinary.com/.well-known/oauth-authorization-server- What we saw
refresh_token granted; no revocation_endpoint
Seen in the server's answer
SpecRFC 7009 (Token Revocation); RFC 8414, Section 2 (revocation_endpoint)