{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"github_mcp-cursortouch-windows-mcp","slug":"mcp-cursortouch-windows-mcp","name":"Windows-MCP","type":"mcp","url":"https://github.com/CursorTouch/Windows-MCP","page_url":"https://unfragile.ai/mcp-cursortouch-windows-mcp","categories":["mcp-servers"],"tags":["ai","desktop","mcp","tools","windows","windows-automation"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"github_mcp-cursortouch-windows-mcp__cap_0","uri":"capability://data.processing.analysis.windows.ui.element.tree.extraction.and.state.capture","name":"windows ui element tree extraction and state capture","description":"Captures the complete hierarchical structure of Windows UI elements using native UI Automation COM APIs, building an accessibility tree that maps all interactive controls, their properties, and spatial relationships without requiring computer vision. The Tree Service maintains a cached, queryable representation of the desktop state that enables LLMs to understand the current UI layout and identify targets for automation actions.","intents":["I need to understand what UI elements are currently visible and their properties so I can target them for interaction","I want to extract the DOM structure of a web page while filtering out browser chrome elements","I need to get a screenshot alongside the UI element tree to correlate visual content with automation targets"],"best_for":["AI agents automating Windows desktop applications without computer vision dependencies","Teams building LLM-powered RPA solutions that need reliable element identification","Developers creating cross-application automation workflows that require consistent UI element discovery"],"limitations":["Requires Windows 7+ with UI Automation framework enabled; some legacy applications may not expose full accessibility tree","Tree caching adds latency on first capture (~200-500ms depending on desktop complexity); subsequent queries are faster","Cannot interact with elements that don't expose UI Automation interfaces (some custom-drawn controls, certain games)"],"requires":["Windows 7, 8, 8.1, 10, or 11","Python 3.13+","UI Automation COM framework (built-in on Windows)"],"input_types":["none (reads system state directly)"],"output_types":["structured JSON tree with element properties","PNG screenshot","DOM tree for browser content"],"categories":["data-processing-analysis","desktop-automation"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_1","uri":"capability://automation.workflow.synthetic.input.simulation.with.multi.modal.action.support","name":"synthetic input simulation with multi-modal action support","description":"Simulates user input across multiple modalities (mouse clicks, keyboard typing, scrolling, mouse movement, keyboard shortcuts) by translating MCP tool calls into Windows input events through the UI Automation framework. Each action type is optimized for its use case: click operations target specific UI elements by coordinate or element reference, type operations handle text input with clipboard fallback for large payloads, and scroll/move operations support both absolute and relative positioning.","intents":["I need to click on a specific UI element or coordinate to trigger an action","I want to type text into a form field, handling special characters and large text blocks efficiently","I need to scroll within a window or perform keyboard shortcuts like Ctrl+S to save","I want to move the mouse to a specific location for hover interactions or visual feedback"],"best_for":["Automation engineers building end-to-end workflows that require realistic user input simulation","AI agents that need to interact with legacy Windows applications lacking API access","Teams automating data entry, form filling, and UI-driven processes at scale"],"limitations":["Input simulation latency varies 0.2-0.9 seconds depending on system load and LLM inference speed; not suitable for real-time interactive applications","Keyboard input via clipboard has size limits (~32KB per paste operation); very large text requires chunked input","Some applications with custom input handling or anti-automation measures may not respond to simulated input","No built-in rate limiting; rapid successive actions may overwhelm target application or cause missed inputs"],"requires":["Windows 7+","Python 3.13+","UI Automation framework access","Target application must be in focus or accept background input"],"input_types":["coordinate pairs (x, y)","text strings","keyboard key names","element references from UI tree"],"output_types":["action confirmation (success/failure)","updated desktop state after action"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_10","uri":"capability://automation.workflow.async.lifespan.management.with.service.initialization.and.cleanup","name":"async lifespan management with service initialization and cleanup","description":"Uses FastMCP's async lifespan context manager to coordinate initialization and cleanup of core services (Desktop Service, Tree Service, WatchDog Service) across the MCP server lifecycle. Services are initialized on server startup and properly cleaned up on shutdown, ensuring resource management and state consistency. The lifespan pattern enables dependency injection and ordered initialization of services.","intents":["I want to ensure all automation services are properly initialized before accepting MCP calls","I need to clean up resources and stop background services when the MCP server shuts down","I want to coordinate initialization order between dependent services (e.g., Desktop Service before Tree Service)"],"best_for":["Production deployments requiring reliable service lifecycle management","Teams extending Windows-MCP with custom services that need coordinated initialization","Scenarios where proper resource cleanup is critical (long-running servers, resource-constrained systems)"],"limitations":["Lifespan context manager adds ~100-200ms to server startup time for service initialization","Service initialization failures block server startup; no graceful degradation for optional services","Cleanup on shutdown may take several seconds if services have pending operations","No built-in health checking; failed services are not automatically restarted"],"requires":["Python 3.13+","FastMCP framework","Async/await support in Python runtime"],"input_types":["none (internal lifecycle management)"],"output_types":["none (internal lifecycle management)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_11","uri":"capability://automation.workflow.configuration.driven.deployment.with.environment.variable.support","name":"configuration-driven deployment with environment variable support","description":"Supports configuration through environment variables for transport mode (local/remote), server endpoints, logging levels, and feature flags. Configuration is read at startup and applied across all services, enabling deployment flexibility without code changes. The manifest.json file defines server metadata and tool availability, allowing clients to discover capabilities.","intents":["I want to deploy Windows-MCP locally or remotely without modifying code","I need to configure logging and debugging levels for troubleshooting","I want to enable/disable specific features or tools based on deployment environment"],"best_for":["DevOps teams deploying Windows-MCP across multiple environments","Organizations using containerized or cloud deployments requiring environment-based configuration","Teams wanting to customize Windows-MCP behavior without forking the codebase"],"limitations":["Configuration is read at startup; changes require server restart","No built-in configuration validation; invalid environment variables are silently ignored or use defaults","Environment variable naming is not standardized; documentation required for all configuration options","No configuration file support; all configuration must be environment variables"],"requires":["Python 3.13+","Environment variable support in deployment environment","Documentation of available configuration options"],"input_types":["environment variables"],"output_types":["applied configuration (via manifest.json or logging)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_12","uri":"capability://automation.workflow.lightweight.dependency.footprint.with.minimal.external.requirements","name":"lightweight dependency footprint with minimal external requirements","description":"Designed with minimal external dependencies, relying primarily on Python standard library and FastMCP framework. Windows UI Automation is accessed through native COM interfaces rather than heavy third-party libraries. This minimizes installation size, reduces dependency conflicts, and improves deployment reliability. The project uses UV (Astral) for dependency management, providing fast, deterministic package resolution.","intents":["I want to install Windows-MCP with minimal dependencies and fast setup","I need to deploy Windows-MCP in constrained environments with limited package availability","I want to avoid dependency conflicts with other Python projects on the same system"],"best_for":["Teams deploying Windows-MCP in production environments where dependency management is critical","Developers building on resource-constrained systems or in isolated environments","Organizations with strict dependency approval processes"],"limitations":["Minimal dependencies means some features may require manual implementation or external tools","No built-in support for advanced features (e.g., image processing, advanced logging) without additional packages","Dependency updates must be manually tracked; no automatic security patching"],"requires":["Python 3.13+","UV package manager (Astral)","Windows 7+"],"input_types":["none (dependency information)"],"output_types":["none (dependency information)"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_13","uri":"capability://tool.use.integration.mit.licensed.open.source.codebase.with.community.contribution.support","name":"mit-licensed open-source codebase with community contribution support","description":"Published under MIT license with full source code available on GitHub, enabling community contributions, customization, and transparency. The project includes contribution guidelines, development setup documentation, and code quality standards. Open-source licensing allows integration into commercial products and custom deployments without licensing restrictions.","intents":["I want to customize Windows-MCP for my specific use case without licensing restrictions","I want to contribute improvements or bug fixes back to the project","I need to integrate Windows-MCP into a commercial product with clear licensing"],"best_for":["Organizations building commercial products that need Windows automation","Community developers wanting to contribute to the project","Teams requiring full source code access for security audits or customization"],"limitations":["Open-source licensing provides no commercial support or SLA","Community contributions may have varying code quality; review burden falls on maintainers","No guaranteed maintenance or security patching; depends on community engagement"],"requires":["MIT license acceptance","GitHub account for contributions (optional)"],"input_types":["none (licensing information)"],"output_types":["none (licensing information)"],"categories":["tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_2","uri":"capability://automation.workflow.application.lifecycle.management.and.process.control","name":"application lifecycle management and process control","description":"Manages Windows application launching, window control, and process termination through native Windows APIs integrated into the MCP tool layer. Enables starting applications by path or name, bringing windows to focus, minimizing/maximizing/closing windows, and terminating processes. The Desktop Service coordinates these operations with the UI Automation layer to maintain consistent state tracking.","intents":["I need to launch a specific application or script to begin an automation workflow","I want to switch focus between multiple open applications or windows","I need to close or minimize a window, or force-terminate a hung process","I want to manage window state (maximize, restore, move to virtual desktop) as part of automation"],"best_for":["Automation workflows that span multiple applications and require coordinated window management","AI agents that need to launch tools or utilities as part of task execution","Teams automating complex multi-step processes involving application switching"],"limitations":["Process termination is forceful (SIGKILL equivalent); no graceful shutdown opportunity for applications to save state","Window management operations may fail for system windows or protected applications (Windows Defender, UAC dialogs)","Application launch paths must be absolute or resolvable through PATH; relative paths not supported","No built-in process monitoring or health checking; launched applications may crash silently"],"requires":["Windows 7+","Python 3.13+","Appropriate permissions to launch target applications","Target application must be installed and accessible"],"input_types":["application path or name","window handle or title","process ID"],"output_types":["process ID (on launch)","operation success/failure","window state confirmation"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_3","uri":"capability://data.processing.analysis.browser.dom.extraction.with.ui.chrome.filtering","name":"browser dom extraction with ui chrome filtering","description":"Implements a specialized 'DOM mode' for browser automation that extracts the actual web page content structure while intelligently filtering out browser UI elements (address bar, tabs, toolbars, scrollbars). This is achieved by parsing the browser's accessibility tree and applying heuristics to distinguish page content from browser chrome, returning a clean DOM representation that LLMs can reason about without visual noise.","intents":["I need to extract the structure of a web page so I can identify and interact with specific content elements","I want to automate web form filling or data extraction without being distracted by browser UI elements","I need to understand the DOM hierarchy of a page to target specific elements for clicking or text input"],"best_for":["Web automation and scraping workflows that need clean DOM representation","AI agents automating web-based applications and forms","Teams building browser-based RPA solutions that require reliable element targeting"],"limitations":["DOM mode only works with browsers that expose accessibility tree (Chrome, Edge, Firefox); Safari support limited","JavaScript-rendered content may not be fully captured if not yet rendered in accessibility tree","Filtering heuristics may incorrectly classify some custom UI elements as chrome or vice versa","No support for shadow DOM or web components that don't expose accessibility interfaces"],"requires":["Windows 7+","Python 3.13+","Browser with UI Automation support (Chrome, Edge, Firefox)","Browser must be running and accessible"],"input_types":["none (reads browser state directly)"],"output_types":["filtered DOM tree as JSON","element references for targeting"],"categories":["data-processing-analysis","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_4","uri":"capability://automation.workflow.real.time.desktop.state.monitoring.and.change.detection","name":"real-time desktop state monitoring and change detection","description":"The WatchDog Service continuously monitors the Windows desktop for state changes (new windows, closed applications, UI element tree modifications) and provides real-time notifications to MCP clients. This enables reactive automation workflows where agents can respond to system events rather than polling. The service maintains a delta between previous and current state, allowing efficient change detection without full tree re-traversal.","intents":["I want to be notified when a new window appears so I can react to it automatically","I need to detect when an application has finished loading or a dialog has appeared","I want to monitor for specific UI element changes (button enabled, text updated) without constant polling"],"best_for":["Event-driven automation workflows that react to system state changes","AI agents that need to handle dynamic UI changes or unexpected dialogs","Teams building long-running automation processes that must adapt to runtime conditions"],"limitations":["Change detection latency depends on monitoring interval; default interval may miss rapid state transitions","No built-in filtering for noise; high-frequency UI updates (animations, progress bars) generate many notifications","Memory overhead grows with desktop complexity; large numbers of windows or UI elements increase monitoring cost","WatchDog service must remain running; stopping it disables change detection"],"requires":["Windows 7+","Python 3.13+","WatchDog Service running in MCP server process"],"input_types":["none (monitors system state)"],"output_types":["state change notifications (JSON)","delta between previous and current state"],"categories":["automation-workflow","planning-reasoning"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_5","uri":"capability://automation.workflow.virtual.desktop.and.workspace.management","name":"virtual desktop and workspace management","description":"Provides control over Windows Virtual Desktop functionality, enabling automation workflows to create, switch between, and manage virtual desktops. This allows organizing application workspaces and isolating automation tasks to specific desktops. The Virtual Desktop Manager integrates with the UI Automation layer to track which applications are on which desktops.","intents":["I want to create a new virtual desktop for a specific automation task to keep it isolated","I need to switch between virtual desktops to manage multiple concurrent workflows","I want to move windows between desktops as part of workspace organization"],"best_for":["Complex automation workflows that benefit from workspace isolation","Teams running multiple concurrent automation tasks on the same machine","Scenarios where application organization improves reliability or reduces interference"],"limitations":["Virtual Desktop feature only available on Windows 10/11; not supported on Windows 7/8","Desktop switching may cause brief visual flicker or input lag during transition","Some applications may not properly handle desktop switching (lose focus, fail to render)","No built-in persistence; virtual desktops are lost on system restart"],"requires":["Windows 10 or 11","Python 3.13+","Virtual Desktop feature enabled (default on Windows 10/11)"],"input_types":["desktop index or name","window handle"],"output_types":["desktop creation confirmation","current desktop index","operation success/failure"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_6","uri":"capability://tool.use.integration.codebase.aware.function.calling.with.mcp.tool.schema.binding","name":"codebase-aware function calling with mcp tool schema binding","description":"Exposes 17 specialized Windows automation tools through the Model Context Protocol using a schema-based function registry that binds to FastMCP framework. Each tool is defined with precise input/output schemas, parameter validation, and error handling. The MCP server dynamically generates tool definitions that LLM clients can discover and invoke, with automatic marshaling between LLM function calls and Python implementation.","intents":["I want to invoke Windows automation tools from an LLM client (Claude Desktop, Gemini, Perplexity) with proper schema validation","I need to discover what automation capabilities are available and their parameters","I want to call multiple tools in sequence with proper error handling and state management"],"best_for":["LLM client developers integrating Windows automation into AI agents","Teams building multi-step automation workflows that require reliable tool invocation","Developers creating custom MCP servers that extend Windows-MCP capabilities"],"limitations":["Tool invocation latency includes LLM inference time plus action execution; typical round-trip 0.5-2 seconds","Schema validation is strict; malformed tool calls are rejected rather than auto-corrected","No built-in transaction support; partial failures in multi-step workflows require manual recovery","Tool output is serialized to JSON; binary data (images) must be base64-encoded, increasing payload size"],"requires":["Python 3.13+","FastMCP framework","MCP-compatible LLM client (Claude Desktop, Gemini CLI, Perplexity Desktop, or custom client)","Windows 7+"],"input_types":["JSON-serialized tool parameters"],"output_types":["JSON-serialized tool results","base64-encoded images","structured error messages"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_7","uri":"capability://automation.workflow.multi.operation.batch.execution.with.state.coordination","name":"multi-operation batch execution with state coordination","description":"Supports executing multiple automation operations in a single MCP call through multi-operation tools that coordinate state changes across sequential actions. This reduces round-trip latency and improves reliability by grouping related operations (e.g., click, wait for state change, type text) into atomic units. The Desktop Service maintains state consistency across operations, rolling back on failure.","intents":["I want to perform multiple related actions (click, type, press Enter) as a single atomic operation","I need to execute a sequence of actions with automatic state synchronization between steps","I want to reduce latency by batching multiple operations instead of making separate MCP calls"],"best_for":["High-frequency automation workflows where latency is critical","Scenarios requiring atomic multi-step operations that must succeed or fail together","Teams automating form filling or data entry that involves multiple sequential interactions"],"limitations":["Batch operations are limited in size; very large batches may exceed MCP message size limits","Partial failures in a batch are not granularly reported; entire batch fails if any operation fails","State rollback is not automatic; failed batches may leave system in intermediate state","Debugging multi-operation failures is harder than single-operation calls due to lack of granular error reporting"],"requires":["Python 3.13+","MCP client supporting multi-operation tool calls","Windows 7+"],"input_types":["array of operation objects with parameters"],"output_types":["array of operation results","aggregated success/failure status","final desktop state"],"categories":["automation-workflow","tool-use-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_8","uri":"capability://image.visual.screenshot.capture.with.optional.vision.free.operation","name":"screenshot capture with optional vision-free operation","description":"Captures PNG screenshots of the current desktop state, with optional integration into the snapshot tool. The screenshot capability is decoupled from UI element identification, allowing operation in 'vision-free' mode where LLMs can automate Windows without computer vision capabilities. Screenshots are base64-encoded for MCP transmission and can be selectively captured (full desktop, specific window, or region).","intents":["I want to capture a screenshot of the current desktop to verify automation progress","I need to get a visual representation of the current state for debugging or logging","I want to operate without computer vision, using only the UI element tree for navigation"],"best_for":["Automation workflows that benefit from visual verification but don't require vision-based element detection","Teams using LLMs without vision capabilities (text-only models) that still want screenshot logging","Debugging and monitoring scenarios where visual state capture is useful"],"limitations":["Screenshot encoding to base64 increases payload size by ~33%; large screenshots may exceed MCP message limits","Screenshot capture latency varies with desktop complexity and GPU availability; typically 50-200ms","Screenshots don't capture elements outside the visible window (off-screen content, minimized windows)","No built-in image compression; high-resolution screenshots generate large payloads"],"requires":["Windows 7+","Python 3.13+","Display adapter (virtual displays supported)"],"input_types":["optional: window handle or region coordinates"],"output_types":["base64-encoded PNG image"],"categories":["image-visual","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"github_mcp-cursortouch-windows-mcp__cap_9","uri":"capability://tool.use.integration.cross.client.mcp.protocol.compatibility.with.transport.abstraction","name":"cross-client mcp protocol compatibility with transport abstraction","description":"Implements the Model Context Protocol (MCP) specification with transport abstraction, supporting both local (stdio) and remote (HTTP/WebSocket) operation modes. The server is compatible with multiple LLM clients including Claude Desktop, Perplexity Desktop, Gemini CLI, and custom MCP clients. Transport configuration is environment-driven, allowing deployment flexibility without code changes.","intents":["I want to use Windows-MCP with my preferred LLM client (Claude, Gemini, Perplexity, or custom)","I need to deploy Windows-MCP locally on my machine or remotely on a cloud Windows instance","I want to integrate Windows-MCP into a custom MCP client or automation framework"],"best_for":["Teams using multiple LLM clients and wanting a single Windows automation backend","Developers building custom MCP clients that need Windows automation capabilities","Organizations deploying automation on cloud Windows instances (windowsmcp.io or custom)"],"limitations":["Remote mode requires network connectivity and introduces latency (typically 50-200ms additional per operation)","Transport configuration requires environment variables; no runtime transport switching","HTTP/WebSocket remote mode lacks built-in authentication; requires external security layer (VPN, firewall)","Client compatibility depends on MCP version; older clients may not support all Windows-MCP features"],"requires":["Python 3.13+","MCP-compatible client (Claude Desktop 0.1+, Gemini CLI, Perplexity Desktop, or custom)","For remote mode: network connectivity, optional: windowsmcp.io account or custom server"],"input_types":["MCP protocol messages (JSON-RPC)"],"output_types":["MCP protocol responses (JSON-RPC)"],"categories":["tool-use-integration","automation-workflow"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":47,"verified":false,"data_access_risk":"high","permissions":["Windows 7, 8, 8.1, 10, or 11","Python 3.13+","UI Automation COM framework (built-in on Windows)","Windows 7+","UI Automation framework access","Target application must be in focus or accept background input","FastMCP framework","Async/await support in Python runtime","Environment variable support in deployment environment","Documentation of available configuration options"],"failure_modes":["Requires Windows 7+ with UI Automation framework enabled; some legacy applications may not expose full accessibility tree","Tree caching adds latency on first capture (~200-500ms depending on desktop complexity); subsequent queries are faster","Cannot interact with elements that don't expose UI Automation interfaces (some custom-drawn controls, certain games)","Input simulation latency varies 0.2-0.9 seconds depending on system load and LLM inference speed; not suitable for real-time interactive applications","Keyboard input via clipboard has size limits (~32KB per paste operation); very large text requires chunked input","Some applications with custom input handling or anti-automation measures may not respond to simulated input","No built-in rate limiting; rapid successive actions may overwhelm target application or cause missed inputs","Lifespan context manager adds ~100-200ms to server startup time for service initialization","Service initialization failures block server startup; no graceful degradation for optional services","Cleanup on shutdown may take several seconds if services have pending operations","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.606669992142995,"quality":0.35,"ecosystem":0.5800000000000001,"match_graph":0.25,"freshness":0.75,"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-05-24T12:16:22.064Z","last_scraped_at":"2026-05-03T14:23:31.492Z","last_commit":"2026-05-01T00:34:09Z"},"community":{"stars":5449,"forks":708,"weekly_downloads":null,"model_downloads":null,"model_likes":null}},"distribution":{"claim_url":"https://unfragile.ai/submit?claim=mcp-cursortouch-windows-mcp","compare_url":"https://unfragile.ai/compare?artifact=mcp-cursortouch-windows-mcp"}},"signature":"Ksh+Ewlsn7J8UiXJRVyrUlz36bx85rzT5rhvuFcMEogM9frAfUbc5WYEwgbFtueRmlBfsly32wan3EJELP3KBQ==","signedAt":"2026-06-22T03:02:41.418Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/mcp-cursortouch-windows-mcp","artifact":"https://unfragile.ai/mcp-cursortouch-windows-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=mcp-cursortouch-windows-mcp","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"}}