{"passport":{"unfragile":{"@version":"1.0","version":"2026-05","artifact":{"id":"smithery_suse00544-xiaohongshu-mcp","slug":"suse00544-xiaohongshu-mcp","name":"xiaohongshu-mcp","type":"mcp","url":"https://github.com/suse00544/xiaohongshu-mcp","page_url":"https://unfragile.ai/suse00544-xiaohongshu-mcp","categories":["mcp-servers"],"tags":["mcp","model-context-protocol","smithery:suse00544/xiaohongshu-mcp"],"pricing":{"model":"open_source","free":true,"starting_price":null},"status":"active","verified":false},"capabilities":[{"id":"smithery_suse00544-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 defines how different functions can be invoked across multiple providers. It utilizes a modular architecture to facilitate seamless integration with various APIs, enabling dynamic function resolution based on the context of the request. This design choice enhances flexibility and interoperability compared to static function calling systems.","intents":["How can I call functions from different APIs seamlessly?","I need to integrate multiple service providers into my application.","What is the best way to manage function calls dynamically?"],"best_for":["developers building applications that require multi-provider API integrations"],"limitations":["Requires a predefined schema for function definitions, which may add complexity.","Performance may vary depending on the number of providers integrated."],"requires":["Node.js 14+","Access to the respective API keys for each service provider"],"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_suse00544-xiaohongshu-mcp__cap_1","uri":"capability://memory.knowledge.context.aware.request.handling","name":"context-aware request handling","description":"This capability processes incoming requests by leveraging contextual information to tailor responses and function calls. It employs a context management system that retains state across interactions, allowing for more relevant and personalized API responses. This approach distinguishes it from simpler request handlers that do not consider prior interactions.","intents":["How can I maintain context between API calls?","I want to personalize responses based on user history.","What is the best way to handle stateful interactions in my application?"],"best_for":["developers creating interactive applications that require user context management"],"limitations":["Context retention may increase memory usage, especially with long interactions.","Requires careful management of context to avoid stale data."],"requires":["Node.js 14+","A mechanism for storing context, such as a database or in-memory store"],"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_suse00544-xiaohongshu-mcp__cap_2","uri":"capability://tool.use.integration.dynamic.api.endpoint.resolution","name":"dynamic api endpoint resolution","description":"This capability enables the system to dynamically resolve API endpoints based on the incoming request parameters and context. It uses a routing mechanism that evaluates the request against a set of predefined rules to determine the appropriate endpoint, allowing for greater flexibility in API interactions. This design choice allows for easier updates and maintenance of API integrations.","intents":["How can I dynamically route API requests based on user input?","I need a flexible way to manage multiple API endpoints.","What is the best approach for handling variable API paths?"],"best_for":["developers needing to manage complex API interactions with variable endpoints"],"limitations":["Routing rules can become complex and may require thorough documentation.","Performance may be impacted if routing logic is not optimized."],"requires":["Node.js 14+","A configuration file defining routing rules"],"input_types":["text","structured data"],"output_types":["structured data","API responses"],"categories":["tool-use-integration","api orchestration"],"confidence":0.5,"matches":0,"success_rate":0},{"id":"smithery_suse00544-xiaohongshu-mcp__cap_3","uri":"capability://data.processing.analysis.multi.format.data.processing","name":"multi-format data processing","description":"This capability supports processing and transforming data across various formats, including JSON, XML, and CSV. It employs a set of transformation functions that can be applied based on the input format, allowing for seamless data interchange between different systems. This approach is particularly beneficial for applications that need to integrate with diverse data sources.","intents":["How can I convert data between different formats?","I need to process incoming data from various sources.","What is the best way to handle data transformation in my application?"],"best_for":["developers working with diverse data sources and requiring format conversions"],"limitations":["Transformations may introduce latency depending on the complexity of the data.","Requires thorough testing to ensure data integrity across formats."],"requires":["Node.js 14+","Libraries for handling specific data formats (e.g., xml2js for XML)"],"input_types":["JSON","XML","CSV"],"output_types":["JSON","XML","CSV"],"categories":["data-processing-analysis","data-transformation"],"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 API keys for each service provider","A mechanism for storing context, such as a database or in-memory store","A configuration file defining routing rules","Libraries for handling specific data formats (e.g., xml2js for XML)"],"failure_modes":["Requires a predefined schema for function definitions, which may add complexity.","Performance may vary depending on the number of providers integrated.","Context retention may increase memory usage, especially with long interactions.","Requires careful management of context to avoid stale data.","Routing rules can become complex and may require thorough documentation.","Performance may be impacted if routing logic is not optimized.","Transformations may introduce latency depending on the complexity of the data.","Requires thorough testing to ensure data integrity across formats.","builder identity is not verified yet","no observed match outcomes yet"],"rank_breakdown":{"adoption":0.05,"quality":0.18,"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:28.139Z","last_scraped_at":"2026-05-03T15:19:29.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=suse00544-xiaohongshu-mcp","compare_url":"https://unfragile.ai/compare?artifact=suse00544-xiaohongshu-mcp"}},"signature":"DdvXvMXYIcowNKUzEKLxTy4LAh+L5+nKWcuOYLDWAP2/ovdjW2raLQLsBB0GKW6e7E9DvU0aYWG+DEBDD7CuBQ==","signedAt":"2026-06-21T22:28:00.507Z","signedBy":"unfragile.ai","version":1},"_links":{"self":"https://unfragile.ai/api/v1/passport/suse00544-xiaohongshu-mcp","artifact":"https://unfragile.ai/suse00544-xiaohongshu-mcp","verify":"https://unfragile.ai/api/v1/verify?slug=suse00544-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"}}