{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_befdaynow-beks","slug":"befdaynow-beks","name":"beks","type":"mcp","url":"https://smithery.ai/servers/befdaynow/beks","page_url":"https://unfragile.ai/befdaynow-beks","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:befdaynow/beks"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_befdaynow-beks__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 for dynamic function calling based on a defined schema that integrates with multiple AI model providers. It utilizes a registry pattern to manage function definitions and their corresponding API endpoints, enabling seamless orchestration of calls to various models like OpenAI and Anthropic. The architecture supports extensibility, allowing developers to add new providers without significant changes to the core system.","intents":["How can I call functions from different AI models in a unified way?","I need to integrate multiple AI services into my application easily.","What is the best way to manage different function APIs in my project?"],"best_for":["developers building applications that require multi-provider AI integrations"],"limitations":["Requires manual schema definition for each function, which can be time-consuming.","Limited to providers that support the defined schema."],"requires":["Node.js 18+","API keys for each integrated AI model"],"input_types":["structured data","text"],"output_types":["structured data","text"],"categories":["tool-use-integration","api management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_befdaynow-beks__cap_1","uri":"capability://memory.knowledge.contextual.state.management.for.ai.interactions","name":"contextual state management for ai interactions","description":"This capability provides a mechanism for managing contextual state across multiple interactions with AI models. It employs a context management pattern that retains relevant data from previous interactions, allowing for more coherent and contextually aware responses from the models. This is achieved through a combination of in-memory storage and optional persistence layers, enabling developers to maintain context across sessions.","intents":["How can I maintain context between user interactions with the AI?","I want my AI to remember previous conversations for better responses.","What is the best way to manage session state for my AI application?"],"best_for":["developers creating conversational agents or interactive AI applications"],"limitations":["In-memory context management may lead to data loss on server restarts unless persistence is implemented.","Limited to the size of memory for context storage."],"requires":["Node.js 18+","Optional database for persistent storage"],"input_types":["text","structured data"],"output_types":["text","structured data"],"categories":["memory-knowledge","context management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_befdaynow-beks__cap_2","uri":"capability://tool.use.integration.dynamic.api.orchestration.for.ai.services","name":"dynamic api orchestration for ai services","description":"This capability enables the dynamic orchestration of API calls to various AI services based on user-defined workflows. It uses a workflow engine that interprets user-defined rules and conditions to determine the sequence and conditions under which API calls are made. This allows developers to create complex interactions that can adapt based on real-time input and responses from the AI models.","intents":["How can I create workflows that involve multiple AI services?","I need to orchestrate API calls based on specific conditions.","What is the best way to manage complex interactions with AI models?"],"best_for":["developers building applications with complex AI workflows"],"limitations":["Workflow complexity can lead to increased latency in processing.","Requires careful design to avoid circular dependencies in workflows."],"requires":["Node.js 18+","API keys for each integrated AI model"],"input_types":["structured data","text"],"output_types":["structured data","text"],"categories":["tool-use-integration","workflow management"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_befdaynow-beks__cap_3","uri":"capability://data.processing.analysis.real.time.monitoring.and.analytics.for.api.usage","name":"real-time monitoring and analytics for api usage","description":"This capability provides real-time monitoring and analytics of API usage across different AI services. It employs a logging and metrics collection system that tracks API call frequency, response times, and error rates, allowing developers to gain insights into their application's performance. The data is visualized through a dashboard, enabling quick identification of bottlenecks and optimization opportunities.","intents":["How can I monitor the performance of my AI API calls?","I need insights into the usage patterns of my AI services.","What is the best way to identify bottlenecks in my application?"],"best_for":["developers looking to optimize API performance and reliability"],"limitations":["Real-time monitoring may introduce additional overhead on API calls.","Requires proper configuration to avoid excessive logging."],"requires":["Node.js 18+","Monitoring tools or services for data visualization"],"input_types":["structured data","text"],"output_types":["analytics reports","structured data"],"categories":["data-processing-analysis","monitoring"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":28,"verified":false,"data_access_risk":"high","permissions":["Node.js 18+","API keys for each integrated AI model","Optional database for persistent storage","Monitoring tools or services for data visualization"],"failure_modes":["Requires manual schema definition for each function, which can be time-consuming.","Limited to providers that support the defined schema.","In-memory context management may lead to data loss on server restarts unless persistence is implemented.","Limited to the size of memory for context storage.","Workflow complexity can lead to increased latency in processing.","Requires careful design to avoid circular dependencies in workflows.","Real-time monitoring may introduce additional overhead on API calls.","Requires proper configuration to avoid excessive logging.","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.18,"ecosystem":0.38999999999999996,"match_graph":0.25,"freshness":0.9,"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:25.636Z","last_scraped_at":"2026-05-03T15:19:20.347Z","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=befdaynow-beks","compare_url":"https://unfragile.ai/compare?artifact=befdaynow-beks"}},"signature":"1uVuuzvUBHT/YNYjp9OS8DtrjZsFPTKSrSyKn/C7PDGIfbS2gMF8LtjHY7bWkbdZoVNlGh3ymcLz9l6Ck+yPCQ==","signedAt":"2026-06-15T16:49:09.330Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/befdaynow-beks","artifact":"https://unfragile.ai/befdaynow-beks","verify":"https://unfragile.ai/api/v1/verify?slug=befdaynow-beks","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"}}