Server
Atlassian
- Endpoint
https://mcp.atlassian.com/v2/mcp- Transport
- Streamable HTTP
- Access
- Public Anyone can connect; where an account is needed, anyone can create one by self-service sign-up. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · Requires only an Atlassian Cloud site with Jira, Compass or Confluence and a browser for the OAuth flow.
- Auth
- OAuth An OAuth 2.x authorization obtained through the server's authorization server. Manual check · jbspeakr (documentation pass with Claude Code) · · evidence · OAuth 2.1 authorization code with user consent is the recommended method; an API token is accepted only if the org admin has enabled it.
- Why it is listed
- Listed because it appears in a public directory of MCP servers. Source
- Homepage
- https://atlassian.com
Against MCP Authorization 2026-07-28current
- Supported 11
- Unsupported 3
- Unknown 9
Passive scanGrade C · · Report
Older revisions of the matrix: 2025-11-25
MCP server features 13
| Feature | Level | Status | Observed | Evidence |
|---|---|---|---|---|
| Protected Resource Metadata served | MUST | Supported | source1 earlier observation
| |
| PRM lists an authorization server | MUST | Supported | source1 earlier observation
| |
| PRM lists scopes_supported | MAY | Supported | source1 earlier observation
| |
| PRM reachable at a well-known URI | MUST | Supported | source1 earlier observation
| |
| resource_metadata in the 401 challenge | MUST | Supported | source1 earlier observation
| |
| 403 insufficient_scope for step-up | SHOULD | Unknown no observation | no observation yet | |
| Scope in the WWW-Authenticate challenge | SHOULD | Unsupported | source | |
| No offline_access in advertised scopes | SHOULD | Unsupported | source1 earlier observation
| |
| 401 for missing or invalid tokens | MUST | Unknown no observation | no observation yet | |
| Audience validation | MUST | Unknown no observation | no observation yet | |
| Bearer token only in the Authorization header | MUST | Unknown no observation | no observation yet | |
| No token passthrough to upstream APIs | MUST | Unknown no observation | no observation yet | |
| Per-client consent on proxy servers | MUST | Unknown no observation | no observation yet |
Authorization server features 10
| Feature | Level | Status | Observed | Evidence |
|---|---|---|---|---|
| Metadata issuer matches the discovery URL | MUST | Supported | source1 earlier observation
| |
| Authorization server metadata discoverable | MUST | Supported | source1 earlier observation
| |
| Client ID Metadata Documents supported | SHOULD | Supported | source1 earlier observation
| |
| Dynamic Client Registration offered | MAY | Supported | source | |
| Documented pre-registration path | SHOULD | Unknown no observation | no observation yet | |
| Issuer identifier in authorization responses | SHOULD | Unsupported | source1 earlier observation
| |
| PKCE with S256 advertised | MUST | Supported | source1 earlier observation
| |
| Refresh token rotation for public clients | MUST | Unknown no observation | no observation yet | |
| Resource indicators honoured | MUST | Unknown no observation | no observation yet | |
| All endpoints served over HTTPS | MUST | Supported | source1 earlier observation
|