{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_gbcui-xiaohongshu-mcp","slug":"gbcui-xiaohongshu-mcp","name":"xiaohongshu-mcp","type":"mcp","url":"https://github.com/GBcui/xiaohongshu-mcp","page_url":"https://unfragile.ai/gbcui-xiaohongshu-mcp","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:GBcui/xiaohongshu-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_gbcui-xiaohongshu-mcp__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 function calling through a schema-based registry that supports multiple providers, enabling seamless integration with various APIs. It utilizes a dynamic routing mechanism to direct requests to the appropriate backend service based on the defined schema, ensuring flexibility and extensibility. This design choice allows developers to easily add or modify providers without significant code changes, making it distinct from static function calling implementations.","intents":["How can I integrate multiple AI models into my application?","I need to call different APIs based on user input dynamically.","What is the best way to manage function calls to various services in a modular way?"],"best_for":["developers building applications that require integration with multiple AI services"],"limitations":["Requires careful schema management to avoid conflicts between provider APIs","Performance may vary based on the number of active providers"],"requires":["Node.js 14+","Access to the respective APIs being integrated"],"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_gbcui-xiaohongshu-mcp__cap_1","uri":"capability://memory.knowledge.contextual.state.management.for.api.interactions","name":"contextual state management for api interactions","description":"This capability manages contextual state across multiple API interactions, enabling the system to maintain continuity in conversations or transactions. It employs a context stack that keeps track of previous interactions and user states, allowing for more coherent and relevant responses. This approach is particularly useful for applications that require a conversational interface or complex workflows, setting it apart from simpler state management systems.","intents":["How can I maintain user context across multiple API calls?","What is the best way to handle state in a multi-step API interaction?","I need to ensure my application remembers previous user inputs for better responses."],"best_for":["developers creating conversational agents or complex workflows"],"limitations":["Context stack size is limited, which may lead to loss of earlier states","Requires careful management to prevent context overflow"],"requires":["Node.js 14+","Understanding of context management principles"],"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_gbcui-xiaohongshu-mcp__cap_2","uri":"capability://tool.use.integration.dynamic.api.endpoint.resolution","name":"dynamic api endpoint resolution","description":"This capability resolves API endpoints dynamically based on user input or predefined rules, allowing for flexible routing of requests. It uses a configuration file that maps user intents to specific API endpoints, enabling the system to adapt to varying user needs without hardcoding endpoint URLs. This dynamic resolution makes it easier to update or change API integrations as requirements evolve.","intents":["How can I change API endpoints without modifying the codebase?","I want to route requests based on user preferences dynamically.","What is the best way to manage multiple API endpoints in a single application?"],"best_for":["developers looking to create adaptable applications with multiple API integrations"],"limitations":["Configuration errors can lead to incorrect endpoint resolution","Performance may be affected by the complexity of the routing logic"],"requires":["Node.js 14+","Configuration file for endpoint mapping"],"input_types":["text","structured data"],"output_types":["API responses","structured data"],"categories":["tool-use-integration","api orchestration"],"confidence":0.5,"matches":0,"success_rate":0}],"trust":{"score":26,"verified":false,"data_access_risk":"high","permissions":["Node.js 14+","Access to the respective APIs being integrated","Understanding of context management principles","Configuration file for endpoint mapping"],"failure_modes":["Requires careful schema management to avoid conflicts between provider APIs","Performance may vary based on the number of active providers","Context stack size is limited, which may lead to loss of earlier states","Requires careful management to prevent context overflow","Configuration errors can lead to incorrect endpoint resolution","Performance may be affected by the complexity of the routing logic","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.16,"ecosystem":0.48999999999999994,"match_graph":0.25,"freshness":0.6,"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.347Z","last_scraped_at":"2026-05-03T15:19:11.466Z","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=gbcui-xiaohongshu-mcp","compare_url":"https://unfragile.ai/compare?artifact=gbcui-xiaohongshu-mcp"}},"signature":"Z4N36fVmAGwZwkfo3wdSfuhfjuifKDSl7sU3Xtnhqz9BLriRWdWJY4NcJ41CwIobF31hrCX0InC4C92Xav0oDA==","signedAt":"2026-06-22T15:14:21.079Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/gbcui-xiaohongshu-mcp","artifact":"https://unfragile.ai/gbcui-xiaohongshu-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=gbcui-xiaohongshu-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"}}