{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"confluence-mcp-server","slug":"confluence-mcp-server","name":"Confluence MCP Server","type":"mcp","url":"https://github.com/sooperset/mcp-atlassian","page_url":"https://unfragile.ai/confluence-mcp-server","categories":["mcp-servers"],"tags":["confluence","atlassian","wiki","community"],"pricing":{"model":"free","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"confluence-mcp-server__cap_0","uri":"capability://search.retrieval.confluence.full.text.page.search.with.jql.style.filtering","name":"confluence full-text page search with jql-style filtering","description":"Enables semantic and keyword-based search across Confluence pages using the Confluence Search API with support for CQL (Confluence Query Language) filters. The implementation wraps the native Confluence search endpoint with parameter marshaling for space filtering, content type restrictions, and result pagination, returning structured page metadata including page IDs, titles, spaces, and excerpt snippets. Supports both Cloud and Server/Data Center deployments with automatic API format adaptation.","intents":["Find documentation pages matching specific keywords or topics across multiple spaces","Retrieve pages from a specific Confluence space filtered by content type or modification date","Build AI-driven documentation retrieval pipelines that feed search results into LLM context windows"],"best_for":["Teams building AI agents that need to retrieve Confluence documentation as context","Documentation-heavy organizations automating knowledge discovery workflows","Developers integrating Confluence as a knowledge base for RAG systems"],"limitations":["Search results limited to 50 items per request by default; requires pagination for larger result sets","CQL filter syntax varies between Cloud and Server/Data Center; server-specific filters may not translate","No full-text indexing optimization — relies on Confluence's native search performance which can be slow on large instances"],"requires":["Confluence Cloud (*.atlassian.net) or Server/Data Center instance","API token or OAuth 2.0 credentials with read access to target spaces","Network connectivity to Confluence instance"],"input_types":["text (search query string)","text (CQL filter expression)","text (space key for filtering)"],"output_types":["structured JSON (page metadata with ID, title, space, excerpt, URL)"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_1","uri":"capability://text.generation.language.confluence.page.creation.and.hierarchical.content.authoring","name":"confluence page creation and hierarchical content authoring","description":"Enables AI agents to create new Confluence pages with full support for parent-child page hierarchies, content formatting (HTML/XHTML), and metadata assignment. The implementation uses the Confluence Content API with automatic body format detection (storage format for Server/Data Center, rich text format for Cloud), parent page resolution, and space assignment. Supports inline attachments, labels, and custom properties through the underlying Confluence API schema.","intents":["Generate and publish documentation pages programmatically from AI-generated content","Create nested page hierarchies for structured documentation (e.g., API docs with method pages as children)","Automate wiki page creation as part of CI/CD or knowledge management workflows"],"best_for":["AI-powered documentation generation systems that need to publish directly to Confluence","Teams automating knowledge base population from structured data or AI outputs","Developers building content management workflows that treat Confluence as a content sink"],"limitations":["Content format differs between Cloud (rich text) and Server/Data Center (storage format); requires format-specific HTML/XHTML markup","Parent page resolution requires exact page title or ID; no fuzzy matching for parent lookup","No built-in conflict detection — concurrent page creation with identical titles may cause unexpected behavior","Attachment embedding requires separate API calls; inline attachment references must be pre-uploaded"],"requires":["Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with write access to target space","Valid space key and (optionally) parent page ID for hierarchical placement"],"input_types":["text (page title)","text (page body in HTML or storage format)","text (space key)","text (parent page ID for hierarchy)"],"output_types":["structured JSON (created page metadata including page ID, URL, version)"],"categories":["text-generation-language","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_10","uri":"capability://tool.use.integration.tool.registration.and.discovery.with.dependency.injection","name":"tool registration and discovery with dependency injection","description":"Registers 72 Confluence and Jira tools with FastMCP framework using dependency injection pattern for client instantiation and configuration. The implementation uses FastMCP's tool decorator system to expose tools with automatic schema generation, parameter validation, and error handling. Supports tool access control through permission decorators and conditional tool availability based on deployment type or authentication method.","intents":["Expose Confluence and Jira capabilities as discoverable MCP tools to AI clients","Automatically generate tool schemas for AI model understanding","Implement tool access control and permission-based tool filtering"],"best_for":["AI platforms integrating Confluence/Jira through MCP protocol","Teams building custom tool registries with dynamic tool availability","Developers extending MCP server with custom tools"],"limitations":["Tool schema generation is static; no dynamic schema updates based on Confluence/Jira custom fields","Access control decorators are coarse-grained (tool-level); no field-level or operation-level permissions","Tool registration happens at server startup; no hot-reload for new tools without restart","Parameter validation uses JSON schema; complex validation logic requires custom decorators"],"requires":["FastMCP framework","Python 3.9+","Tool definitions in src/mcp_atlassian/servers/jira.py and confluence.py"],"input_types":["tool definitions with schema"],"output_types":["MCP tool discovery messages with schema"],"categories":["tool-use-integration","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_11","uri":"capability://tool.use.integration.jira.issue.creation.and.field.management","name":"jira issue creation and field management","description":"Enables creating Jira issues with full support for custom fields, issue types, projects, and field validation. The implementation uses the Jira Create Issue API with automatic field schema discovery, type coercion, and validation error reporting. Supports both Cloud and Server/Data Center with field name mapping and custom field ID resolution.","intents":["Create Jira issues programmatically from AI-generated content or external systems","Populate custom fields with structured data during issue creation","Validate field values against Jira schema before submission"],"best_for":["AI agents that need to create issues from documentation or user requests","Automation systems that generate Jira issues from external data sources","Teams building issue creation workflows with custom field support"],"limitations":["Custom field IDs differ between Cloud and Server/DC instances; no cross-instance field mapping","Field validation errors are generic; no detailed error messages for complex field types","Issue creation does not support bulk operations; each issue requires separate API call","No automatic issue linking or epic assignment in single call; requires separate API calls"],"requires":["Jira Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with issue creation permission","Valid project key and issue type"],"input_types":["text (issue summary)","text (issue description)","text (project key)","text (issue type)","structured data (custom fields)"],"output_types":["structured JSON (created issue metadata with key, ID, URL)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_12","uri":"capability://search.retrieval.jira.issue.search.and.jql.query.execution","name":"jira issue search and jql query execution","description":"Enables searching Jira issues using JQL (Jira Query Language) with support for complex filters, sorting, and result pagination. The implementation wraps the Jira Search API with JQL validation, result expansion (issue details, changelog, comments), and automatic pagination handling. Supports both Cloud and Server/Data Center with JQL dialect adaptation.","intents":["Find Jira issues matching specific criteria (assignee, status, labels, custom fields)","Retrieve issue details for AI analysis or summarization","Build issue collections for reporting or bulk operations"],"best_for":["AI agents that need to search Jira for context or decision-making","Reporting systems that aggregate issues by criteria","Automation workflows that operate on filtered issue sets"],"limitations":["JQL syntax errors return generic error messages; no JQL validation or suggestion","Search results limited to 50 items per request; pagination requires separate calls","Complex JQL queries with many conditions may timeout on large instances","Result expansion (changelog, comments) adds latency; no streaming for large result sets"],"requires":["Jira Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with issue search permission","Valid JQL query syntax"],"input_types":["text (JQL query)"],"output_types":["structured JSON (issue list with metadata, changelog, comments)"],"categories":["search-retrieval","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_13","uri":"capability://tool.use.integration.jira.issue.updates.and.workflow.transitions","name":"jira issue updates and workflow transitions","description":"Enables updating Jira issues (fields, status, assignee) and executing workflow transitions with automatic permission checking and field validation. The implementation uses the Jira Update Issue API with support for bulk field updates, transition execution with required field validation, and changelog tracking. Supports both Cloud and Server/Data Center with field name mapping.","intents":["Update issue fields (assignee, labels, custom fields) programmatically","Transition issues through workflow states (e.g., Open → In Progress → Done)","Implement automation workflows that modify issues based on conditions"],"best_for":["Automation systems that need to update issues based on external events","AI agents that modify issues as part of task execution","Workflow automation that transitions issues through states"],"limitations":["Bulk field updates in single call may fail partially; no transaction semantics for multi-field updates","Workflow transition validation requires separate API call to fetch available transitions","Field update permissions are checked per-field; no bulk permission check before update","No automatic changelog generation; update history relies on Jira's native audit trail"],"requires":["Jira Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with issue update permission","Valid issue key and field names"],"input_types":["text (issue key)","structured data (field updates)","text (transition name)"],"output_types":["structured JSON (updated issue metadata)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_2","uri":"capability://memory.knowledge.confluence.page.content.reading.with.format.normalization","name":"confluence page content reading with format normalization","description":"Retrieves full page content from Confluence with automatic format normalization across Cloud and Server/Data Center deployments. The implementation fetches pages via the Content API with expand parameters for body content, metadata, and version history, then normalizes storage format (Server/DC) or rich text format (Cloud) into a consistent representation. Includes support for retrieving page hierarchies, child pages, and version history metadata.","intents":["Fetch full documentation pages to feed into LLM context for analysis or summarization","Retrieve page version history to track documentation changes over time","Build page hierarchy trees to understand documentation structure"],"best_for":["AI agents that need to read and analyze Confluence documentation as context","Documentation audit systems that track page changes and modifications","Knowledge base systems that need to understand page relationships and hierarchies"],"limitations":["Large pages (>1MB content) may timeout or return truncated results; no streaming support for massive pages","Format normalization is lossy — complex macros, embedded content, and custom formatting may not survive conversion","Version history retrieval limited to 50 versions per request; full history requires pagination","Child page retrieval does not recursively fetch nested hierarchies — requires separate calls per level"],"requires":["Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with read access to target page","Valid page ID or page title + space key for lookup"],"input_types":["text (page ID)","text (page title + space key)"],"output_types":["structured JSON (page metadata, normalized body content, version history, child pages)"],"categories":["memory-knowledge","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_3","uri":"capability://search.retrieval.confluence.space.and.page.hierarchy.traversal","name":"confluence space and page hierarchy traversal","description":"Enables navigation and discovery of Confluence space structures, page hierarchies, and content organization through tools that list spaces, retrieve page trees, and resolve parent-child relationships. The implementation uses the Confluence Content API with recursive expansion parameters to fetch page hierarchies, space metadata, and permission information. Supports filtering by space type (global, personal) and pagination for large hierarchies.","intents":["Discover available Confluence spaces and their organization structure","Build page tree representations to understand documentation hierarchy","Resolve parent-child page relationships for context-aware navigation"],"best_for":["AI agents that need to understand Confluence workspace structure before performing operations","Documentation mapping tools that visualize wiki hierarchies","Systems automating bulk operations across multiple spaces or page hierarchies"],"limitations":["Recursive hierarchy expansion limited to 3-4 levels deep; deeper nesting requires separate API calls per level","Space listing returns only spaces the authenticated user can access; no admin override for full workspace visibility","Page tree expansion does not include page content — requires separate content fetch calls for each page","No caching of hierarchy data; repeated traversals result in multiple API calls with no deduplication"],"requires":["Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with read access to spaces","Valid space key for hierarchy traversal"],"input_types":["text (space key)","text (page ID for subtree expansion)"],"output_types":["structured JSON (space metadata, page tree with hierarchical nesting, permission info)"],"categories":["search-retrieval","memory-knowledge"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_4","uri":"capability://text.generation.language.confluence.page.comments.and.discussion.management","name":"confluence page comments and discussion management","description":"Enables reading, creating, and managing comments on Confluence pages through tools that fetch comment threads, post new comments, and update existing comments. The implementation uses the Confluence Comments API with support for nested replies, mention resolution (@username), and comment metadata (author, timestamp, edit history). Supports both inline comments and page-level discussions.","intents":["Retrieve discussion threads on documentation pages to understand feedback and questions","Post AI-generated responses or clarifications as comments on pages","Build discussion-aware documentation systems that incorporate community feedback"],"best_for":["Collaborative documentation systems that need to surface and respond to page discussions","AI agents that need to understand page-level feedback and questions","Knowledge management systems that track documentation discussions"],"limitations":["Nested reply depth limited to 2 levels in API responses; deeper threads require separate calls","Mention resolution (@username) requires exact username match; no fuzzy user lookup","Comment editing limited to original author or admins; no delegation of edit permissions","No bulk comment operations — each comment requires separate API call"],"requires":["Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with read/write access to page comments","Valid page ID for comment operations"],"input_types":["text (page ID)","text (comment body with optional @mentions)","text (comment ID for updates)"],"output_types":["structured JSON (comment threads with metadata, author info, timestamps)"],"categories":["text-generation-language","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_5","uri":"capability://data.processing.analysis.confluence.page.labels.and.metadata.tagging","name":"confluence page labels and metadata tagging","description":"Enables adding, removing, and querying labels (tags) on Confluence pages for content organization and discovery. The implementation uses the Confluence Labels API to manage page labels, retrieve pages by label, and support label hierarchies (prefix-based organization like 'team:backend', 'status:draft'). Supports bulk label operations and label-based filtering in search queries.","intents":["Tag AI-generated or modified pages with metadata labels for organization","Retrieve pages by label to build label-based content collections","Implement status tracking (draft, reviewed, published) through label conventions"],"best_for":["Documentation systems using labels for content classification and workflow tracking","Teams implementing label-based content organization (e.g., 'team:*', 'status:*')","AI systems that need to categorize and organize generated content"],"limitations":["Label hierarchies are convention-based (prefix matching) with no enforced schema; no validation of label format","Bulk label operations require separate API calls per page; no batch label assignment","Label search limited to exact match or prefix; no fuzzy label matching","No label deletion cascade — removing a label from all pages requires manual iteration"],"requires":["Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with write access to page labels","Valid page ID for label operations"],"input_types":["text (label name)","text (page ID)"],"output_types":["structured JSON (label metadata, pages with matching labels)"],"categories":["data-processing-analysis","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_6","uri":"capability://tool.use.integration.confluence.page.attachments.and.file.management","name":"confluence page attachments and file management","description":"Enables uploading, downloading, and managing file attachments on Confluence pages through tools that handle file I/O, attachment metadata, and version tracking. The implementation uses the Confluence Attachments API with support for multipart file uploads, attachment versioning, and metadata (filename, size, MIME type, upload timestamp). Supports both Cloud and Server/Data Center with automatic format adaptation.","intents":["Upload generated files (PDFs, images, documents) as page attachments","Retrieve attachment metadata and download URLs for embedded content","Track attachment versions and manage file updates on pages"],"best_for":["Documentation systems that need to embed generated files (diagrams, reports, exports)","AI agents that produce file outputs and need to attach them to pages","Content management workflows that track file versions and modifications"],"limitations":["File size limits enforced by Confluence instance (typically 250MB Cloud, configurable Server/DC); no chunked upload for large files","Attachment versioning limited to 10 versions per file by default; older versions may be purged","No direct file streaming — entire file must be loaded into memory for upload","Attachment download URLs are temporary; no persistent direct links"],"requires":["Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with write access to page attachments","Valid page ID for attachment operations","File path or binary content for upload"],"input_types":["binary (file content)","text (filename)","text (MIME type)"],"output_types":["structured JSON (attachment metadata with download URL, version info)"],"categories":["tool-use-integration","data-processing-analysis"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_7","uri":"capability://tool.use.integration.multi.transport.mcp.server.deployment.stdio.sse.http","name":"multi-transport mcp server deployment (stdio, sse, http)","description":"Exposes the Confluence and Jira tools through multiple transport protocols (stdio for IDE integration, Server-Sent Events for streaming, streamable-http for service deployments) using FastMCP framework. The implementation abstracts transport selection through CLI arguments and environment variables, with automatic server lifecycle management (startup, shutdown, error handling). Supports both synchronous and asynchronous tool execution with streaming response support.","intents":["Deploy Confluence/Jira MCP server in IDE environments (Claude Desktop, Cursor) via stdio transport","Run MCP server as a cloud service with HTTP/SSE transport for multi-client access","Integrate MCP server into existing AI platforms with transport flexibility"],"best_for":["Developers integrating Confluence/Jira into AI IDEs (Claude Desktop, Cursor, etc.)","Teams deploying MCP servers as shared services for multiple AI clients","Organizations building custom AI platforms with pluggable tool integrations"],"limitations":["Stdio transport limited to single client connection; no multiplexing for concurrent requests","SSE transport requires persistent HTTP connection; no automatic reconnection on network failure","Streamable-http transport adds ~200ms latency per request due to HTTP overhead vs stdio","No built-in load balancing or request queuing; concurrent requests may timeout under high load"],"requires":["Python 3.9+","FastMCP framework (included in dependencies)","For stdio: IDE with MCP server support (Claude Desktop 0.1+, Cursor, etc.)","For HTTP/SSE: Network connectivity and port availability"],"input_types":["text (CLI arguments for transport selection)","text (environment variables for configuration)"],"output_types":["MCP protocol messages (tool definitions, results, errors)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_8","uri":"capability://tool.use.integration.flexible.authentication.with.oauth.2.0.api.tokens.and.pat.support","name":"flexible authentication with oauth 2.0, api tokens, and pat support","description":"Supports multiple authentication methods (API tokens, Personal Access Tokens, OAuth 2.0 3LO) with automatic credential resolution from environment variables, CLI arguments, or per-request HTTP headers. The implementation uses a credential chain pattern that checks multiple sources in priority order (CLI args > environment variables > HTTP headers for multi-tenant deployments). Includes OAuth 2.0 3LO flow support for user-delegated access without storing credentials.","intents":["Authenticate to Confluence/Jira using API tokens for service accounts","Support OAuth 2.0 user delegation for multi-tenant SaaS deployments","Enable per-request authentication in shared MCP server deployments"],"best_for":["Teams deploying MCP server as shared service with per-user authentication","Organizations using OAuth 2.0 for user-delegated access","Service accounts that need API token-based authentication"],"limitations":["OAuth 2.0 token refresh requires manual implementation; no automatic token rotation","Per-request authentication via HTTP headers only supported in HTTP transport; not available in stdio","Credential chain resolution adds ~50ms overhead for each request due to environment variable lookup","No credential caching — each request re-evaluates authentication source"],"requires":["Confluence Cloud or Server/Data Center instance","API token (for token auth) OR OAuth 2.0 client credentials (for 3LO flow)","Environment variables or CLI arguments for credential configuration"],"input_types":["text (API token)","text (OAuth 2.0 client ID and secret)","text (HTTP Authorization header for per-request auth)"],"output_types":["authenticated HTTP requests to Confluence/Jira APIs"],"categories":["tool-use-integration","safety-moderation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__cap_9","uri":"capability://tool.use.integration.cloud.and.server.data.center.deployment.abstraction","name":"cloud and server/data center deployment abstraction","description":"Automatically detects and adapts to Confluence/Jira deployment type (Cloud vs Server/Data Center) with format-specific API handling, response parsing, and feature availability checks. The implementation uses deployment detection logic that inspects instance URL patterns and API response formats, then routes requests through deployment-specific code paths for body format conversion (rich text vs storage format), field name mapping, and API endpoint differences.","intents":["Deploy single MCP server codebase against both Cloud and Server/Data Center instances","Automatically handle API differences between deployment types without client-side logic","Support organizations with mixed Cloud/Server/DC deployments"],"best_for":["Organizations with both Cloud and Server/Data Center Confluence/Jira instances","Teams building deployment-agnostic AI integrations","Vendors providing MCP server as multi-deployment service"],"limitations":["Deployment detection based on URL pattern matching; custom domain Server/DC instances may not auto-detect","Some Server/DC-specific features (e.g., custom fields) may not be available in Cloud; no feature flag system for graceful degradation","API response format differences require separate parsing logic per deployment; adds ~100ms overhead per request","Cloud-specific features (e.g., OAuth 2.0 3LO) not available in Server/DC; no fallback mechanism"],"requires":["Confluence Cloud (*.atlassian.net) OR Server/Data Center instance","Valid instance URL for deployment detection"],"input_types":["text (instance URL)"],"output_types":["deployment-specific API requests and responses"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"confluence-mcp-server__headline","uri":"capability://tool.use.integration.mcp.server.for.atlassian.confluence.and.jira","name":"mcp server for atlassian confluence and jira","description":"A community-driven Model Context Protocol (MCP) server that facilitates AI interactions with Atlassian Confluence and Jira, enabling seamless content management and issue tracking across platforms.","intents":["best MCP server for Confluence","MCP server for Jira integration","community MCP server for Atlassian","MCP solutions for project management","AI-driven documentation tools for Confluence"],"best_for":["teams using Atlassian products","developers integrating AI with Confluence and Jira"],"limitations":[],"requires":[],"input_types":[],"output_types":[],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":60,"verified":false,"data_access_risk":"high","permissions":["Confluence Cloud (*.atlassian.net) or Server/Data Center instance","API token or OAuth 2.0 credentials with read access to target spaces","Network connectivity to Confluence instance","Confluence Cloud or Server/Data Center instance","API token or OAuth 2.0 credentials with write access to target space","Valid space key and (optionally) parent page ID for hierarchical placement","FastMCP framework","Python 3.9+","Tool definitions in src/mcp_atlassian/servers/jira.py and confluence.py","Jira Cloud or Server/Data Center instance"],"failure_modes":["Search results limited to 50 items per request by default; requires pagination for larger result sets","CQL filter syntax varies between Cloud and Server/Data Center; server-specific filters may not translate","No full-text indexing optimization — relies on Confluence's native search performance which can be slow on large instances","Content format differs between Cloud (rich text) and Server/Data Center (storage format); requires format-specific HTML/XHTML markup","Parent page resolution requires exact page title or ID; no fuzzy matching for parent lookup","No built-in conflict detection — concurrent page creation with identical titles may cause unexpected behavior","Attachment embedding requires separate API calls; inline attachment references must be pre-uploaded","Tool schema generation is static; no dynamic schema updates based on Confluence/Jira custom fields","Access control decorators are coarse-grained (tool-level); no field-level or operation-level permissions","Tool registration happens at server startup; no hot-reload for new tools without restart","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.7,"quality":0.9,"ecosystem":0.52,"match_graph":0.25,"freshness":0.52,"weights":{"adoption":0.25,"quality":0.25,"ecosystem":0.15,"match_graph":0.23,"freshness":0.12}},"observed_outcomes":{"matches":0,"success_rate":0,"avg_confidence":0,"top_intents":[],"last_matched_at":null},"maintenance":{"status":"active","updated_at":"2026-06-17T09:51:04.690Z","last_scraped_at":null,"last_commit":null},"community":{"stars":null,"forks":null,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=confluence-mcp-server","compare_url":"https://unfragile.ai/compare?artifact=confluence-mcp-server"}},"signature":"Crm9zst16Xu09L06njZBWNhTKVDN74yX0ExpUiQzW8CjP4nbkZo/Bdx1r/Br5zqSevs444Mfr+x/1YpCwDpnBA==","signedAt":"2026-06-20T01:49:10.761Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/confluence-mcp-server","artifact":"https://unfragile.ai/confluence-mcp-server","verify":"https://unfragile.ai/api/v1/verify?slug=confluence-mcp-server","publicKey":"https://unfragile.ai/api/v1/trust-passport-public-key","spec":"https://unfragile.ai/trust","schema":"https://unfragile.ai/schema.json","docs":"https://unfragile.ai/docs"}}