{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_igledaniel-tourmis","slug":"igledaniel-tourmis","name":"tourmis","type":"mcp","url":"https://smithery.ai/servers/igledaniel/tourmis","page_url":"https://unfragile.ai/igledaniel-tourmis","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:igledaniel/tourmis"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_igledaniel-tourmis__cap_0","uri":"capability://tool.use.integration.schema.based.function.calling.with.multi.provider.support","name":"schema-based function calling with multi-provider support","description":"This capability allows users to define and call functions based on a schema that supports multiple providers. It uses a dynamic function registry that maps function signatures to their respective implementations, enabling seamless integration with various APIs. This architecture allows for easy extensibility and adaptability to new providers without significant code changes, making it distinct from rigid function calling systems.","intents":["How can I integrate multiple APIs into my application without rewriting code?","What is the best way to manage function calls to different service providers?","Can I easily switch between different API providers in my workflow?"],"best_for":["developers building applications that require integration with multiple APIs"],"limitations":["Requires manual configuration of function schemas for each provider","Performance may vary based on the complexity of the schema"],"requires":["Node.js 18+","API keys for the respective service providers"],"input_types":["structured data","API requests"],"output_types":["structured data","API responses"],"categories":["tool-use-integration","api orchestration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_igledaniel-tourmis__cap_1","uri":"capability://memory.knowledge.contextual.data.management.for.api.interactions","name":"contextual data management for api interactions","description":"This capability manages the context of API interactions by maintaining state across multiple calls. It employs a context stack that retains relevant information from previous interactions, allowing for more intelligent and context-aware responses. This design pattern ensures that users can build complex workflows that depend on historical data without losing track of previous states.","intents":["How can I maintain context across multiple API calls in my application?","What is the best way to handle stateful interactions with APIs?","Can I create workflows that depend on previous API responses?"],"best_for":["developers creating applications that require stateful API interactions"],"limitations":["Context management can lead to increased memory usage","Complex workflows may introduce latency"],"requires":["Node.js 18+","Proper configuration of context management settings"],"input_types":["structured data","API requests"],"output_types":["structured data","contextual responses"],"categories":["memory-knowledge","state management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_igledaniel-tourmis__cap_2","uri":"capability://automation.workflow.dynamic.workflow.orchestration","name":"dynamic workflow orchestration","description":"This capability allows users to create and manage dynamic workflows that can adapt to changing conditions. It uses a rule-based engine to evaluate conditions and trigger specific actions based on real-time data inputs. This architecture supports complex decision-making processes and enables users to automate tasks without hardcoding logic into their applications.","intents":["How can I automate workflows that change based on real-time data?","What is the best way to implement conditional logic in my application?","Can I create workflows that adapt to user inputs dynamically?"],"best_for":["teams looking to automate complex workflows that require real-time adaptability"],"limitations":["Rule complexity can lead to maintenance challenges","Performance may degrade with highly nested conditions"],"requires":["Node.js 18+","Configuration of the rule engine"],"input_types":["structured data","events"],"output_types":["structured data","task outputs"],"categories":["automation-workflow","dynamic systems"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_igledaniel-tourmis__cap_3","uri":"capability://data.processing.analysis.multi.format.data.processing","name":"multi-format data processing","description":"This capability enables the processing of data in various formats, including JSON, XML, and CSV. It employs a modular architecture that allows for the addition of new data format handlers without disrupting existing functionality. This design choice ensures that users can easily work with diverse data sources and formats in a consistent manner.","intents":["How can I handle data from different sources with varying formats?","What is the best way to convert data between formats in my application?","Can I integrate multiple data formats into a single workflow?"],"best_for":["developers dealing with heterogeneous data sources"],"limitations":["Performance may vary based on the complexity of data transformations","Requires additional configuration for new formats"],"requires":["Node.js 18+","Libraries for specific data formats"],"input_types":["JSON","XML","CSV"],"output_types":["JSON","XML","CSV"],"categories":["data-processing-analysis","data-integration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_igledaniel-tourmis__cap_4","uri":"capability://automation.workflow.real.time.event.handling","name":"real-time event handling","description":"This capability allows for the processing and handling of real-time events, enabling applications to respond to changes as they happen. It uses an event-driven architecture that listens for specific triggers and executes predefined actions in response. This design choice ensures that users can build responsive applications that react to real-time data inputs effectively.","intents":["How can I build an application that responds to real-time events?","What is the best way to implement event-driven architecture in my project?","Can I create workflows that trigger actions based on live data?"],"best_for":["developers building applications that require real-time responsiveness"],"limitations":["Event handling can introduce latency if not optimized","Complex event chains may lead to debugging challenges"],"requires":["Node.js 18+","Event handling libraries or frameworks"],"input_types":["events","real-time data"],"output_types":["structured data","event responses"],"categories":["automation-workflow","event-driven"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":24,"verified":false,"data_access_risk":"moderate","permissions":["Node.js 18+","API keys for the respective service providers","Proper configuration of context management settings","Configuration of the rule engine","Libraries for specific data formats","Event handling libraries or frameworks"],"failure_modes":["Requires manual configuration of function schemas for each provider","Performance may vary based on the complexity of the schema","Context management can lead to increased memory usage","Complex workflows may introduce latency","Rule complexity can lead to maintenance challenges","Performance may degrade with highly nested conditions","Performance may vary based on the complexity of data transformations","Requires additional configuration for new formats","Event handling can introduce latency if not optimized","Complex event chains may lead to debugging challenges","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.2,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.5,"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:26.913Z","last_scraped_at":"2026-05-03T15:19:51.141Z","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=igledaniel-tourmis","compare_url":"https://unfragile.ai/compare?artifact=igledaniel-tourmis"}},"signature":"Krnl1sOnvKoGuv5IPWW754RpsA5W4W+LojCqayJzJJXZeeEqihoo+QkPmgV/ZSrfdtqtwqc5K5D4xKrPvWYTAQ==","signedAt":"2026-06-21T15:51:24.834Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/igledaniel-tourmis","artifact":"https://unfragile.ai/igledaniel-tourmis","verify":"https://unfragile.ai/api/v1/verify?slug=igledaniel-tourmis","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"}}