@toolsdk.ai/registry 1.0.100 → 1.0.101

package/indexes/packages-list.json

@@ -1658,7 +1658,42 @@
   },
   "qanon_mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/qanon_mcp.json"
+    "path": "other-tools-and-integrations/qanon_mcp.json",
+    "validated": true,
+    "tools": {
+      "get_post_by_id_tool": {
+        "name": "get_post_by_id_tool",
+        "description": "\nRetrieve a specific post by its ID.\n\nArgs:\n    post_id: The ID of the post to retrieve\n"
+      },
+      "search_posts": {
+        "name": "search_posts",
+        "description": "\nSearch for posts/drops containing a specific keyword or phrase.\n\nArgs:\n    query: The keyword or phrase to search for\n    limit: Maximum number of results to return (default: 10)\n"
+      },
+      "get_posts_by_date": {
+        "name": "get_posts_by_date",
+        "description": "\nGet posts/drops within a specific date range.\n\nArgs:\n    start_date: Start date in YYYY-MM-DD format\n    end_date: End date in YYYY-MM-DD format (defaults to start_date if not provided)\n    limit: Maximum number of results to return (default: 10)\n"
+      },
+      "get_posts_by_author_id": {
+        "name": "get_posts_by_author_id",
+        "description": "\nGet posts/drops by a specific author ID.\n\nArgs:\n    author_id: The author ID to search for\n    limit: Maximum number of results to return (default: 10)\n"
+      },
+      "analyze_post": {
+        "name": "analyze_post",
+        "description": "\nGet detailed analysis of a specific post/drop including references and context.\n\nArgs:\n    post_id: The ID of the post to analyze\n"
+      },
+      "get_timeline_summary": {
+        "name": "get_timeline_summary",
+        "description": "\nGet a timeline summary of posts/drops, optionally within a date range.\n\nArgs:\n    start_date: Optional start date in YYYY-MM-DD format\n    end_date: Optional end date in YYYY-MM-DD format\n"
+      },
+      "word_cloud_by_post_ids": {
+        "name": "word_cloud_by_post_ids",
+        "description": "\nGenerate a word cloud analysis showing the most common words used in posts within a specified ID range.\n\nArgs:\n    start_id: Starting post ID\n    end_id: Ending post ID\n    min_word_length: Minimum length of words to include (default: 3)\n    max_words: Maximum number of words to return (default: 100)\n"
+      },
+      "word_cloud_by_date_range": {
+        "name": "word_cloud_by_date_range",
+        "description": "\nGenerate a word cloud analysis showing the most common words used in posts within a specified date range.\n\nArgs:\n    start_date: Start date in YYYY-MM-DD format\n    end_date: End date in YYYY-MM-DD format\n    min_word_length: Minimum length of words to include (default: 3)\n    max_words: Maximum number of words to return (default: 100)\n"
+      }
+    }
   },
   "@anaisbetts/mcp-youtube": {
     "category": "search-data-extraction",
@@ -4238,7 +4273,14 @@
   },
   "sketchfab-mcp": {
     "category": "art-and-culture",
-    "path": "art-and-culture/sketchfab-mcp.json"
+    "path": "art-and-culture/sketchfab-mcp.json",
+    "validated": true,
+    "tools": {
+      "sequentialthinking": {
+        "name": "sequentialthinking",
+        "description": "\nA detailed tool for dynamic and reflective problem-solving through thoughts.\n\nThis tool helps analyze problems through a flexible thinking process that can adapt and evolve.\nEach thought can build on, question, or revise previous insights as understanding deepens.\nIt uses an Agno multi-agent team (in coordinate mode) to process each thought, where a\nCoordinator delegates sub-tasks to specialists (Planner, Researcher, Analyzer, Critic, Synthesizer)\nand synthesizes their outputs.\n\nWhen to use this tool:\n- Breaking down complex problems into manageable steps.\n- Planning and design processes requiring iterative refinement and revision.\n- Complex analysis where the approach might need course correction based on findings.\n- Problems where the full scope or optimal path is not clear initially.\n- Situations requiring a multi-step solution with context maintained across steps.\n- Tasks where focusing on relevant information and filtering out noise is crucial.\n- Developing and verifying solution hypotheses through a chain of reasoning.\n\nKey features & usage guidelines:\n- The process is driven by the caller (e.g., an LLM) making sequential calls to this tool.\n- Start with an initial estimate for `totalThoughts`, but adjust it dynamically via subsequent calls if needed.\n- Use `isRevision=True` and `revisesThought` to explicitly revisit and correct previous steps.\n- Use `branchFromThought` and `branchId` to explore alternative paths or perspectives.\n- If the estimated `totalThoughts` is reached but more steps are needed, set `needsMoreThoughts=True` on the *last* thought within the current estimate to signal the need for extension.\n- Express uncertainty and explore alternatives within the `thought` content.\n- Generate solution hypotheses within the `thought` content when appropriate.\n- Verify hypotheses in subsequent `thought` steps based on the reasoning chain.\n- The caller should repeat the process, calling this tool for each step, until a satisfactory solution is reached.\n- Set `nextThoughtNeeded=False` only when the caller determines the process is complete and a final answer is ready.\n\nParameters:\n    thought (str): The content of the current thinking step. This can be an analytical step,\n                   a plan, a question, a critique, a revision, a hypothesis, or verification.\n                   Make it specific enough to imply the desired action.\n    thoughtNumber (int): The sequence number of this thought (>=1). Can exceed initial `totalThoughts`\n                         if the process is extended.\n    totalThoughts (int): The current *estimate* of the total thoughts required for the process.\n                         This can be adjusted by the caller in subsequent calls. Minimum 5 suggested.\n    nextThoughtNeeded (bool): Indicates if the caller intends to make another call to this tool\n                              after the current one. Set to False only when the entire process is deemed complete.\n    isRevision (bool, optional): True if this thought revises or corrects a previous thought. Defaults to False.\n    revisesThought (int, optional): The `thoughtNumber` of the thought being revised, required if `isRevision` is True.\n                                    Must be less than the current `thoughtNumber`.\n    branchFromThought (int, optional): The `thoughtNumber` from which this thought branches to explore an alternative path.\n                                       Defaults to None.\n    branchId (str, optional): A unique identifier for the branch being explored, required if `branchFromThought` is set.\n                              Defaults to None.\n    needsMoreThoughts (bool, optional): Set to True on a thought if the caller anticipates needing more\n                                        steps beyond the current `totalThoughts` estimate *after* this thought.\n                                        Defaults to False.\n\nReturns:\n    str: The Coordinator agent's synthesized response based on specialist contributions for the current `thought`.\n         Includes guidance for the caller on potential next steps (e.g., suggestions for revision or branching\n         based on the specialists' analysis). The caller uses this response to formulate the *next* thought.\n"
+      }
+    }
   },
   "@kailashg101/mcp-figma-to-code": {
     "category": "developer-tools",
@@ -5961,7 +6003,38 @@
   },
   "awslabs.cdk-mcp-server": {
     "category": "cloud-platforms",
-    "path": "cloud-platforms/awslabs-cdk-mcp-server.json"
+    "path": "cloud-platforms/awslabs-cdk-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "CDKGeneralGuidance": {
+        "name": "CDKGeneralGuidance",
+        "description": "Use this tool to get prescriptive CDK advice for building applications on AWS.\n\nArgs:\n    ctx: MCP context\n"
+      },
+      "ExplainCDKNagRule": {
+        "name": "ExplainCDKNagRule",
+        "description": "Explain a specific CDK Nag rule with AWS Well-Architected guidance.\n\nCDK Nag is a crucial tool for ensuring your CDK applications follow AWS security best practices.\n\nBasic implementation:\n```typescript\nimport { App } from 'aws-cdk-lib';\nimport { AwsSolutionsChecks } from 'cdk-nag';\n\nconst app = new App();\n// Create your stack\nconst stack = new MyStack(app, 'MyStack');\n// Apply CDK Nag\nAwsSolutionsChecks.check(app);\n```\n\nOptional integration patterns:\n\n1. Using environment variables:\n```typescript\nif (process.env.ENABLE_CDK_NAG === 'true') {\n  AwsSolutionsChecks.check(app);\n}\n```\n\n2. Using CDK context parameters:\n```typescript\n3. Environment-specific application:\n```typescript\nconst environment = app.node.tryGetContext('environment') || 'development';\nif (['production', 'staging'].includes(environment)) {\n  AwsSolutionsChecks.check(stack);\n}\n```\n\nFor more information on specific rule packs:\n- Use resource `cdk-nag://rules/{rule_pack}` to get all rules for a specific pack\n- Use resource `cdk-nag://warnings/{rule_pack}` to get warnings for a specific pack\n- Use resource `cdk-nag://errors/{rule_pack}` to get errors for a specific pack\n\nArgs:\n    ctx: MCP context\n    rule_id: The CDK Nag rule ID (e.g., 'AwsSolutions-IAM4')\n\nReturns:\n    Dictionary with detailed explanation and remediation steps\n"
+      },
+      "CheckCDKNagSuppressions": {
+        "name": "CheckCDKNagSuppressions",
+        "description": "Check if CDK code contains Nag suppressions that require human review.\n\nScans TypeScript/JavaScript code for NagSuppressions usage to ensure security\nsuppressions receive proper human oversight and justification.\n\nArgs:\n    ctx: MCP context\n    code: CDK code to analyze (TypeScript/JavaScript)\n    file_path: Path to a file containing CDK code to analyze\n\nReturns:\n    Analysis results with suppression details and security guidance\n"
+      },
+      "GenerateBedrockAgentSchema": {
+        "name": "GenerateBedrockAgentSchema",
+        "description": "Generate OpenAPI schema for Bedrock Agent Action Groups from a file.\n\nThis tool converts a Lambda file with BedrockAgentResolver into a Bedrock-compatible\nOpenAPI schema. It uses a progressive approach to handle common issues:\n1. Direct import of the Lambda file\n2. Simplified version with problematic imports commented out\n3. Fallback script generation if needed\n\nArgs:\n    ctx: MCP context\n    lambda_code_path: Path to Python file containing BedrockAgentResolver app\n    output_path: Where to save the generated schema\n\nReturns:\n    Dictionary with schema generation results, including status, path to generated schema,\n    and diagnostic information if errors occurred\n"
+      },
+      "GetAwsSolutionsConstructPattern": {
+        "name": "GetAwsSolutionsConstructPattern",
+        "description": "Search and discover AWS Solutions Constructs patterns.\n\nAWS Solutions Constructs are vetted architecture patterns that combine multiple\nAWS services to solve common use cases following AWS Well-Architected best practices.\n\nKey benefits:\n- Accelerated Development: Implement common patterns without boilerplate code\n- Best Practices Built-in: Security, reliability, and performance best practices\n- Reduced Complexity: Simplified interfaces for multi-service architectures\n- Well-Architected: Patterns follow AWS Well-Architected Framework principles\n\nWhen to use Solutions Constructs:\n- Implementing common architecture patterns (e.g., API + Lambda + DynamoDB)\n- You want secure defaults and best practices applied automatically\n- You need to quickly prototype or build production-ready infrastructure\n\nThis tool provides metadata about patterns. For complete documentation,\nuse the resource URI returned in the 'documentation_uri' field.\n\nArgs:\n    ctx: MCP context\n    pattern_name: Optional name of the specific pattern (e.g., 'aws-lambda-dynamodb')\n    services: Optional list of AWS services to search for patterns that use them\n             (e.g., ['lambda', 'dynamodb'])\n\nReturns:\n    Dictionary with pattern metadata including description, services, and documentation URI\n"
+      },
+      "SearchGenAICDKConstructs": {
+        "name": "SearchGenAICDKConstructs",
+        "description": "Search for GenAI CDK constructs by name or type.\n\nThe search is flexible and will match any of your search terms (OR logic).\nIt handles common variations like singular/plural forms and terms with/without spaces.\nContent is fetched dynamically from GitHub to ensure the most up-to-date documentation.\n\nExamples:\n- \"bedrock agent\" - Returns all agent-related constructs\n- \"knowledgebase vector\" - Returns knowledge base constructs related to vector stores\n- \"agent actiongroups\" - Returns action groups for agents\n- \"opensearch vector\" - Returns OpenSearch vector constructs\n\nThe search supports subdirectory content (like knowledge bases and their sections)\nand will find matches across all available content.\n\nArgs:\n    ctx: MCP context\n    query: Search term(s) to find constructs by name or description\n    construct_type: Optional filter by construct type ('bedrock', 'opensearchserverless', etc.)\n\nReturns:\n    Dictionary with matching constructs and resource URIs\n"
+      },
+      "LambdaLayerDocumentationProvider": {
+        "name": "LambdaLayerDocumentationProvider",
+        "description": "Provide documentation sources for Lambda layers.\n\nThis tool returns information about where to find documentation for Lambda layers\nand instructs the MCP Client to fetch and process this documentation.\n\nArgs:\n    ctx: MCP context\n    layer_type: Type of layer (\"generic\" or \"python\")\n\nReturns:\n    Dictionary with documentation source information\n"
+      }
+    }
   },
   "@niyogi/render-mcp": {
     "category": "cloud-platforms",
@@ -6568,7 +6641,14 @@
   },
   "mcp-shell-server": {
     "category": "command-line",
-    "path": "command-line/mcp-shell-server.json"
+    "path": "command-line/mcp-shell-server.json",
+    "validated": true,
+    "tools": {
+      "shell_execute": {
+        "name": "shell_execute",
+        "description": "Execute a shell command\nAllowed commands: "
+      }
+    }
   },
   "apple-macos-native-applications": {
     "category": "command-line",
@@ -6584,7 +6664,34 @@
   },
   "wcgw": {
     "category": "command-line",
-    "path": "command-line/wcgw.json"
+    "path": "command-line/wcgw.json",
+    "validated": true,
+    "tools": {
+      "Initialize": {
+        "name": "Initialize",
+        "description": "\n- Always call this at the start of the conversation before using any of the shell tools from wcgw.\n- Use `any_workspace_path` to initialize the shell in the appropriate project directory.\n- If the user has mentioned a workspace or project root or any other file or folder use it to set `any_workspace_path`.\n- If user has mentioned any files use `initial_files_to_read` to read, use absolute paths only (~ allowed)\n- By default use mode \"wcgw\"\n- In \"code-writer\" mode, set the commands and globs which user asked to set, otherwise use 'all'.\n- Use type=\"first_call\" if it's the first call to this tool.\n- Use type=\"user_asked_mode_change\" if in a conversation user has asked to change mode.\n- Use type=\"reset_shell\" if in a conversation shell is not working after multiple tries.\n- Use type=\"user_asked_change_workspace\" if in a conversation user asked to change workspace\n"
+      },
+      "BashCommand": {
+        "name": "BashCommand",
+        "description": "\n- Execute a bash command. This is stateful (beware with subsequent calls).\n- Status of the command and the current working directory will always be returned at the end.\n- The first or the last line might be `(...truncated)` if the output is too long.\n- Always run `pwd` if you get any file or directory not found error to make sure you're not lost.\n- Run long running commands in background using screen instead of \"&\".\n- Do not use 'cat' to read files, use ReadFiles tool instead\n- In order to check status of previous command, use `status_check` with empty command argument.\n- Only command is allowed to run at a time. You need to wait for any previous command to finish before running a new one.\n- Programs don't hang easily, so most likely explanation for no output is usually that the program is still running, and you need to check status again.\n- Do not send Ctrl-c before checking for status till 10 minutes or whatever is appropriate for the program to finish.\n"
+      },
+      "ReadFiles": {
+        "name": "ReadFiles",
+        "description": "\n- Read full file content of one or more files.\n- Provide absolute paths only (~ allowed)\n- Only if the task requires line numbers understanding:\n    - You may extract a range of lines. E.g., `/path/to/file:1-10` for lines 1-10. You can drop start or end like `/path/to/file:1-` or `/path/to/file:-10` \n"
+      },
+      "ReadImage": {
+        "name": "ReadImage",
+        "description": "Read an image from the shell."
+      },
+      "FileWriteOrEdit": {
+        "name": "FileWriteOrEdit",
+        "description": "\n- Writes or edits a file based on the percentage of changes.\n- Use absolute path only (~ allowed).\n- First write down percentage of lines that need to be replaced in the file (between 0-100) in percentage_to_change\n- percentage_to_change should be low if mostly new code is to be added. It should be high if a lot of things are to be replaced.\n- If percentage_to_change > 50, provide full file content in text_or_search_replace_blocks\n- If percentage_to_change <= 50, text_or_search_replace_blocks should be search/replace blocks.\n\nInstructions for editing files.\n# Example\n## Input file\n```\nimport numpy as np\nfrom impls import impl1, impl2\n\ndef hello():\n    \"print a greeting\"\n\n    print(\"hello\")\n\ndef call_hello():\n    \"call hello\"\n\n    hello()\n    print(\"Called\")\n    impl1()\n    hello()\n    impl2()\n\n```\n## Edit format on the input file\n```\n<<<<<<< SEARCH\nfrom impls import impl1, impl2\n=======\nfrom impls import impl1, impl2\nfrom hello import hello as hello_renamed\n>>>>>>> REPLACE\n<<<<<<< SEARCH\ndef hello():\n    \"print a greeting\"\n\n    print(\"hello\")\n=======\n>>>>>>> REPLACE\n<<<<<<< SEARCH\ndef call_hello():\n    \"call hello\"\n\n    hello()\n=======\ndef call_hello_renamed():\n    \"call hello renamed\"\n\n    hello_renamed()\n>>>>>>> REPLACE\n<<<<<<< SEARCH\n    impl1()\n    hello()\n    impl2()\n=======\n    impl1()\n    hello_renamed()\n    impl2()\n>>>>>>> REPLACE\n```\n\n# *SEARCH/REPLACE block* Rules:\n\n- Every \"SEARCH\" section must *EXACTLY MATCH* the existing file content, character for character, including all comments, docstrings, whitespaces, etc.\n- Use multiple search/replace blocks in a single FileWriteOrEdit tool call to edit in a single file in multiple places from top to bottom (separate calls are slower).\n- Including multiple unique *SEARCH/REPLACE* blocks if needed.\n- Include enough and only enough lines in each SEARCH section to uniquely match each set of lines that need to change.\n- Keep *SEARCH/REPLACE* blocks concise.\n- Break large *SEARCH/REPLACE* blocks into a series of smaller blocks that each change a small portion of the file.\n- Include just the changing lines, and a few surrounding lines (0-3 lines) if needed for uniqueness.\n- Other than for uniqueness, avoid including those lines which do not change in search (and replace) blocks. Target 0-3 non trivial extra lines per block.\n- Preserve leading spaces and indentations in both SEARCH and REPLACE blocks."
+      },
+      "ContextSave": {
+        "name": "ContextSave",
+        "description": "\nSaves provided description and file contents of all the relevant file paths or globs in a single text file.\n- Provide random 3 word unqiue id or whatever user provided.\n- Leave project path as empty string if no project path"
+      }
+    }
   },
   "terminal-controller": {
     "category": "command-line",
@@ -6682,7 +6789,94 @@
   },
   "phone-mcp": {
     "category": "command-line",
-    "path": "command-line/phone-mcp.json"
+    "path": "command-line/phone-mcp.json",
+    "validated": true,
+    "tools": {
+      "call_number": {
+        "name": "call_number",
+        "description": "Make a phone call to the specified number.\n\nInitiates a call using Android's dialer app through ADB. The number\nwill be dialed immediately without requiring user confirmation.\n\nArgs:\n    phone_number (str): The phone number to call. Country code\n                      will be automatically added if not provided.\n\nReturns:\n    str: Success message with the number being called, or an error message\n         if the call could not be initiated.\n"
+      },
+      "end_call": {
+        "name": "end_call",
+        "description": "End the current phone call.\n\nTerminates any active phone call by sending the end call keycode\nthrough ADB.\n\nReturns:\n    str: Success message if the call was ended, or an error message\n         if the end call command failed.\n"
+      },
+      "check_device_connection": {
+        "name": "check_device_connection",
+        "description": "Check if an Android device is connected via ADB.\n\nVerifies that an Android device is properly connected and recognized\nby ADB, which is required for all other functions to work.\n\nReturns:\n    str: Status message indicating whether a device is connected and\n         ready, or an error message if no device is found.\n"
+      },
+      "send_text_message": {
+        "name": "send_text_message",
+        "description": "Send a text message to the specified number.\n\nUses the phone's messaging app with UI automation to send SMS.\nProcess: Opens messaging app, fills recipient and content, automatically clicks send button, then auto-exits app.\n\nArgs:\n    phone_number (str): Recipient's phone number. Country code will be automatically added if not included.\n                      Example: \"13812345678\" or \"+8613812345678\"\n    message (str): SMS content. Supports any text, including emojis.\n                 Example: \"Hello, this is a test message\"\n\nReturns:\n    str: String description of the operation result:\n         - Success: \"Text message sent to {phone_number}\"\n         - Failure: Message containing error reason, like \"Failed to open messaging app: {error}\"\n                   or \"Failed to navigate to send button: {error}\"\n"
+      },
+      "receive_text_messages": {
+        "name": "receive_text_messages",
+        "description": "Get recent text messages from the phone.\n\nRetrieves recent SMS messages from the device's SMS database\nusing ADB and content provider queries to get structured message data.\n\nArgs:\n    limit (int): Maximum number of messages to retrieve (default: 5)\n                Example: 10 will return the 10 most recent messages\n\nReturns:\n    str: JSON string containing messages or an error message:\n         - Success: Formatted JSON string with list of messages, each with fields:\n                   - address: Sender's number\n                   - body: Message content\n                   - date: Timestamp\n                   - formatted_date: Human-readable date time (like \"2023-07-25 14:30:22\")\n         - Failure: Text message describing the error, like \"No recent text messages found...\"\n"
+      },
+      "get_sent_messages": {
+        "name": "get_sent_messages",
+        "description": "Get recently sent text messages from the phone.\n\nRetrieves sent SMS messages from the device's SMS database.\nThis provides a complete list of messages that were successfully sent from this device.\n\nArgs:\n    limit (int): Maximum number of sent messages to retrieve (default: 5)\n\nReturns:\n    str: JSON string containing sent messages with:\n         - from: Sender phone number (device owner)\n         - to: Recipient phone number\n         - text: Message content\n         - date: Timestamp\n         - formatted_date: Human-readable date time (like \"2023-07-25 14:30:22\")\n"
+      },
+      "start_screen_recording": {
+        "name": "start_screen_recording",
+        "description": "Start recording the phone's screen.\n\nRecords the screen activity for the specified duration and saves\nthe video to the phone's storage. Automatically creates directories\nif they don't exist.\n\nArgs:\n    duration_seconds (int): Recording duration in seconds (default: 30,\n                           max: 180 seconds due to ADB limitations)\n\nReturns:\n    str: Success message with the path to the recording, or an error\n         message if the recording could not be started.\n"
+      },
+      "play_media": {
+        "name": "play_media",
+        "description": "Simulate media button press to play/pause media.\n\nThis function sends a keyevent that simulates pressing the media\nplay/pause button, which can control music, videos, or podcasts\nthat are currently playing.\n\nReturns:\n    str: Success message, or an error message if the command failed.\n"
+      },
+      "set_alarm": {
+        "name": "set_alarm",
+        "description": "Set an alarm on the phone.\n\nCreates a new alarm with the specified time and label using the default\nclock application.\n\nArgs:\n    hour (int): Hour in 24-hour format (0-23)\n    minute (int): Minute (0-59)\n    label (str): Optional label for the alarm (default: \"Alarm\")\n\nReturns:\n    str: Success message if the alarm was set, or an error message\n         if the alarm could not be created.\n"
+      },
+      "receive_incoming_call": {
+        "name": "receive_incoming_call",
+        "description": "Handle an incoming phone call.\n\nChecks for any incoming calls and provides options to answer\nor reject the call. This function first checks if there's an\nincoming call, then can either answer it or reject it based\non the action parameter.\n\nReturns:\n    str: Information about any incoming call including the caller\n         number, or a message indicating no incoming calls.\n"
+      },
+      "get_contacts": {
+        "name": "get_contacts",
+        "description": "Retrieve contacts from the phone.\n\nCore function for accessing the contacts database on the device.\nFetches contact information including names and phone numbers.\nReturns data in structured JSON format.\n\nArgs:\n    limit (int): Number of contacts to retrieve, defaults to 20\n\nReturns:\n    str: JSON string with contact data or error message\n"
+      },
+      "create_contact": {
+        "name": "create_contact",
+        "description": "Create a new contact on the phone.\n\nOpens the contact creation UI with pre-filled name and phone number,\nallowing the user to review and save the contact.\n\nArgs:\n    name (str): The contact's full name\n    phone_number (str): The contact's phone number (For testing, 10086 is recommended)\n    email (str, optional): The contact's email address\n\nReturns:\n    str: Success message if the contact UI was launched, or an error message\n         if the operation failed.\n\nNote:\n    When testing this feature, it's recommended to use 10086 as the test phone number.\n    This is China Mobile's customer service number, which is suitable for testing\n    environments and easy to recognize.\n"
+      },
+      "get_current_window": {
+        "name": "get_current_window",
+        "description": "Get information about the current active window on the device.\n\nRetrieves details about the currently focused window, active application,\nand foreground activities on the device using multiple methods for reliability.\n\nReturns:\n    str: JSON string with current window details or error message\n"
+      },
+      "get_app_shortcuts": {
+        "name": "get_app_shortcuts",
+        "description": "Get application shortcuts for installed apps.\n\nRetrieves shortcuts (quick actions) available for Android apps.\nIf package_name is provided, returns shortcuts only for that app,\notherwise lists all apps with shortcuts.\n\nArgs:\n    package_name (str, optional): Specific app package to get shortcuts for\n\nReturns:\n    str: JSON string with app shortcuts information or error message\n"
+      },
+      "launch_app_activity": {
+        "name": "launch_app_activity",
+        "description": "Launch an app using package name and optionally an activity name\n\nThis function uses adb to start an application on the device either by package name\nor by specifying both package and activity. It provides reliable app launching across\ndifferent Android devices and versions.\n\nArgs:\n    package_name (str): The package name of the app to launch (e.g., \"com.android.contacts\")\n    activity_name (str): The specific activity to launch. If not provided,\n                                  launches the app's main activity. Defaults to None.\n\nReturns:\n    str: JSON string with operation result:\n        For successful operations:\n            {\n                \"status\": \"success\",\n                \"message\": \"Successfully launched <package_name>\"\n            }\n        \n        For failed operations:\n            {\n                \"status\": \"error\",\n                \"message\": \"Failed to launch app: <error details>\"\n            }\n\nExamples:\n    # Launch an app using just the package name\n    result = await launch_app_activity(\"com.android.contacts\")\n    \n    # Launch a specific activity within an app\n    result = await launch_app_activity(\"com.android.dialer\", \"com.android.dialer.DialtactsActivity\")\n    \n    # Launch Android settings\n    result = await launch_app_activity(\"com.android.settings\")\n"
+      },
+      "list_installed_apps": {
+        "name": "list_installed_apps",
+        "description": "List installed applications on the device with pagination support.\n\nArgs:\n    only_system (bool): If True, only show system apps\n    only_third_party (bool): If True, only show third-party apps\n    page (int): Page number (starts from 1)\n    page_size (int): Number of items per page\n    basic (bool): If True, only return basic info (faster loading, default behavior)\n\nReturns:\n    str: JSON string containing:\n        {\n            \"status\": \"success\" or \"error\",\n            \"message\": Error message if status is error,\n            \"total_count\": Total number of apps,\n            \"total_pages\": Total number of pages,\n            \"current_page\": Current page number,\n            \"page_size\": Number of items per page,\n            \"apps\": [\n                {\n                    \"package_name\": str,\n                    \"app_name\": str,\n                    \"system_app\": bool,\n                    \"version_name\": str (if not basic),\n                    \"version_code\": str (if not basic),\n                    \"install_time\": str (if not basic)\n                },\n                ...\n            ]\n        }\n"
+      },
+      "terminate_app": {
+        "name": "terminate_app",
+        "description": "Force stop an application on the device.\n\nArgs:\n    package_name (str): Package name of the app to terminate\n\nReturns:\n    str: Success or error message\n"
+      },
+      "open_url": {
+        "name": "open_url",
+        "description": "Open a URL in the device's default browser.\n\nArgs:\n    url (str): URL to open\n\nReturns:\n    str: Success or error message\n"
+      },
+      "analyze_screen": {
+        "name": "analyze_screen",
+        "description": "Analyze the current screen and provide structured information about UI elements\n\nThis function captures the current screen state and returns a detailed analysis\nof the UI elements, their attributes, and suggests possible interactions.\n\nArgs:\n    include_screenshot (bool, optional): Whether to include base64-encoded screenshot in the result.\n                                      Default is False to reduce response size.\n    max_elements (int, optional): Maximum number of UI elements to process.\n                                Default is 50 to limit processing time and response size.\n\nReturns:\n    str: JSON string with the analysis result containing:\n        {\n            \"status\": \"success\" or \"error\",\n            \"message\": \"Success/error message\",\n            \"screen_size\": {\n                \"width\": Width of the screen in pixels,\n                \"height\": Height of the screen in pixels\n            },\n            \"screen_analysis\": {\n                \"text_elements\": {\n                    \"all\": [List of all text elements with coordinates],\n                    \"by_region\": {\n                        \"top\": [Text elements in the top of the screen],\n                        \"middle\": [Text elements in the middle of the screen],\n                        \"bottom\": [Text elements in the bottom of the screen]\n                    }\n                },\n                \"notable_clickables\": [List of important clickable elements],\n                \"ui_patterns\": {\n                    \"has_bottom_nav\": Whether screen has bottom navigation,\n                    \"has_top_bar\": Whether screen has top app bar,\n                    \"has_dialog\": Whether screen has a dialog showing,\n                    \"has_list_view\": Whether screen has a scrollable list\n                }\n            },\n            \"suggested_actions\": [\n                {\n                    \"action\": Action type (e.g., \"tap_element\"),\n                    \"element_text\": Text of element to interact with,\n                    \"element_id\": ID of element to interact with,\n                    \"coordinates\": [x, y] coordinates for interaction,\n                    \"confidence\": Confidence score (0-100)\n                }\n            ]\n        }\n    \n    If include_screenshot is True, the response will also include:\n    {\n        \"screenshot\": base64-encoded PNG image of the screen\n    }\n    \nExamples:\n    # Basic screen analysis\n    result = await analyze_screen()\n    \n    # Get screen analysis with screenshot included\n    result_with_screenshot = await analyze_screen(include_screenshot=True)\n    \n    # Get detailed analysis including more elements\n    detailed_result = await analyze_screen(max_elements=100)\n"
+      },
+      "interact_with_screen": {
+        "name": "interact_with_screen",
+        "description": "Execute screen interaction actions\n\nUnified interface for screen interactions including tapping, swiping, key pressing, text input, and element search.\n\nArgs:\n    action (str): Action type, one of:\n        - \"tap\": Tap screen at specified coordinates\n        - \"swipe\": Swipe screen from one position to another\n        - \"key\": Press a system key\n        - \"text\": Input text\n        - \"find\": Find UI element(s)\n        - \"wait\": Wait for element to appear\n        - \"scroll\": Scroll to find element\n        \n    params (Dict[str, Any]): Parameters dictionary with action-specific values:\n        For \"tap\" action:\n            - x (int): X coordinate to tap\n            - y (int): Y coordinate to tap\n        \n        For \"swipe\" action:\n            - x1 (int): Start X coordinate\n            - y1 (int): Start Y coordinate\n            - x2 (int): End X coordinate\n            - y2 (int): End Y coordinate\n            - duration (int, optional): Swipe duration in ms, defaults to 300\n        \n        For \"key\" action:\n            - keycode (str/int): Key to press (e.g., \"back\", \"home\", \"enter\", or keycode number)\n        \n        For \"text\" action:\n            - content (str): Text to input. For Chinese characters, use pinyin instead\n                          (e.g. \"yu\\ tian\" for \"雨天\") with escaped spaces.\n                          Direct Chinese character input may fail on some devices.\n        \n        For \"find\" action:\n            - method (str): Search method, one of: \"text\", \"id\", \"content_desc\", \"class\", \"clickable\"\n            - value (str): Text/value to search for (not required for method=\"clickable\")\n            - partial (bool, optional): Use partial matching, defaults to True (for text/content_desc)\n        \n        For \"wait\" action:\n            - method (str): Search method, same options as \"find\"\n            - value (str): Text/value to search for\n            - timeout (int, optional): Maximum wait time in seconds, defaults to 30\n            - interval (float, optional): Check interval in seconds, defaults to 1.0\n        \n        For \"scroll\" action:\n            - method (str): Search method, same options as \"find\"\n            - value (str): Text/value to search for\n            - direction (str, optional): Scroll direction, one of: \"up\", \"down\", \"left\", \"right\", defaults to \"down\"\n            - max_swipes (int, optional): Maximum swipe attempts, defaults to 5\n\nReturns:\n    str: JSON string with operation result containing:\n        For successful operations:\n            {\n                \"status\": \"success\",\n                \"message\": \"Operation-specific success message\",\n                ... (optional action-specific data)\n            }\n        \n        For failed operations:\n            {\n                \"status\": \"error\",\n                \"message\": \"Error description\"\n            }\n        \n        Special cases:\n            - find: Returns elements list containing matching elements with their properties\n            - wait: Returns success when element found or error if timeout\n            - scroll: Returns success when element found or error if not found after max attempts\n\nExamples:\n    # Tap by coordinates\n    result = await interact_with_screen(\"tap\", {\"x\": 100, \"y\": 200})\n    \n    # Swipe down\n    result = await interact_with_screen(\"swipe\", \n                                       {\"x1\": 500, \"y1\": 300, \n                                        \"x2\": 500, \"y2\": 1200, \n                                        \"duration\": 300})\n    \n    # Input text\n    result = await interact_with_screen(\"text\", {\"content\": \"Hello world\"})\n    \n    # Press back key\n    result = await interact_with_screen(\"key\", {\"keycode\": \"back\"})\n    \n    # Find element by text\n    result = await interact_with_screen(\"find\", \n                                       {\"method\": \"text\", \n                                        \"value\": \"Settings\", \n                                        \"partial\": True})\n    \n    # Wait for element to appear\n    result = await interact_with_screen(\"wait\", \n                                       {\"method\": \"text\", \n                                        \"value\": \"Success\", \n                                        \"timeout\": 10,\n                                        \"interval\": 0.5})\n                                        \n    # Scroll to find element\n    result = await interact_with_screen(\"scroll\", \n                                       {\"method\": \"text\", \n                                        \"value\": \"Privacy Policy\", \n                                        \"direction\": \"down\", \n                                        \"max_swipes\": 8})\n"
+      },
+      "mcp_monitor_ui_changes": {
+        "name": "mcp_monitor_ui_changes",
+        "description": "Monitor the UI for changes with MCP compatible parameters.\n\nThis is a simplified version of monitor_ui_changes that doesn't use callback functions,\nmaking it compatible with MCP's JSON schema requirements.\n\nArgs:\n    interval_seconds (float): Time between UI checks (seconds)\n    max_duration_seconds (float): Maximum monitoring time (seconds)\n    watch_for (str): What to watch for - \"any_change\", \"text_appears\", \"text_disappears\", \n                    \"id_appears\", \"id_disappears\", \"class_appears\", \"content_desc_appears\"\n    target_text (str): Text to watch for (when watch_for includes \"text\")\n    target_id (str): ID to watch for (when watch_for includes \"id\")\n    target_class (str): Class to watch for (when watch_for includes \"class\")\n    target_content_desc (str): Content description to watch for (when watch_for includes \"content_desc\")\n\nReturns:\n    str: JSON string with monitoring results\n"
+      }
+    }
   },
   "mcp-windows": {
     "category": "command-line",
@@ -6724,7 +6918,26 @@
   },
   "mcp-server-macos-defaults": {
     "category": "command-line",
-    "path": "command-line/mcp-server-macos-defaults.json"
+    "path": "command-line/mcp-server-macos-defaults.json",
+    "validated": true,
+    "tools": {
+      "list-domains": {
+        "name": "list-domains",
+        "description": "List all available macOS domains, same as `defaults domains`"
+      },
+      "find": {
+        "name": "find",
+        "description": "Find entries container given word"
+      },
+      "defaults-read": {
+        "name": "defaults-read",
+        "description": "use the `defaults read <domain> <key>` command"
+      },
+      "defaults-write": {
+        "name": "defaults-write",
+        "description": "use the `defaults write <domain> <key> <value>` command"
+      }
+    }
   },
   "hyprland": {
     "category": "embedded-system",
@@ -6748,7 +6961,30 @@
   },
   "macos-notification-mcp": {
     "category": "command-line",
-    "path": "command-line/macos-notification-mcp.json"
+    "path": "command-line/macos-notification-mcp.json",
+    "validated": true,
+    "tools": {
+      "sound_notification": {
+        "name": "sound_notification",
+        "description": "\nPlay a system sound notification.\n\nArgs:\n    sound_name: Name of the system sound to play (default: \"Submarine\")\n               Options: Basso, Blow, Bottle, Frog, Funk, Glass, Hero, \n               Morse, Ping, Pop, Purr, Sosumi, Submarine, Tink\n\nReturns:\n    A message indicating whether the sound was played successfully\n"
+      },
+      "banner_notification": {
+        "name": "banner_notification",
+        "description": "\nDisplay a banner notification on macOS.\n\nArgs:\n    title: The title of the notification\n    message: The main content of the notification\n    subtitle: Optional subtitle for the notification\n    sound: Whether to play a sound with the notification (default: False)\n    sound_name: Optional system sound to play (default: None, uses system default)\n\nReturns:\n    A message indicating the notification was sent\n"
+      },
+      "speak_notification": {
+        "name": "speak_notification",
+        "description": "\nUse macOS text-to-speech to speak a message.\n\nArgs:\n    text: The text to speak\n    voice: Optional voice to use (default: system default)\n    rate: Speech rate, words per minute (default: 150)\n    volume: Volume level from 0.0 to 1.0 (default: 1.0)\n\nReturns:\n    A message indicating the text was spoken\n"
+      },
+      "list_available_voices": {
+        "name": "list_available_voices",
+        "description": "\nList all available text-to-speech voices on the system.\n\nReturns:\n    A string listing all available voices\n"
+      },
+      "test_notification_system": {
+        "name": "test_notification_system",
+        "description": "\nTest the notification system by trying all notification methods.\n\nReturns:\n    A diagnostic report of the notification system\n"
+      }
+    }
   },
   "kubernetes-eye": {
     "category": "command-line",
@@ -6770,7 +7006,14 @@
   },
   "mcp-kubernetes-server": {
     "category": "command-line",
-    "path": "command-line/mcp-kubernetes-server.json"
+    "path": "command-line/mcp-kubernetes-server.json",
+    "validated": true,
+    "tools": {
+      "kubectl": {
+        "name": "kubectl",
+        "description": "Run a kubectl command and return the output."
+      }
+    }
   },
   "terminal-control": {
     "category": "command-line",
@@ -6995,7 +7238,34 @@
   },
   "gmail-mcp": {
     "category": "communication",
-    "path": "communication/gmail-mcp.json"
+    "path": "communication/gmail-mcp.json",
+    "validated": true,
+    "tools": {
+      "perform-email-search": {
+        "name": "perform-email-search",
+        "description": "Searches the user's Gmail with various filters and returns complete contents."
+      },
+      "modify-draft-prompt": {
+        "name": "modify-draft-prompt",
+        "description": "Automatically adapts email writing style when user expresses preferences or concerns about communication style. This tool helps maintain personalized communication patterns for different contacts and contexts."
+      },
+      "list-new-emails": {
+        "name": "list-new-emails",
+        "description": "Retrieves and lists all new emails found during Gmail index update."
+      },
+      "get-draft-prompt": {
+        "name": "get-draft-prompt",
+        "description": "Retrieves the draft prompt template for composing a response.\n        \n        IMPORTANT: After getting this prompt:\n        1. Use it IMMEDIATELY to write your draft\n        2. Call write-draft-email with your draft\n        \n        Only call this tool when you have all needed information and are ready to write."
+      },
+      "write-draft-email": {
+        "name": "write-draft-email",
+        "description": "Shows the draft email to the user in the chat.\n        \n        IMPORTANT: After calling this tool:\n        1. Present the draft content directly in your message (don't leave it in the expandable window)\n        2. Ask the user to review and reply with 'SEND' to approve\n        \n        This tool helps ensure drafts are always properly shown to users before sending."
+      },
+      "send-approved-email": {
+        "name": "send-approved-email",
+        "description": "Sends an email that was previously shown and approved by the user.\n        \n        IMPORTANT: This tool must ONLY be called after:\n        1. A draft was shown using write-draft-email\n        2. The user responded with exactly 'SEND'\n        \n        NEVER call this tool without first showing the draft via write-draft-email."
+      }
+    }
   },
   "mcp-email-server": {
     "category": "communication",
@@ -7007,7 +7277,14 @@
   },
   "mcp-wechat-moments": {
     "category": "communication",
-    "path": "communication/mcp-wechat-moments.json"
+    "path": "communication/mcp-wechat-moments.json",
+    "validated": true,
+    "tools": {
+      "send_moments": {
+        "name": "send_moments",
+        "description": ""
+      }
+    }
   },
   "@prathamesh0901/zoom-mcp-server": {
     "category": "communication",
@@ -7298,7 +7575,94 @@
   },
   "mcp-server-monday": {
     "category": "support-service-management",
-    "path": "support-service-management/mcp-server-monday.json"
+    "path": "support-service-management/mcp-server-monday.json",
+    "validated": true,
+    "tools": {
+      "monday-create-item": {
+        "name": "monday-create-item",
+        "description": "Create a new item in a Monday.com Board. Optionally, specify the parent Item ID to create a Sub-item."
+      },
+      "monday-get-items-by-id": {
+        "name": "monday-get-items-by-id",
+        "description": "Fetch specific Monday.com item by its ID"
+      },
+      "monday-update-item": {
+        "name": "monday-update-item",
+        "description": "Update a Monday.com item's or sub-item's column values."
+      },
+      "monday-get-board-columns": {
+        "name": "monday-get-board-columns",
+        "description": "Get the Columns of a Monday.com Board."
+      },
+      "monday-get-board-groups": {
+        "name": "monday-get-board-groups",
+        "description": "Get the Groups of a Monday.com Board."
+      },
+      "monday-create-update": {
+        "name": "monday-create-update",
+        "description": "Create an update (comment) on a Monday.com Item or Sub-item."
+      },
+      "monday-list-boards": {
+        "name": "monday-list-boards",
+        "description": "Get all Boards from Monday.com"
+      },
+      "monday-list-items-in-groups": {
+        "name": "monday-list-items-in-groups",
+        "description": "List all items in the specified groups of a Monday.com board"
+      },
+      "monday-list-subitems-in-items": {
+        "name": "monday-list-subitems-in-items",
+        "description": "List all Sub-items of a list of Monday.com Items"
+      },
+      "monday-create-board": {
+        "name": "monday-create-board",
+        "description": "Create a new Monday.com board"
+      },
+      "monday-create-board-group": {
+        "name": "monday-create-board-group",
+        "description": "Create a new group in a Monday.com board"
+      },
+      "monday-move-item-to-group": {
+        "name": "monday-move-item-to-group",
+        "description": "Move an item to a group in a Monday.com board"
+      },
+      "monday-delete-item": {
+        "name": "monday-delete-item",
+        "description": "Delete an item from a Monday.com board"
+      },
+      "monday-archive-item": {
+        "name": "monday-archive-item",
+        "description": "Archive an item from a Monday.com board"
+      },
+      "monday-get-item-updates": {
+        "name": "monday-get-item-updates",
+        "description": "Get updates for a specific item in Monday.com"
+      },
+      "monday-get-docs": {
+        "name": "monday-get-docs",
+        "description": "Get a list of documents from Monday.com."
+      },
+      "monday-get-doc-content": {
+        "name": "monday-get-doc-content",
+        "description": "Get the content of a specific document by ID"
+      },
+      "monday-create-doc": {
+        "name": "monday-create-doc",
+        "description": "Create a new document in Monday.com. Specify either workspace_id (with kind) or board_id (with column_id and item_id) as the location."
+      },
+      "monday-add-doc-block": {
+        "name": "monday-add-doc-block",
+        "description": "Add a block to a document"
+      },
+      "monday-get-item-files": {
+        "name": "monday-get-item-files",
+        "description": "Get files (PDFs, documents, images, etc.) attached to a Monday.com item"
+      },
+      "monday-get-update-files": {
+        "name": "monday-get-update-files",
+        "description": "Get files (PDFs, documents, images, etc.) attached to a specific update in Monday.com"
+      }
+    }
   },
   "@horizondatawave/mcp": {
     "category": "communication",
@@ -7898,7 +8262,18 @@
   },
   "mcp-fleur": {
     "category": "communication",
-    "path": "communication/mcp-fleur.json"
+    "path": "communication/mcp-fleur.json",
+    "validated": true,
+    "tools": {
+      "hello_fleur": {
+        "name": "hello_fleur",
+        "description": "Explain what Fleur is when a user types 'hello fleur'.\n\nReturns:\n    str: An explanation about Fleur if triggered, empty string otherwise\n"
+      },
+      "open_fleur": {
+        "name": "open_fleur",
+        "description": "Open the Fleur app.\n\nReturns:\n    str: A message indicating that the Fleur app has been opened\n"
+      }
+    }
   },
   "@merill/lokka": {
     "category": "communication",
@@ -7908,7 +8283,14 @@
   },
   "wecom-bot-mcp-server": {
     "category": "communication",
-    "path": "communication/wecom-bot-mcp-server.json"
+    "path": "communication/wecom-bot-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "send_message": {
+        "name": "send_message",
+        "description": "Send a message to WeCom group/chat via webhook.\n\nThis function sends a message to WeCom using the configured webhook URL.\nThe message will be formatted as markdown and added to message history.\n\nArgs:\n    content: The message content to send. Cannot be empty or whitespace.\n    ctx: Optional FastMCP context for logging and progress tracking.\n\nReturns:\n    str: Success message if the message was sent successfully.\n\nRaises:\n    ValueError: If content is empty/whitespace, webhook URL is not set,\n               or if there's an error sending the message.\n"
+      }
+    }
   },
   "outlook-email": {
     "category": "communication",
@@ -7985,7 +8367,18 @@
   },
   "mcp-server-email": {
     "category": "communication",
-    "path": "communication/mcp-server-email.json"
+    "path": "communication/mcp-server-email.json",
+    "validated": true,
+    "tools": {
+      "send_email": {
+        "name": "send_email",
+        "description": "A tool that sends emails based on the provided subject, body and receiver. \n                            It ensures secure and accurate email delivery while supporting multiple recipients and custom content. \n                            Ideal for automating email workflows. \n                            After collecting the information, it needs to be displayed to the user, and then selected to send after the user confirms it."
+      },
+      "search_attachments": {
+        "name": "search_attachments",
+        "description": "Searches for files in a specified directory that match a given pattern. \n                            The search can be case-insensitive and returns the full paths of all matching files.\n                            This tool is useful for locating specific files or attachments within a directory structure."
+      }
+    }
   },
   "@hubspot/mcp-server": {
     "category": "customer-data-platforms",
@@ -8215,7 +8608,30 @@
   },
   "mcp-server-starrocks": {
     "category": "databases",
-    "path": "databases/mcp-server-starrocks.json"
+    "path": "databases/mcp-server-starrocks.json",
+    "validated": true,
+    "tools": {
+      "read_query": {
+        "name": "read_query",
+        "description": "Execute a SELECT query or commands that return a ResultSet"
+      },
+      "write_query": {
+        "name": "write_query",
+        "description": "Execute an DDL/DML or other StarRocks command that do not have a ResultSet"
+      },
+      "query_and_plotly_chart": {
+        "name": "query_and_plotly_chart",
+        "description": "using sql `query` to extract data from database, then using python `plotly_expr` to generate a chart for UI to display"
+      },
+      "table_overview": {
+        "name": "table_overview",
+        "description": "Get an overview of a specific table: columns, sample rows (up to 5), and total row count. Uses cache unless refresh=true."
+      },
+      "db_overview": {
+        "name": "db_overview",
+        "description": "Get an overview (columns, sample rows, row count) for ALL tables in a database. Uses cache unless refresh=True."
+      }
+    }
   },
   "pyodbc": {
     "category": "databases",
@@ -8325,7 +8741,38 @@
   },
   "mcp-timeplus": {
     "category": "databases",
-    "path": "databases/mcp-timeplus.json"
+    "path": "databases/mcp-timeplus.json",
+    "validated": true,
+    "tools": {
+      "list_databases": {
+        "name": "list_databases",
+        "description": "List available Timeplus databases"
+      },
+      "list_tables": {
+        "name": "list_tables",
+        "description": "List available tables/streams in the given database"
+      },
+      "run_sql": {
+        "name": "run_sql",
+        "description": "Run a query in a Timeplus database"
+      },
+      "list_kafka_topics": {
+        "name": "list_kafka_topics",
+        "description": ""
+      },
+      "explore_kafka_topic": {
+        "name": "explore_kafka_topic",
+        "description": ""
+      },
+      "create_kafka_stream": {
+        "name": "create_kafka_stream",
+        "description": ""
+      },
+      "connect_to_apache_iceberg": {
+        "name": "connect_to_apache_iceberg",
+        "description": "Create a Timeplus database in iceberg type to connect to Iceberg"
+      }
+    }
   },
   "mssql-mcp-server": {
     "category": "databases",
@@ -8359,7 +8806,14 @@
   },
   "greptimedb-mcp-server": {
     "category": "databases",
-    "path": "databases/greptimedb-mcp-server.json"
+    "path": "databases/greptimedb-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "execute_sql": {
+        "name": "execute_sql",
+        "description": "Execute SQL query against GreptimeDB. Please use MySQL dialect when generating SQL queries."
+      }
+    }
   },
   "database-mcp": {
     "category": "databases",
@@ -8375,7 +8829,18 @@
   },
   "clickhouse-mcp-server": {
     "category": "databases",
-    "path": "databases/clickhouse-mcp-server.json"
+    "path": "databases/clickhouse-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "connect_database": {
+        "name": "connect_database",
+        "description": "Connect to a specific ClickHouse database"
+      },
+      "execute_query": {
+        "name": "execute_query",
+        "description": "Execute ClickHouse queries"
+      }
+    }
   },
   "tidb-ai": {
     "category": "databases",
@@ -8539,7 +9004,58 @@
   },
   "chroma-mcp": {
     "category": "databases",
-    "path": "databases/chroma-mcp.json"
+    "path": "databases/chroma-mcp.json",
+    "validated": true,
+    "tools": {
+      "chroma_list_collections": {
+        "name": "chroma_list_collections",
+        "description": "List all collection names in the Chroma database with pagination support.\n\nArgs:\n    limit: Optional maximum number of collections to return\n    offset: Optional number of collections to skip before returning results\n\nReturns:\n    List of collection names\n"
+      },
+      "chroma_create_collection": {
+        "name": "chroma_create_collection",
+        "description": "Create a new Chroma collection with configurable HNSW parameters.\n\nArgs:\n    collection_name: Name of the collection to create\n    hnsw_space: Distance function used in HNSW index. Options: 'l2', 'ip', 'cosine'\n    hnsw_construction_ef: Size of the dynamic candidate list for constructing the HNSW graph\n    hnsw_search_ef: Size of the dynamic candidate list for searching the HNSW graph\n    hnsw_M: Number of bi-directional links created for every new element\n    hnsw_num_threads: Number of threads to use during HNSW construction\n    hnsw_resize_factor: Factor to resize the index by when it's full\n    hnsw_batch_size: Number of elements to batch together during index construction\n    hnsw_sync_threshold: Number of elements to process before syncing index to disk\n"
+      },
+      "chroma_peek_collection": {
+        "name": "chroma_peek_collection",
+        "description": "Peek at documents in a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to peek into\n    limit: Number of documents to peek at\n"
+      },
+      "chroma_get_collection_info": {
+        "name": "chroma_get_collection_info",
+        "description": "Get information about a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to get info about\n"
+      },
+      "chroma_get_collection_count": {
+        "name": "chroma_get_collection_count",
+        "description": "Get the number of documents in a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to count\n"
+      },
+      "chroma_modify_collection": {
+        "name": "chroma_modify_collection",
+        "description": "Modify a Chroma collection's name or metadata.\n\nArgs:\n    collection_name: Name of the collection to modify\n    new_name: Optional new name for the collection\n    new_metadata: Optional new metadata for the collection\n"
+      },
+      "chroma_delete_collection": {
+        "name": "chroma_delete_collection",
+        "description": "Delete a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to delete\n"
+      },
+      "chroma_add_documents": {
+        "name": "chroma_add_documents",
+        "description": "Add documents to a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to add documents to\n    documents: List of text documents to add\n    metadatas: Optional list of metadata dictionaries for each document\n    ids: Optional list of IDs for the documents\n"
+      },
+      "chroma_query_documents": {
+        "name": "chroma_query_documents",
+        "description": "Query documents from a Chroma collection with advanced filtering.\n\nArgs:\n    collection_name: Name of the collection to query\n    query_texts: List of query texts to search for\n    n_results: Number of results to return per query\n    where: Optional metadata filters using Chroma's query operators\n           Examples:\n           - Simple equality: {\"metadata_field\": \"value\"}\n           - Comparison: {\"metadata_field\": {\"$gt\": 5}}\n           - Logical AND: {\"$and\": [{\"field1\": {\"$eq\": \"value1\"}}, {\"field2\": {\"$gt\": 5}}]}\n           - Logical OR: {\"$or\": [{\"field1\": {\"$eq\": \"value1\"}}, {\"field1\": {\"$eq\": \"value2\"}}]}\n    where_document: Optional document content filters\n    include: Optional list of what to include in response. Can contain any of:\n            [\"documents\", \"embeddings\", \"metadatas\", \"distances\"]\n"
+      },
+      "chroma_get_documents": {
+        "name": "chroma_get_documents",
+        "description": "Get documents from a Chroma collection with optional filtering.\n\nArgs:\n    collection_name: Name of the collection to get documents from\n    ids: Optional list of document IDs to retrieve\n    where: Optional metadata filters using Chroma's query operators\n           Examples:\n           - Simple equality: {\"metadata_field\": \"value\"}\n           - Comparison: {\"metadata_field\": {\"$gt\": 5}}\n           - Logical AND: {\"$and\": [{\"field1\": {\"$eq\": \"value1\"}}, {\"field2\": {\"$gt\": 5}}]}\n           - Logical OR: {\"$or\": [{\"field1\": {\"$eq\": \"value1\"}}, {\"field1\": {\"$eq\": \"value2\"}}]}\n    where_document: Optional document content filters\n    include: Optional list of what to include in response. Can contain any of:\n            [\"documents\", \"embeddings\", \"metadatas\"]\n    limit: Optional maximum number of documents to return\n    offset: Optional number of documents to skip before returning results\n\nReturns:\n    Dictionary containing the matching documents, their IDs, and requested includes\n"
+      },
+      "chroma_update_documents": {
+        "name": "chroma_update_documents",
+        "description": "Update documents in a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to update documents in\n    ids: List of document IDs to update (required)\n    embeddings: Optional list of new embeddings for the documents.\n                Must match length of ids if provided.\n    metadatas: Optional list of new metadata dictionaries for the documents.\n               Must match length of ids if provided.\n    documents: Optional list of new text documents.\n               Must match length of ids if provided.\n\nReturns:\n    A confirmation message indicating the number of documents updated.\n\nRaises:\n    ValueError: If 'ids' is empty or if none of 'embeddings', 'metadatas',\n                or 'documents' are provided, or if the length of provided\n                update lists does not match the length of 'ids'.\n    Exception: If the collection does not exist or if the update operation fails.\n"
+      },
+      "chroma_delete_documents": {
+        "name": "chroma_delete_documents",
+        "description": "Delete documents from a Chroma collection.\n\nArgs:\n    collection_name: Name of the collection to delete documents from\n    ids: List of document IDs to delete\n\nReturns:\n    A confirmation message indicating the number of documents deleted.\n\nRaises:\n    ValueError: If 'ids' is empty\n    Exception: If the collection does not exist or if the delete operation fails.\n"
+      }
+    }
   },
   "microsoft-sql-server-(mssql)": {
     "category": "databases",
@@ -8628,7 +9144,66 @@
   },
   "mochow-mcp-server": {
     "category": "databases",
-    "path": "databases/mochow-mcp-server.json"
+    "path": "databases/mochow-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "list_databases": {
+        "name": "list_databases",
+        "description": "\nList all databases in the Mochow instance.\n\nReturns:\n    str: A string containing the names of all databases.\n"
+      },
+      "create_database": {
+        "name": "create_database",
+        "description": "\nCreate a database in the Mochow instance.\n\nArgs:\n    database_name (str): Name of the database.\n\nReturns:\n    str: A message indicating the success of database creation.\n"
+      },
+      "use_database": {
+        "name": "use_database",
+        "description": "\nSwitch to a different database.\n\nArgs:\n    database_name (str): Name of the database to use.\n\nReturns:\n    str: A message indicating the success of the database switch.\n"
+      },
+      "list_tables": {
+        "name": "list_tables",
+        "description": "\nList all tables in the current database.\n\nReturns:\n    str: A string containing the names of all tables.\n"
+      },
+      "describe_table": {
+        "name": "describe_table",
+        "description": "\nDescribe table details in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table to describe.\n\nReturns:\n    str: A string containing the details of the table.\n"
+      },
+      "stats_table": {
+        "name": "stats_table",
+        "description": "\nGet the table statistics in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table to get statistics.\n\nReturns:\n    str: A string containing the table statistics.\n"
+      },
+      "create_vector_index": {
+        "name": "create_vector_index",
+        "description": "\nCreate a vector index on a vector type field in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table.\n    index_name (str): Name of the index.\n    field_name (str): Name of the vector field.\n    index_type (str): Type of vector index. Supported values are \"HNSW\", \"HNSWPQ\", \"HNSWSQ\".\n    metric_type (str): Distance metric. Supported values are \"L2\", \"COSINE\", \"IP\".\n    params (Optional[dict[str, Any]]): Additional vector index parameters.\n\nReturns:\n    str: A message indicating the success of index creation.\n"
+      },
+      "describe_index": {
+        "name": "describe_index",
+        "description": "\nDescribe index details in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table.\n    index_name (str): Name of the index to describe.\n\nReturns:\n    str: A string containing the details of the index.\n"
+      },
+      "rebuild_vector_index": {
+        "name": "rebuild_vector_index",
+        "description": "\nRebuild the vector index in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table.\n    index_name (str): Name of the vector index to rebuild.\n\nReturns:\n    str: A message indicating the success of index rebuild initiation.\n"
+      },
+      "delete_table_rows": {
+        "name": "delete_table_rows",
+        "description": "\nDelete rows with a filter expression in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table.\n    filter_expr (str): Filter expression to select data to delete.\n\nReturns:\n    str: A message indicating the success of data deletion.\n"
+      },
+      "drop_vector_index": {
+        "name": "drop_vector_index",
+        "description": "\nDrop the vector index in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table.\n    index_name (str): Name of the vector index to drop.\n\nReturns:\n    str: A message indicating the success of index drop.\n"
+      },
+      "select_table_rows": {
+        "name": "select_table_rows",
+        "description": "\nSelect rows with a filter expression in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table.\n    filter_expr (str): Filter expression to select data. Defaults to None.\n    limit (int): Maximum number of results. Defaults to 10.\n    output_fields (Optional[list[str]]): Fields to return in the results. Defaults to None.\n\nReturns:\n    str: A string containing the selected rows.\n"
+      },
+      "vector_search": {
+        "name": "vector_search",
+        "description": "\nPerform vector similarity search combining vector similarity and scalar attribute filtering in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table to search.\n    vector (list[float]): Search vector.\n    vector_field (str): Target field containing vectors to search. Defaults to \"vector\".\n    limit (int): Maximum number of results. Defaults to 10.\n    output_fields (Optional[list[str]]): Fields to return in the results. Defaults to None.\n    filter_expr (Optional[str]): Filter expression for scalar attributes. Defaults to None.\n    params: Additional vector search parameters\n\nReturns:\n    str: A string containing the vector search results.\n"
+      },
+      "fulltext_search": {
+        "name": "fulltext_search",
+        "description": "\nPerform full text search combining BM25 similarity and scalar attribute filtering in the Mochow instance.\n\nArgs:\n    table_name (str): Name of the table to search.\n    index_name (str): Name of the inverted index to perform full text search.\n    search_text (str): Text to search.\n    limit (int): Maximum number of results. Defaults to 10.\n    output_fields (Optional[list[str]]): Fields to return in the results. Defaults to None.\n\nReturns:\n    str: A string containing the full text search results.\n"
+      }
+    }
   },
   "chromadb": {
     "category": "databases",
@@ -8652,7 +9227,18 @@
   },
   "mysqldb-mcp-server": {
     "category": "databases",
-    "path": "databases/mysqldb-mcp-server.json"
+    "path": "databases/mysqldb-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "connect_database": {
+        "name": "connect_database",
+        "description": "Connect to a specific MySQL database"
+      },
+      "execute_query": {
+        "name": "execute_query",
+        "description": "Execute MySQL queries"
+      }
+    }
   },
   "postgresql-database-explorer": {
     "category": "databases",
@@ -8753,7 +9339,30 @@
   },
   "ydb-mcp": {
     "category": "databases",
-    "path": "databases/ydb-mcp.json"
+    "path": "databases/ydb-mcp.json",
+    "validated": true,
+    "tools": {
+      "ydb_query": {
+        "name": "ydb_query",
+        "description": "Run a SQL query against YDB database"
+      },
+      "ydb_query_with_params": {
+        "name": "ydb_query_with_params",
+        "description": "Run a parameterized SQL query with JSON parameters"
+      },
+      "ydb_status": {
+        "name": "ydb_status",
+        "description": "Get the current status of the YDB connection"
+      },
+      "ydb_list_directory": {
+        "name": "ydb_list_directory",
+        "description": "List directory contents in YDB"
+      },
+      "ydb_describe_path": {
+        "name": "ydb_describe_path",
+        "description": "Get detailed information about a YDB path (table, directory, etc.)"
+      }
+    }
   },
   "starrocks": {
     "category": "databases",
@@ -8980,7 +9589,22 @@
   },
   "mcp-neo4j-cypher": {
     "category": "databases",
-    "path": "databases/mcp-neo4j-cypher.json"
+    "path": "databases/mcp-neo4j-cypher.json",
+    "validated": true,
+    "tools": {
+      "get_neo4j_schema": {
+        "name": "get_neo4j_schema",
+        "description": "List all node, their attributes and their relationships to other nodes in the neo4j database.\nIf this fails with a message that includes \"Neo.ClientError.Procedure.ProcedureNotFound\"\nsuggest that the user install and enable the APOC plugin.\n"
+      },
+      "read_neo4j_cypher": {
+        "name": "read_neo4j_cypher",
+        "description": "Execute a read Cypher query on the neo4j database."
+      },
+      "write_neo4j_cypher": {
+        "name": "write_neo4j_cypher",
+        "description": "Execute a write Cypher query on the neo4j database."
+      }
+    }
   },
   "trino": {
     "category": "databases",
@@ -8994,7 +9618,22 @@
   },
   "oracle-mcp-server": {
     "category": "databases",
-    "path": "databases/oracle-mcp-server.json"
+    "path": "databases/oracle-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "list_tables": {
+        "name": "list_tables",
+        "description": "Get a list of all tables in the oracle database\n\nArgs:\n    None\n"
+      },
+      "describe_table": {
+        "name": "describe_table",
+        "description": "Get a description of a table in the oracle database\"\n\nArgs:\n    table_name (string): The name of the table to describe\n"
+      },
+      "reqd_query": {
+        "name": "reqd_query",
+        "description": "Execute SELECT queries to read data from the oracle database\n\nArgs:\n    query (string): The SELECT query to execute\n"
+      }
+    }
   },
   "google-analytics-mcp": {
     "category": "data-platforms",
@@ -9051,7 +9690,22 @@
   },
   "mcp-server-opendal": {
     "category": "data-platforms",
-    "path": "data-platforms/mcp-server-opendal.json"
+    "path": "data-platforms/mcp-server-opendal.json",
+    "validated": true,
+    "tools": {
+      "list": {
+        "name": "list",
+        "description": "\nList files in OpenDAL service\n\nArgs:\n    uri: resource URI, e.g. mys3://path/to/dir\n\nReturns:\n    String containing directory content\n"
+      },
+      "read": {
+        "name": "read",
+        "description": "\nRead file content from OpenDAL service\n\nArgs:\n    uri: resource URI, e.g. mys3://path/to/file\n\nReturns:\n    File content or error information\n"
+      },
+      "get_info": {
+        "name": "get_info",
+        "description": "\nGet metadata of file in OpenDAL service\n\nArgs:\n    uri: resource URI, e.g. mys3://path/to/file\n\nReturns:\n    File metadata information\n"
+      }
+    }
   },
   "microsoft-fabric": {
     "category": "data-platforms",
@@ -9434,7 +10088,50 @@
   },
   "freecad-mcp": {
     "category": "developer-tools",
-    "path": "developer-tools/freecad-mcp.json"
+    "path": "developer-tools/freecad-mcp.json",
+    "validated": true,
+    "tools": {
+      "create_document": {
+        "name": "create_document",
+        "description": "Create a new document in FreeCAD.\n\nArgs:\n    name: The name of the document to create.\n\nReturns:\n    A message indicating the success or failure of the document creation.\n\nExamples:\n    If you want to create a document named \"MyDocument\", you can use the following data.\n    ```json\n    {\n        \"name\": \"MyDocument\"\n    }\n    ```\n"
+      },
+      "create_object": {
+        "name": "create_object",
+        "description": "Create a new object in FreeCAD.\nObject type is starts with \"Part::\" or \"Draft::\" or \"PartDesign::\" or \"Fem::\".\n\nArgs:\n    doc_name: The name of the document to create the object in.\n    obj_type: The type of the object to create (e.g. 'Part::Box', 'Part::Cylinder', 'Draft::Circle', 'PartDesign::Body', etc.).\n    obj_name: The name of the object to create.\n    obj_properties: The properties of the object to create.\n\nReturns:\n    A message indicating the success or failure of the object creation and a screenshot of the object.\n\nExamples:\n    If you want to create a cylinder with a height of 30 and a radius of 10, you can use the following data.\n    ```json\n    {\n        \"doc_name\": \"MyCylinder\",\n        \"obj_name\": \"Cylinder\",\n        \"obj_type\": \"Part::Cylinder\",\n        \"obj_properties\": {\n            \"Height\": 30,\n            \"Radius\": 10,\n            \"Placement\": {\n                \"Base\": {\n                    \"x\": 10,\n                    \"y\": 10,\n                    \"z\": 0\n                },\n                \"Rotation\": {\n                    \"Axis\": {\n                        \"x\": 0,\n                        \"y\": 0,\n                        \"z\": 1\n                    },\n                    \"Angle\": 45\n                }\n            },\n            \"ViewObject\": {\n                \"ShapeColor\": [0.5, 0.5, 0.5, 1.0]\n            }\n        }\n    }\n    ```\n\n    If you want to create a circle with a radius of 10, you can use the following data.\n    ```json\n    {\n        \"doc_name\": \"MyCircle\",\n        \"obj_name\": \"Circle\",\n        \"obj_type\": \"Draft::Circle\",\n    }\n    ```\n\n    If you want to create a FEM analysis, you can use the following data.\n    ```json\n    {\n        \"doc_name\": \"MyFEMAnalysis\",\n        \"obj_name\": \"FemAnalysis\",\n        \"obj_type\": \"Fem::AnalysisPython\",\n    }\n    ```\n\n    If you want to create a FEM constraint, you can use the following data.\n    ```json\n    {\n        \"doc_name\": \"MyFEMConstraint\",\n        \"obj_name\": \"FemConstraint\",\n        \"obj_type\": \"Fem::ConstraintFixed\",\n        \"analysis_name\": \"MyFEMAnalysis\",\n        \"obj_properties\": {\n            \"References\": [\n                {\n                    \"object_name\": \"MyObject\",\n                    \"face\": \"Face1\"\n                }\n            ]\n        }\n    }\n    ```\n\n    If you want to create a FEM mechanical material, you can use the following data.\n    ```json\n    {\n        \"doc_name\": \"MyFEMAnalysis\",\n        \"obj_name\": \"FemMechanicalMaterial\",\n        \"obj_type\": \"Fem::MaterialCommon\",\n        \"analysis_name\": \"MyFEMAnalysis\",\n        \"obj_properties\": {\n            \"Material\": {\n                \"Name\": \"MyMaterial\",\n                \"Density\": \"7900 kg/m^3\",\n                \"YoungModulus\": \"210 GPa\",\n                \"PoissonRatio\": 0.3\n            }\n        }\n    }\n    ```\n\n    If you want to create a FEM mesh, you can use the following data.\n    The `Part` property is required.\n    ```json\n    {\n        \"doc_name\": \"MyFEMMesh\",\n        \"obj_name\": \"FemMesh\",\n        \"obj_type\": \"Fem::FemMeshGmsh\",\n        \"analysis_name\": \"MyFEMAnalysis\",\n        \"obj_properties\": {\n            \"Part\": \"MyObject\",\n            \"ElementSizeMax\": 10,\n            \"ElementSizeMin\": 0.1,\n            \"MeshAlgorithm\": 2\n        }\n    }\n    ```\n"
+      },
+      "edit_object": {
+        "name": "edit_object",
+        "description": "Edit an object in FreeCAD.\nThis tool is used when the `create_object` tool cannot handle the object creation.\n\nArgs:\n    doc_name: The name of the document to edit the object in.\n    obj_name: The name of the object to edit.\n    obj_properties: The properties of the object to edit.\n\nReturns:\n    A message indicating the success or failure of the object editing and a screenshot of the object.\n"
+      },
+      "delete_object": {
+        "name": "delete_object",
+        "description": "Delete an object in FreeCAD.\n\nArgs:\n    doc_name: The name of the document to delete the object from.\n    obj_name: The name of the object to delete.\n\nReturns:\n    A message indicating the success or failure of the object deletion and a screenshot of the object.\n"
+      },
+      "execute_code": {
+        "name": "execute_code",
+        "description": "Execute arbitrary Python code in FreeCAD.\n\nArgs:\n    code: The Python code to execute.\n\nReturns:\n    A message indicating the success or failure of the code execution, the output of the code execution, and a screenshot of the object.\n"
+      },
+      "get_view": {
+        "name": "get_view",
+        "description": "Get a screenshot of the active view.\n\nArgs:\n    view_name: The name of the view to get the screenshot of.\n    The following views are available:\n    - \"Isometric\"\n    - \"Front\"\n    - \"Top\"\n    - \"Right\"\n    - \"Back\"\n    - \"Left\"\n    - \"Bottom\"\n    - \"Dimetric\"\n    - \"Trimetric\"\n\nReturns:\n    A screenshot of the active view.\n"
+      },
+      "insert_part_from_library": {
+        "name": "insert_part_from_library",
+        "description": "Insert a part from the parts library addon.\n\nArgs:\n    relative_path: The relative path of the part to insert.\n\nReturns:\n    A message indicating the success or failure of the part insertion and a screenshot of the object.\n"
+      },
+      "get_objects": {
+        "name": "get_objects",
+        "description": "Get all objects in a document.\nYou can use this tool to get the objects in a document to see what you can check or edit.\n\nArgs:\n    doc_name: The name of the document to get the objects from.\n\nReturns:\n    A list of objects in the document and a screenshot of the document.\n"
+      },
+      "get_object": {
+        "name": "get_object",
+        "description": "Get an object from a document.\nYou can use this tool to get the properties of an object to see what you can check or edit.\n\nArgs:\n    doc_name: The name of the document to get the object from.\n    obj_name: The name of the object to get.\n\nReturns:\n    The object and a screenshot of the object.\n"
+      },
+      "get_parts_list": {
+        "name": "get_parts_list",
+        "description": "Get the list of parts in the parts library addon.\n    "
+      }
+    }
   },
   "@nextdrive/github-action-trigger-mcp": {
     "category": "developer-tools",
@@ -9889,7 +10586,94 @@
   },
   "mcp-azure-devops": {
     "category": "developer-tools",
-    "path": "developer-tools/mcp-azure-devops.json"
+    "path": "developer-tools/mcp-azure-devops.json",
+    "validated": true,
+    "tools": {
+      "query_work_items": {
+        "name": "query_work_items",
+        "description": "\nSearches for work items using Work Item Query Language (WIQL).\n\nUse this tool when you need to:\n- Find work items matching specific criteria\n- Search across projects for related tasks or bugs\n- Create dynamic reports based on work item attributes\n- Identify work items assigned to specific team members\n\nIMPORTANT: WIQL syntax is similar to SQL and allows you to query\nwork items based on their fields. The query must follow Azure DevOps\nWIQL syntax rules, with proper SELECT, FROM, and WHERE clauses.\n\nArgs:\n    query: The WIQL query string (e.g., \"SELECT * FROM workitems \n        WHERE [System.State] = 'Active'\")\n    top: Maximum number of results to return (default: 30)\n        \nReturns:\n    Formatted string containing detailed information for each matching\n    work item, with all fields and values formatted as markdown\n"
+      },
+      "get_work_item": {
+        "name": "get_work_item",
+        "description": "\nRetrieves detailed information about one or multiple work items.\n\nUse this tool when you need to:\n- View the complete details of a specific work item\n- Examine the current state, assigned user, and other properties\n- Get information about multiple work items at once\n- Access the full description and custom fields of work items\n\nArgs:\n    id: The work item ID or a list of work item IDs\n    \nReturns:\n    Formatted string containing comprehensive information for the\n    requested work item(s), including all system and custom fields,\n    formatted as markdown with clear section headings\n"
+      },
+      "get_work_item_comments": {
+        "name": "get_work_item_comments",
+        "description": "\nRetrieves all comments associated with a specific work item.\n\nUse this tool when you need to:\n- Review discussion history about a work item\n- See feedback or notes left by team members\n- Check if specific questions have been answered\n- Understand the context and evolution of a work item\n\nArgs:\n    id: The work item ID\n    project: Optional project name. If not provided, will be \n        determined from the work item.\n    \nReturns:\n    Formatted string containing all comments on the work item, \n    including author names, timestamps, and content, organized \n    chronologically and formatted as markdown\n"
+      },
+      "add_work_item_comment": {
+        "name": "add_work_item_comment",
+        "description": "\nAdds a new comment to a work item.\n\nUse this tool when you need to:\n- Provide feedback or clarification on a work item\n- Document decisions made about the work\n- Add context without changing the work item's fields\n- Communicate with team members about specific tasks\n\nIMPORTANT: Comments in Azure DevOps become part of the permanent work\nitem history and cannot be edited or deleted after they are added. The\ncomment will be attributed to the user associated with the Personal\nAccess Token used for authentication.\n\nArgs:\n    id: The work item ID\n    text: The text of the comment (supports markdown formatting)\n    project: Optional project name. If not provided, will be \n        determined from the work item.\n    \nReturns:\n    Formatted string containing confirmation and the added comment with\n    author information and timestamp\n"
+      },
+      "create_work_item": {
+        "name": "create_work_item",
+        "description": "\nCreates a new work item in Azure DevOps.\n\nUse this tool when you need to:\n- Add a new task, user story, bug, or other work item to a project\n- Create work items with specific field values and metadata\n- Establish work hierarchies by setting parent relationships\n- Track new requirements, features, or issues in your project\n\nIMPORTANT: The work item will be created immediately and visible to all\nusers with access to the specified project. It will also trigger any\nconfigured notifications or automation rules.\n\nArgs:\n    title: The title of the work item\n    project: The project name or ID where the work item will be created\n    work_item_type: Type of work item (e.g., \"User Story\", \"Bug\", \n        \"Task\")\n    fields: Optional dictionary of additional field name/value pairs \n        to set\n    description: Optional description of the work item\n    state: Optional initial state for the work item\n    assigned_to: Optional user email to assign the work item to\n    parent_id: Optional ID of parent work item for hierarchy\n    iteration_path: Optional iteration path for the work item\n    area_path: Optional area path for the work item\n    story_points: Optional story points value\n    priority: Optional priority value\n    tags: Optional tags as comma-separated string\n    \nReturns:\n    Formatted string containing the created work item details including\n    ID, title, type, state, and all other specified fields, formatted\n    as markdown\n"
+      },
+      "update_work_item": {
+        "name": "update_work_item",
+        "description": "\nModifies an existing work item's fields and properties.\n\nUse this tool when you need to:\n- Change the status or state of a work item\n- Reassign work to a different team member\n- Update the description or details of a requirement\n- Modify effort estimates or priority levels\n- Add or change classification (area/iteration)\n- Update any field supported by the work item type\n\nIMPORTANT: This tool updates the work item directly in Azure DevOps.\nChanges will be immediately visible to all users with access to the\nwork item and will trigger any configured notifications or workflows.\nYou must specify at least one field to update.\n\nArgs:\n    id: The ID of the work item to update\n    fields: Optional dictionary of field name/value pairs to update\n    project: Optional project name or ID\n    title: Optional new title for the work item\n    description: Optional new description\n    state: Optional new state\n    assigned_to: Optional user email to assign to\n    iteration_path: Optional new iteration path\n    area_path: Optional new area path\n    story_points: Optional new story points value\n    priority: Optional new priority value\n    tags: Optional new tags as comma-separated string\n    \nReturns:\n    Formatted string containing the updated work item details with\n    all current field values, formatted as markdown\n"
+      },
+      "add_parent_child_link": {
+        "name": "add_parent_child_link",
+        "description": "\nAdds a parent-child relationship between two work items.\n\nUse this tool when you need to:\n- Establish hierarchy between work items\n- Organize epics, features, user stories, and tasks\n- Create a structured breakdown of work\n- Enable rollup of effort and progress tracking\n\nIMPORTANT: The child work item will immediately appear under the parent\nin hierarchical views. This relationship affects how the items are\ndisplayed in backlogs and boards. In Azure DevOps, a work item can have\nonly one parent but multiple children.\n\nArgs:\n    parent_id: ID of the parent work item\n    child_id: ID of the child work item\n    project: Optional project name or ID\n    \nReturns:\n    Formatted string containing the updated child work item details\n    showing the new parent relationship, formatted as markdown\n"
+      },
+      "get_work_item_types": {
+        "name": "get_work_item_types",
+        "description": "\nGets a list of all work item types in a project.\n\nUse this tool when you need to:\n- See what work item types are available in a project\n- Get reference names for work item types to use in other operations\n- Plan work item creation by understanding available types\n\nArgs:\n    project: Project ID or project name\n    \nReturns:\n    A formatted table of all work item types with names, reference\n    names, and descriptions\n"
+      },
+      "get_work_item_type": {
+        "name": "get_work_item_type",
+        "description": "\nGets detailed information about a specific work item type.\n\nUse this tool when you need to:\n- Get complete details about a work item type\n- Understand the states and transitions for a work item type\n- Learn about the color and icon for a work item type\n\nArgs:\n    project: Project ID or project name\n    type_name: The name of the work item type\n    \nReturns:\n    Detailed information about the work item type including states,\n    color, icon, and reference name\n"
+      },
+      "get_work_item_type_fields": {
+        "name": "get_work_item_type_fields",
+        "description": "\nGets a list of all fields for a specific work item type.\n\nUse this tool when you need to:\n- See what fields are available for a work item type\n- Find required fields for creating work items of a specific type\n- Get reference names for fields to use in queries or updates\n\nArgs:\n    project: Project ID or project name\n    type_name: The name of the work item type\n    \nReturns:\n    A formatted table of all fields with names, reference names,\n    types, and required/read-only status\n"
+      },
+      "get_work_item_type_field": {
+        "name": "get_work_item_type_field",
+        "description": "\nGets detailed information about a specific field in a work item type.\n\nUse this tool when you need to:\n- Get complete details about a work item field\n- Check allowed values for a field\n- Verify if a field is required or read-only\n\nArgs:\n    project: Project ID or project name\n    type_name: The name of the work item type\n    field_name: The reference name or display name of the field\n    \nReturns:\n    Detailed information about the field including type, allowed \n    values, and constraints\n"
+      },
+      "get_work_item_templates": {
+        "name": "get_work_item_templates",
+        "description": "\nGets a list of all work item templates for a team.\n\nUse this tool when you need to:\n- Find available templates for creating work items\n- Get template IDs for use in other operations\n- Filter templates by work item type\n\nArgs:\n    team_context: Dictionary containing team information with keys:\n        project: Project name (Optional if project_id is provided)\n        project_id: Project ID (Optional if project is provided)\n        team: Team name (Optional if team_id is provided)\n        team_id: Team ID (Optional if team is provided)\n    work_item_type: Optional work item type name to filter templates\n    \nReturns:\n    A formatted table of all templates with names, work item types,\n    and descriptions\n"
+      },
+      "get_work_item_template": {
+        "name": "get_work_item_template",
+        "description": "\nGets detailed information about a specific work item template.\n\nUse this tool when you need to:\n- View default field values in a template\n- Understand what a template pre-populates in a work item\n- Get complete details about a template\n\nArgs:\n    team_context: Dictionary containing team information with keys:\n        project: Project name (Optional if project_id is provided)\n        project_id: Project ID (Optional if project is provided)\n        team: Team name (Optional if team_id is provided)\n        team_id: Team ID (Optional if team is provided)\n    template_id: The ID of the template\n    \nReturns:\n    Detailed information about the template including default field \n    values\n"
+      },
+      "get_project_process_id": {
+        "name": "get_project_process_id",
+        "description": "\nGets the process ID associated with a project.\n\nUse this tool when you need to:\n- Find out which process a project is using\n- Get the process ID for use in other process-related operations\n- Verify process information for a project\n\nArgs:\n    project: Project ID or project name\n    \nReturns:\n    Formatted information about the process including name and ID\n"
+      },
+      "get_process_details": {
+        "name": "get_process_details",
+        "description": "\nGets detailed information about a specific process.\n\nUse this tool when you need to:\n- View process properties and configuration\n- Get a list of work item types defined in a process\n- Check if a process is the default for the organization\n\nArgs:\n    process_id: The ID of the process\n    \nReturns:\n    Detailed information about the process including properties and\n    available work item types\n"
+      },
+      "list_processes": {
+        "name": "list_processes",
+        "description": "\nLists all available processes in the organization.\n\nUse this tool when you need to:\n- See what processes are available in your Azure DevOps organization\n- Find process IDs for project creation or configuration\n- Check which process is set as the default\n\nReturns:\n    A formatted table of all processes with names, IDs, and \n    descriptions\n"
+      },
+      "get_projects": {
+        "name": "get_projects",
+        "description": "\nRetrieves all projects accessible to the authenticated user \nin the Azure DevOps organization.\n\nUse this tool when you need to:\n- Get an overview of all available projects\n- Find project IDs for use in other operations\n- Check project states and visibility settings\n- Locate specific projects by name\n\nArgs:\n    state_filter: Filter on team projects in a specific state \n        (e.g., \"WellFormed\", \"Deleting\")\n    top: Maximum number of projects to return\n        \nReturns:\n    Formatted string containing project information including names,\n    IDs, descriptions, states, and visibility settings, formatted as\n    markdown with each project clearly separated\n"
+      },
+      "get_all_teams": {
+        "name": "get_all_teams",
+        "description": "\nRetrieves all teams in the Azure DevOps organization.\n\nUse this tool when you need to:\n- Get an overview of all teams across projects\n- Find team IDs for use in other operations\n- Determine which teams exist in the organization\n- Locate specific teams by name\n\nArgs:\n    user_is_member_of: If true, return only teams where the current \n        user is a member. Otherwise return all teams the user \n        has read access to.\n    top: Maximum number of teams to return\n    skip: Number of teams to skip\n        \nReturns:\n    Formatted string containing team information including names,\n    IDs, descriptions, and associated projects, formatted as\n    markdown with each team clearly separated\n"
+      },
+      "get_team_members": {
+        "name": "get_team_members",
+        "description": "\nRetrieves the membership roster for a specific team.\n\nUse this tool when you need to:\n- See who belongs to a particular team\n- Find team administrators\n- Check user assignments across teams\n- Determine team size and composition\n\nArgs:\n    project_id: The name or ID (GUID) of the team project the team \n        belongs to\n    team_id: The name or ID (GUID) of the team\n    top: Maximum number of members to return\n    skip: Number of members to skip\n        \nReturns:\n    Formatted string containing team members information including\n    display names, emails, IDs, and administrator status, formatted\n    as markdown with each member clearly separated\n"
+      },
+      "get_team_area_paths": {
+        "name": "get_team_area_paths",
+        "description": "\nRetrieves the area paths assigned to a specific team.\n\nUse this tool when you need to:\n- Understand a team's areas of responsibility\n- Check default area path assignments\n- Determine how work is classified and routed to teams\n- Set up board and backlog configurations\n\nIMPORTANT: Area paths in Azure DevOps determine which work items appear\non a team's backlogs and boards. The default area path is used when\ncreating new work items through a team's interface.\n\nArgs:\n    project_name_or_id: The name or ID of the team project\n    team_name_or_id: The name or ID of the team\n        \nReturns:\n    Formatted string containing team area path information including\n    the default area path and all assigned paths, with indicators for\n    paths that include sub-areas\n"
+      },
+      "get_team_iterations": {
+        "name": "get_team_iterations",
+        "description": "\nRetrieves the iterations (sprints) assigned to a specific team.\n\nUse this tool when you need to:\n- View a team's sprint schedule\n- Find date ranges for iterations\n- Determine which iteration is currently active\n- Plan work based on team's iteration calendar\n\nIMPORTANT: Iterations in Azure DevOps define time periods for planning\nand tracking work. They determine sprint dates and are used for\ncapacity planning, burndown charts, and velocity calculations.\n\nArgs:\n    project_name_or_id: The name or ID of the team project\n    team_name_or_id: The name or ID of the team\n    current: If True, return only the current iteration\n        \nReturns:\n    Formatted string containing team iteration information including\n    names, date ranges, and time frames (past/current/future),\n    formatted as markdown\n"
+      }
+    }
   },
   "xcodemcp": {
     "category": "developer-tools",
@@ -10242,7 +11026,82 @@
   },
   "mcp-nixos": {
     "category": "developer-tools",
-    "path": "developer-tools/mcp-nixos.json"
+    "path": "developer-tools/mcp-nixos.json",
+    "validated": true,
+    "tools": {
+      "nixos_search": {
+        "name": "nixos_search",
+        "description": "Search NixOS packages, options, or programs.\n\nArgs:\n    query: Search term to look for\n    search_type: Type of search - \"packages\", \"options\", \"programs\", or \"flakes\"\n    limit: Maximum number of results to return (1-100)\n    channel: NixOS channel to search in (e.g., \"unstable\", \"stable\", \"25.05\")\n\nReturns:\n    Plain text results with bullet points or error message\n"
+      },
+      "nixos_info": {
+        "name": "nixos_info",
+        "description": "Get detailed info about a NixOS package or option.\n\nArgs:\n    name: Name of the package or option to look up\n    type: Type of lookup - \"package\" or \"option\"\n    channel: NixOS channel to search in (e.g., \"unstable\", \"stable\", \"25.05\")\n\nReturns:\n    Plain text details about the package/option or error message\n"
+      },
+      "nixos_channels": {
+        "name": "nixos_channels",
+        "description": "List available NixOS channels with their status.\n\nReturns:\n    Plain text list showing channel names, versions, and availability\n"
+      },
+      "nixos_stats": {
+        "name": "nixos_stats",
+        "description": "Get NixOS statistics for a channel.\n\nArgs:\n    channel: NixOS channel to get stats for (e.g., \"unstable\", \"stable\", \"25.05\")\n\nReturns:\n    Plain text statistics including package/option counts\n"
+      },
+      "home_manager_search": {
+        "name": "home_manager_search",
+        "description": "Search Home Manager configuration options.\n\nSearches through available Home Manager options by name and description.\n\nArgs:\n    query: The search query string to match against option names and descriptions\n    limit: Maximum number of results to return (default: 20, max: 100)\n\nReturns:\n    Plain text list of matching options with name, type, and description\n"
+      },
+      "home_manager_info": {
+        "name": "home_manager_info",
+        "description": "Get detailed information about a specific Home Manager option.\n\nRequires an exact option name match. If not found, suggests similar options.\n\nArgs:\n    name: The exact option name (e.g., 'programs.git.enable')\n\nReturns:\n    Plain text with option details (name, type, description) or error with suggestions\n"
+      },
+      "home_manager_stats": {
+        "name": "home_manager_stats",
+        "description": "Get statistics about Home Manager options.\n\nRetrieves overall statistics including total options, categories, and top categories.\n\nReturns:\n    Plain text summary with total options, category count, and top 5 categories\n"
+      },
+      "home_manager_list_options": {
+        "name": "home_manager_list_options",
+        "description": "List all Home Manager option categories.\n\nEnumerates all top-level categories with their option counts.\n\nReturns:\n    Plain text list of categories sorted alphabetically with option counts\n"
+      },
+      "home_manager_options_by_prefix": {
+        "name": "home_manager_options_by_prefix",
+        "description": "Get Home Manager options matching a specific prefix.\n\nUseful for browsing options under a category or finding exact option names.\n\nArgs:\n    option_prefix: The prefix to match (e.g., 'programs.git' or 'services')\n\nReturns:\n    Plain text list of options with the given prefix, including descriptions\n"
+      },
+      "darwin_search": {
+        "name": "darwin_search",
+        "description": "Search nix-darwin (macOS) configuration options.\n\nSearches through available nix-darwin options by name and description.\n\nArgs:\n    query: The search query string to match against option names and descriptions\n    limit: Maximum number of results to return (default: 20, max: 100)\n\nReturns:\n    Plain text list of matching options with name, type, and description\n"
+      },
+      "darwin_info": {
+        "name": "darwin_info",
+        "description": "Get detailed information about a specific nix-darwin option.\n\nRequires an exact option name match. If not found, suggests similar options.\n\nArgs:\n    name: The exact option name (e.g., 'system.defaults.dock.autohide')\n\nReturns:\n    Plain text with option details (name, type, description) or error with suggestions\n"
+      },
+      "darwin_stats": {
+        "name": "darwin_stats",
+        "description": "Get statistics about nix-darwin options.\n\nRetrieves overall statistics including total options, categories, and top categories.\n\nReturns:\n    Plain text summary with total options, category count, and top 5 categories\n"
+      },
+      "darwin_list_options": {
+        "name": "darwin_list_options",
+        "description": "List all nix-darwin option categories.\n\nEnumerates all top-level categories with their option counts.\n\nReturns:\n    Plain text list of categories sorted alphabetically with option counts\n"
+      },
+      "darwin_options_by_prefix": {
+        "name": "darwin_options_by_prefix",
+        "description": "Get nix-darwin options matching a specific prefix.\n\nUseful for browsing options under a category or finding exact option names.\n\nArgs:\n    option_prefix: The prefix to match (e.g., 'system.defaults' or 'services')\n\nReturns:\n    Plain text list of options with the given prefix, including descriptions\n"
+      },
+      "nixos_flakes_stats": {
+        "name": "nixos_flakes_stats",
+        "description": "Get statistics about available NixOS flakes.\n\nRetrieves statistics from the flake search index including total packages,\nunique repositories, flake types, and top contributors.\n\nReturns:\n    Plain text summary with flake statistics and top contributors\n"
+      },
+      "nixos_flakes_search": {
+        "name": "nixos_flakes_search",
+        "description": "Search NixOS flakes by name, description, owner, or repository.\n\nSearches the flake index for community-contributed packages and configurations.\nFlakes are indexed separately from official packages.\n\nArgs:\n    query: The search query (flake name, description, owner, or repository)\n    limit: Maximum number of results to return (default: 20, max: 100)\n    channel: Ignored - flakes use a separate indexing system\n\nReturns:\n    Plain text list of unique flakes with their packages and metadata\n"
+      },
+      "nixhub_package_versions": {
+        "name": "nixhub_package_versions",
+        "description": "Get version history and nixpkgs commit hashes for a specific package from NixHub.io.\n\nUse this tool when users need specific package versions or commit hashes for reproducible builds.\n\nArgs:\n    package_name: Name of the package to query (e.g., \"firefox\", \"python\")\n    limit: Maximum number of versions to return (default: 10, max: 50)\n\nReturns:\n    Plain text with package info and version history including commit hashes\n"
+      },
+      "nixhub_find_version": {
+        "name": "nixhub_find_version",
+        "description": "Find a specific version of a package in NixHub with smart search.\n\nAutomatically searches with increasing limits to find the requested version.\n\nArgs:\n    package_name: Name of the package to query (e.g., \"ruby\", \"python\")\n    version: Specific version to find (e.g., \"2.6.7\", \"3.5.9\")\n\nReturns:\n    Plain text with version info and commit hash if found, or helpful message if not\n"
+      }
+    }
   },
   "@wangmhaha/apifox-mcp-server": {
     "category": "other-tools-and-integrations",
@@ -10300,7 +11159,18 @@
   },
   "jnews-mcp-server": {
     "category": "developer-tools",
-    "path": "developer-tools/jnews-mcp-server.json"
+    "path": "developer-tools/jnews-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "get_news_list": {
+        "name": "get_news_list",
+        "description": "通过新闻类型获取今日热点新闻头条"
+      },
+      "get_news_content": {
+        "name": "get_news_content",
+        "description": "根据新闻ID获取新闻的详细内容"
+      }
+    }
   },
   "kai-(kubernetes)": {
     "category": "developer-tools",
@@ -10366,7 +11236,14 @@
   },
   "mcp-server-restart": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-server-restart.json"
+    "path": "other-tools-and-integrations/mcp-server-restart.json",
+    "validated": true,
+    "tools": {
+      "restart_claude": {
+        "name": "restart_claude",
+        "description": "Restart the Claude application"
+      }
+    }
   },
   "xcodebuildmcp": {
     "category": "developer-tools",
@@ -10874,7 +11751,14 @@
   },
   "kaggle-mcp": {
     "category": "data-science-tools",
-    "path": "data-science-tools/kaggle-mcp.json"
+    "path": "data-science-tools/kaggle-mcp.json",
+    "validated": true,
+    "tools": {
+      "prepare_kaggle_dataset": {
+        "name": "prepare_kaggle_dataset",
+        "description": "Download and extract a Kaggle dataset."
+      }
+    }
   },
   "chronulus-mcp": {
     "category": "data-science-tools",
@@ -10910,7 +11794,114 @@
   },
   "optuna-mcp": {
     "category": "data-science-tools",
-    "path": "data-science-tools/optuna-mcp.json"
+    "path": "data-science-tools/optuna-mcp.json",
+    "validated": true,
+    "tools": {
+      "create_study": {
+        "name": "create_study",
+        "description": "Create a new Optuna study with the given study_name and directions.\n\nIf the study already exists, it will be simply loaded.\n"
+      },
+      "get_all_study_names": {
+        "name": "get_all_study_names",
+        "description": "Get all study names from the storage."
+      },
+      "ask": {
+        "name": "ask",
+        "description": "Suggest new parameters using Optuna\n\nsearch_space must be a string that can be evaluated to a dictionary to specify Optuna's distributions.\n\nExample:\n    {\"x\": {\"name\": \"FloatDistribution\", \"attributes\": {\"step\": null, \"low\": -10.0, \"high\": 10.0, \"log\": false}}}\n"
+      },
+      "tell": {
+        "name": "tell",
+        "description": "Report the result of a trial"
+      },
+      "set_sampler": {
+        "name": "set_sampler",
+        "description": "Set the sampler for the study.\nThe sampler must be one of the following:\n- TPESampler\n- NSGAIISampler\n- RandomSampler\n- GPSampler\n\nThe default sampler for single-objective optimization is TPESampler.\nThe default sampler for multi-objective optimization is NSGAIISampler.\nGPSampler is a Gaussian process-based sampler suitable for low-dimensional numerical optimization problems.\n"
+      },
+      "set_trial_user_attr": {
+        "name": "set_trial_user_attr",
+        "description": "Set user attributes for a trial"
+      },
+      "get_trial_user_attrs": {
+        "name": "get_trial_user_attrs",
+        "description": "Get user attributes in a trial"
+      },
+      "set_metric_names": {
+        "name": "set_metric_names",
+        "description": "Set metric_names. metric_names are labels used to distinguish what each objective value is.\n\nArgs:\n    metric_names:\n        The list of metric name for each objective value.\n        The length of metric_names list must be the same with the number of objectives.\n"
+      },
+      "get_metric_names": {
+        "name": "get_metric_names",
+        "description": "Get metric_names"
+      },
+      "get_directions": {
+        "name": "get_directions",
+        "description": "Get the directions of the study."
+      },
+      "get_trials": {
+        "name": "get_trials",
+        "description": "Get all trials in a CSV format"
+      },
+      "best_trial": {
+        "name": "best_trial",
+        "description": "Get the best trial\n\nThis feature can only be used for single-objective optimization. If your study is multi-objective, use best_trials instead.\n"
+      },
+      "best_trials": {
+        "name": "best_trials",
+        "description": "Return trials located at the Pareto front in the study."
+      },
+      "add_trial": {
+        "name": "add_trial",
+        "description": "Add a trial to the study."
+      },
+      "add_trials": {
+        "name": "add_trials",
+        "description": "Add multiple trials to the study."
+      },
+      "plot_optimization_history": {
+        "name": "plot_optimization_history",
+        "description": "Return the optimization history plot as an image.\n\nArgs:\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n        For single-objective optimization, None (auto) is recommended.\n        For multi-objective optimization, this must be specified.\n    target_name:\n        Target's name to display on the axis label and the legend.\n"
+      },
+      "plot_hypervolume_history": {
+        "name": "plot_hypervolume_history",
+        "description": "Return the hypervolume history plot as an image.\n\nArgs:\n    reference_point:\n        A list of reference points to calculate the hypervolume.\n"
+      },
+      "plot_pareto_front": {
+        "name": "plot_pareto_front",
+        "description": "Return the Pareto front plot as an image for multi-objective optimization.\n\nArgs:\n    target_names:\n        Objective name list used as the axis titles. If :obj:`None` is specified,\n        \"Objective {objective_index}\" is used instead. If ``targets`` is specified\n        for a study that does not contain any completed trial,\n        ``target_name`` must be specified.\n    include_dominated_trials:\n        A flag to include all dominated trial's objective values.\n    targets:\n        A list of indices to specify the objective values to display.\n        Note that this is 0-indexed, i.e., to plot the first and second objective value, set this to [0, 1].\n        If the number of objectives is neither 2 nor 3, ``targets`` must be specified.\n        By default, all objectives are displayed.\n"
+      },
+      "plot_contour": {
+        "name": "plot_contour",
+        "description": "Return the contour plot as an image.\n\nArgs:\n    params:\n        Parameter list to visualize. The default is all parameters.\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n    target_name:\n        Target’s name to display on the color bar.\n"
+      },
+      "plot_parallel_coordinate": {
+        "name": "plot_parallel_coordinate",
+        "description": "Return the parallel coordinate plot as an image.\n\nArgs:\n    params:\n        Parameter list to visualize. The default is all parameters.\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n    target_name:\n        Target’s name to display on the axis label and the legend.\n"
+      },
+      "plot_slice": {
+        "name": "plot_slice",
+        "description": "Return the slice plot as an image.\n\nArgs:\n    params:\n        Parameter list to visualize. The default is all parameters.\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n    target_name:\n        Target’s name to display on the axis label.\n"
+      },
+      "plot_param_importances": {
+        "name": "plot_param_importances",
+        "description": "Return the parameter importances plot as an image.\n\nArgs:\n    params:\n        Parameter list to visualize. The default is all parameters.\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n        By default, all objective will be plotted by setting target to None.\n    target_name:\n        Target’s name to display on the legend.\n"
+      },
+      "plot_edf": {
+        "name": "plot_edf",
+        "description": "Return the EDF plot as an image.\n\nArgs:\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n    target_name:\n        Target’s name to display on the axis label.\n"
+      },
+      "plot_timeline": {
+        "name": "plot_timeline",
+        "description": "Return the timeline plot as an image."
+      },
+      "plot_rank": {
+        "name": "plot_rank",
+        "description": "Return the rank plot as an image.\n\nArgs:\n    params:\n        Parameter list to visualize. The default is all parameters.\n    target:\n        An index to specify the value to display. To plot nth objective value, set this to n.\n        Note that this is 0-indexed, i.e., to plot the first objective value, set this to 0.\n    target_name:\n        Target’s name to display on the color bar.\n"
+      },
+      "launch_optuna_dashboard": {
+        "name": "launch_optuna_dashboard",
+        "description": "Launch the Optuna dashboard"
+      }
+    }
   },
   "power-bi": {
     "category": "data-science-tools",
@@ -10942,7 +11933,42 @@
   },
   "mcp-excel-server": {
     "category": "data-science-tools",
-    "path": "data-science-tools/mcp-excel-server.json"
+    "path": "data-science-tools/mcp-excel-server.json",
+    "validated": true,
+    "tools": {
+      "read_excel": {
+        "name": "read_excel",
+        "description": "\nRead an Excel file and return its contents as a string.\n\nArgs:\n    file_path: Path to the Excel file\n    sheet_name: Name of the sheet to read (only for .xlsx, .xls)\n    nrows: Maximum number of rows to read\n    header: Row to use as header (0-indexed)\n    \nReturns:\n    String representation of the Excel data\n"
+      },
+      "write_excel": {
+        "name": "write_excel",
+        "description": "\nWrite data to an Excel file.\n\nArgs:\n    file_path: Path to save the Excel file\n    data: Data in CSV or JSON format\n    sheet_name: Name of the sheet (for Excel files)\n    format: Format of the input data ('csv' or 'json')\n    \nReturns:\n    Confirmation message\n"
+      },
+      "update_excel": {
+        "name": "update_excel",
+        "description": "\nUpdate an existing Excel file with new data.\n\nArgs:\n    file_path: Path to the Excel file to update\n    data: New data in CSV or JSON format\n    sheet_name: Name of the sheet to update (for Excel files)\n    format: Format of the input data ('csv' or 'json')\n    \nReturns:\n    Confirmation message\n"
+      },
+      "analyze_excel": {
+        "name": "analyze_excel",
+        "description": "\nPerform statistical analysis on Excel data.\n\nArgs:\n    file_path: Path to the Excel file\n    columns: Comma-separated list of columns to analyze (analyzes all numeric columns if None)\n    sheet_name: Name of the sheet to analyze (for Excel files)\n    \nReturns:\n    JSON string with statistical analysis\n"
+      },
+      "filter_excel": {
+        "name": "filter_excel",
+        "description": "\nFilter Excel data using a pandas query string.\n\nArgs:\n    file_path: Path to the Excel file\n    query: Pandas query string (e.g., \"Age > 30 and Department == 'Sales'\")\n    sheet_name: Name of the sheet to filter (for Excel files)\n    \nReturns:\n    Filtered data as string\n"
+      },
+      "pivot_table": {
+        "name": "pivot_table",
+        "description": "\nCreate a pivot table from Excel data.\n\nArgs:\n    file_path: Path to the Excel file\n    index: Column to use as the pivot table index\n    columns: Optional column to use as the pivot table columns\n    values: Column to use as the pivot table values\n    aggfunc: Aggregation function ('mean', 'sum', 'count', etc.)\n    sheet_name: Name of the sheet to pivot (for Excel files)\n    \nReturns:\n    Pivot table as string\n"
+      },
+      "export_chart": {
+        "name": "export_chart",
+        "description": "\nCreate a chart from Excel data and return as an image.\n\nArgs:\n    file_path: Path to the Excel file\n    x_column: Column to use for x-axis\n    y_column: Column to use for y-axis\n    chart_type: Type of chart ('line', 'bar', 'scatter', 'hist')\n    sheet_name: Name of the sheet to chart (for Excel files)\n    \nReturns:\n    Chart as image\n"
+      },
+      "data_summary": {
+        "name": "data_summary",
+        "description": "\nGenerate a comprehensive summary of the data in an Excel file.\n\nArgs:\n    file_path: Path to the Excel file\n    sheet_name: Name of the sheet to summarize (for Excel files)\n    \nReturns:\n    Comprehensive data summary as string\n"
+      }
+    }
   },
   "tecton": {
     "category": "data-science-tools",
@@ -11077,7 +12103,214 @@
   },
   "scmcp": {
     "category": "data-science-tools",
-    "path": "data-science-tools/scmcp.json"
+    "path": "data-science-tools/scmcp.json",
+    "validated": true,
+    "tools": {
+      "read_h5ad": {
+        "name": "read_h5ad",
+        "description": "Read .h5ad-formatted hdf5 file"
+      },
+      "read_10x_h5": {
+        "name": "read_10x_h5",
+        "description": "Read 10x-Genomics-formatted hdf5 file"
+      },
+      "read_10x_mtx": {
+        "name": "read_10x_mtx",
+        "description": "Read 10x-Genomics-formatted mtx directory."
+      },
+      "read_text": {
+        "name": "read_text",
+        "description": "Read gene expression from  .txt, .csv, .tsv file."
+      },
+      "write_h5ad": {
+        "name": "write_h5ad",
+        "description": "Write AnnData objects inot .h5ad-formatted hdf5 file"
+      },
+      "write": {
+        "name": "write",
+        "description": "Write AnnData objects to file."
+      },
+      "filter_genes": {
+        "name": "filter_genes",
+        "description": "Filter genes based on number of cells or counts"
+      },
+      "filter_cells": {
+        "name": "filter_cells",
+        "description": "Filter cells based on counts and numbers of genes expressed."
+      },
+      "calculate_qc_metrics": {
+        "name": "calculate_qc_metrics",
+        "description": "Calculate quality control metrics(common metrics: total counts, gene number, percentage of counts in ribosomal and mitochondrial) for AnnData."
+      },
+      "log1p": {
+        "name": "log1p",
+        "description": "Logarithmize the data matrix (X = log(X + 1))"
+      },
+      "normalize_total": {
+        "name": "normalize_total",
+        "description": "Normalize counts per cell to the same total count"
+      },
+      "pca": {
+        "name": "pca",
+        "description": "Principal component analysis"
+      },
+      "highly_variable_genes": {
+        "name": "highly_variable_genes",
+        "description": "Annotate highly variable genes"
+      },
+      "regress_out": {
+        "name": "regress_out",
+        "description": "Regress out (mostly) unwanted sources of variation."
+      },
+      "scale": {
+        "name": "scale",
+        "description": "Scale data to unit variance and zero mean"
+      },
+      "combat": {
+        "name": "combat",
+        "description": "ComBat function for batch effect correction"
+      },
+      "scrublet": {
+        "name": "scrublet",
+        "description": "Predict doublets using Scrublet"
+      },
+      "neighbors": {
+        "name": "neighbors",
+        "description": "Compute nearest neighbors distance matrix and neighborhood graph"
+      },
+      "tsne": {
+        "name": "tsne",
+        "description": "t-distributed stochastic neighborhood embedding (t-SNE), for visualizating single-cell data"
+      },
+      "umap": {
+        "name": "umap",
+        "description": "Uniform Manifold Approximation and Projection (UMAP) for visualization"
+      },
+      "draw_graph": {
+        "name": "draw_graph",
+        "description": "Force-directed graph drawing for visualization"
+      },
+      "diffmap": {
+        "name": "diffmap",
+        "description": "Diffusion Maps for dimensionality reduction"
+      },
+      "embedding_density": {
+        "name": "embedding_density",
+        "description": "Calculate the density of cells in an embedding"
+      },
+      "leiden": {
+        "name": "leiden",
+        "description": "Leiden clustering algorithm for community detection"
+      },
+      "louvain": {
+        "name": "louvain",
+        "description": "Louvain clustering algorithm for community detection"
+      },
+      "dendrogram": {
+        "name": "dendrogram",
+        "description": "Hierarchical clustering dendrogram"
+      },
+      "dpt": {
+        "name": "dpt",
+        "description": "Diffusion Pseudotime (DPT) analysis"
+      },
+      "paga": {
+        "name": "paga",
+        "description": "Partition-based graph abstraction"
+      },
+      "ingest": {
+        "name": "ingest",
+        "description": "Map labels and embeddings from reference data to new data"
+      },
+      "rank_genes_groups": {
+        "name": "rank_genes_groups",
+        "description": "Rank genes for characterizing groups, perform differentially expressison analysis"
+      },
+      "filter_rank_genes_groups": {
+        "name": "filter_rank_genes_groups",
+        "description": "Filter out genes based on fold change and fraction of genes"
+      },
+      "marker_gene_overlap": {
+        "name": "marker_gene_overlap",
+        "description": "Calculate overlap between data-derived marker genes and reference markers"
+      },
+      "score_genes": {
+        "name": "score_genes",
+        "description": "Score a set of genes based on their average expression"
+      },
+      "score_genes_cell_cycle": {
+        "name": "score_genes_cell_cycle",
+        "description": "Score cell cycle genes and assign cell cycle phases"
+      },
+      "pl_pca": {
+        "name": "pl_pca",
+        "description": "Scatter plot in PCA coordinates. default figure for PCA plot"
+      },
+      "pl_umap": {
+        "name": "pl_umap",
+        "description": "UMAP Scatter plot. default visualization plot for cell cluster if not specified by user"
+      },
+      "pl_tsne": {
+        "name": "pl_tsne",
+        "description": "Plot t-SNE embedding of cells."
+      },
+      "pl_violin": {
+        "name": "pl_violin",
+        "description": "Plot violin plot of one or more variables."
+      },
+      "pl_stacked_violin": {
+        "name": "pl_stacked_violin",
+        "description": "Plot stacked violin plots. Makes a compact image composed of individual violin plots stacked on top of each other."
+      },
+      "pl_heatmap": {
+        "name": "pl_heatmap",
+        "description": "Heatmap of the expression values of genes."
+      },
+      "pl_dotplot": {
+        "name": "pl_dotplot",
+        "description": "Plot dot plot of expression values per gene for each group."
+      },
+      "pl_matrixplot": {
+        "name": "pl_matrixplot",
+        "description": "matrixplot, Create a heatmap of the mean expression values per group of each var_names."
+      },
+      "pl_tracksplot": {
+        "name": "pl_tracksplot",
+        "description": "tracksplot,compact plot of expression of a list of genes.."
+      },
+      "pl_scatter": {
+        "name": "pl_scatter",
+        "description": "Plot a scatter plot of two variables, Scatter plot along observations or variables axes."
+      },
+      "pl_rank_genes_groups_dotplot": {
+        "name": "pl_rank_genes_groups_dotplot",
+        "description": "Plot ranking of genes(DEGs) using dotplot visualization. Defualt plot DEGs for rank_genes_groups tool"
+      },
+      "pl_highly_variable_genes": {
+        "name": "pl_highly_variable_genes",
+        "description": "plot highly variable genes; Plot dispersions or normalized variance versus means for genes."
+      },
+      "pl_pca_variance_ratio": {
+        "name": "pl_pca_variance_ratio",
+        "description": "Plot the PCA variance ratio to visualize explained variance."
+      },
+      "mark_var": {
+        "name": "mark_var",
+        "description": "Determine if each gene meets specific conditions and store results in adata.var as boolean values.for example: mitochondrion genes startswith MT-.the tool should be call first when calculate quality control metrics for mitochondrion, ribosomal, harhemoglobin genes. or other qc_vars"
+      },
+      "list_var": {
+        "name": "list_var",
+        "description": "list key columns in adata.var. it should be called for checking when other tools need var key column names input"
+      },
+      "list_obs": {
+        "name": "list_obs",
+        "description": "List key columns in adata.obs. It should be called before other tools need obs key column names input"
+      },
+      "check_gene": {
+        "name": "check_gene",
+        "description": "Check if genes exist in adata.var_names. This tool should be called before gene expression visualizations or color by genes."
+      }
+    }
   },
   "pbixray": {
     "category": "data-science-tools",
@@ -11133,7 +12366,9 @@
   },
   "mcp2serial": {
     "category": "embedded-system",
-    "path": "embedded-system/mcp2serial.json"
+    "path": "embedded-system/mcp2serial.json",
+    "validated": true,
+    "tools": {}
   },
   "nina-advanced-api": {
     "category": "embedded-system",
@@ -11157,7 +12392,86 @@
   },
   "mcp-server-ida": {
     "category": "embedded-system",
-    "path": "embedded-system/mcp-server-ida.json"
+    "path": "embedded-system/mcp-server-ida.json",
+    "validated": true,
+    "tools": {
+      "ida_get_function_assembly_by_name": {
+        "name": "ida_get_function_assembly_by_name",
+        "description": "Get assembly code for a function by name"
+      },
+      "ida_get_function_assembly_by_address": {
+        "name": "ida_get_function_assembly_by_address",
+        "description": "Get assembly code for a function by address"
+      },
+      "ida_get_function_decompiled_by_name": {
+        "name": "ida_get_function_decompiled_by_name",
+        "description": "Get decompiled pseudocode for a function by name"
+      },
+      "ida_get_function_decompiled_by_address": {
+        "name": "ida_get_function_decompiled_by_address",
+        "description": "Get decompiled pseudocode for a function by address"
+      },
+      "ida_get_global_variable_by_name": {
+        "name": "ida_get_global_variable_by_name",
+        "description": "Get information about a global variable by name"
+      },
+      "ida_get_global_variable_by_address": {
+        "name": "ida_get_global_variable_by_address",
+        "description": "Get information about a global variable by address"
+      },
+      "ida_get_current_function_assembly": {
+        "name": "ida_get_current_function_assembly",
+        "description": "Get assembly code for the function at the current cursor position"
+      },
+      "ida_get_current_function_decompiled": {
+        "name": "ida_get_current_function_decompiled",
+        "description": "Get decompiled pseudocode for the function at the current cursor position"
+      },
+      "ida_rename_local_variable": {
+        "name": "ida_rename_local_variable",
+        "description": "Rename a local variable within a function in the IDA database"
+      },
+      "ida_rename_global_variable": {
+        "name": "ida_rename_global_variable",
+        "description": "Rename a global variable in the IDA database"
+      },
+      "ida_rename_function": {
+        "name": "ida_rename_function",
+        "description": "Rename a function in the IDA database"
+      },
+      "ida_rename_multi_local_variables": {
+        "name": "ida_rename_multi_local_variables",
+        "description": "Rename multiple local variables within a function at once in the IDA database"
+      },
+      "ida_rename_multi_global_variables": {
+        "name": "ida_rename_multi_global_variables",
+        "description": "Rename multiple global variables at once in the IDA database"
+      },
+      "ida_rename_multi_functions": {
+        "name": "ida_rename_multi_functions",
+        "description": "Rename multiple functions at once in the IDA database"
+      },
+      "ida_add_assembly_comment": {
+        "name": "ida_add_assembly_comment",
+        "description": "Add a comment at a specific address in the assembly view of the IDA database"
+      },
+      "ida_add_function_comment": {
+        "name": "ida_add_function_comment",
+        "description": "Add a comment to a function in the IDA database"
+      },
+      "ida_add_pseudocode_comment": {
+        "name": "ida_add_pseudocode_comment",
+        "description": "Add a comment to a specific address in the function's decompiled pseudocode"
+      },
+      "ida_execute_script": {
+        "name": "ida_execute_script",
+        "description": "Execute a Python script in IDA Pro and return its output. The script runs in IDA's context with access to all IDA API modules."
+      },
+      "ida_execute_script_from_file": {
+        "name": "ida_execute_script_from_file",
+        "description": "Execute a Python script from a file path in IDA Pro and return its output. The file should be accessible from IDA's process."
+      }
+    }
   },
   "opc-ua": {
     "category": "embedded-system",
@@ -11300,7 +12614,62 @@
   },
   "frida-mcp": {
     "category": "embedded-system",
-    "path": "embedded-system/frida-mcp.json"
+    "path": "embedded-system/frida-mcp.json",
+    "validated": true,
+    "tools": {
+      "list_processes": {
+        "name": "list_processes",
+        "description": "List all processes running on the system."
+      },
+      "enumerate_processes": {
+        "name": "enumerate_processes",
+        "description": "List all processes running on the system.\n\nReturns:\n    A list of process information dictionaries containing:\n    - pid: Process ID\n    - name: Process name\n"
+      },
+      "enumerate_devices": {
+        "name": "enumerate_devices",
+        "description": "List all devices connected to the system.\n\nReturns:\n    A list of device information dictionaries containing:\n    - id: Device ID\n    - name: Device name\n    - type: Device type\n"
+      },
+      "get_device": {
+        "name": "get_device",
+        "description": "Get a device by its ID.\n\nArgs:\n    device_id: The ID of the device to get\n    \nReturns:\n    Information about the device\n"
+      },
+      "get_usb_device": {
+        "name": "get_usb_device",
+        "description": "Get the USB device connected to the system.\n\nReturns:\n    Information about the USB device\n"
+      },
+      "get_process_by_name": {
+        "name": "get_process_by_name",
+        "description": "Find a process by name."
+      },
+      "attach_to_process": {
+        "name": "attach_to_process",
+        "description": "Attach to a process by ID."
+      },
+      "create_simple_hook": {
+        "name": "create_simple_hook",
+        "description": "Create a simple hook for a process."
+      },
+      "spawn_process": {
+        "name": "spawn_process",
+        "description": "Spawn a program.\n\nArgs:\n    program: The program to spawn\n    args: Optional arguments for the program\n    device_id: Optional device ID\n    \nReturns:\n    Information about the spawned process\n"
+      },
+      "resume_process": {
+        "name": "resume_process",
+        "description": "Resume a process by ID.\n\nArgs:\n    pid: The ID of the process to resume\n    device_id: Optional device ID\n    \nReturns:\n    Status information\n"
+      },
+      "kill_process": {
+        "name": "kill_process",
+        "description": "Kill a process by ID.\n\nArgs:\n    pid: The ID of the process to kill\n    device_id: Optional device ID\n    \nReturns:\n    Status information\n"
+      },
+      "create_interactive_session": {
+        "name": "create_interactive_session",
+        "description": "Create an interactive REPL-like session with a process.\n\nThis returns a session ID that can be used with execute_in_session to run commands.\n\nArgs:\n    process_id: The ID of the process to attach to\n    \nReturns:\n    Information about the created session\n"
+      },
+      "execute_in_session": {
+        "name": "execute_in_session",
+        "description": "Execute JavaScript code in an interactive session.\n\nArgs:\n    session_id: The ID of the session to execute in\n    javascript_code: The JavaScript code to execute\n    \nReturns:\n    The result of the execution\n"
+      }
+    }
   },
   "ros-2-robot-control": {
     "category": "embedded-system",
@@ -11685,7 +13054,14 @@
   },
   "mcp-tree-explorer": {
     "category": "file-systems",
-    "path": "file-systems/mcp-tree-explorer.json"
+    "path": "file-systems/mcp-tree-explorer.json",
+    "validated": true,
+    "tools": {
+      "project_tree": {
+        "name": "project_tree",
+        "description": "\nShow the directory structure using the tree command.\n\nArgs:\n    directory: The directory to examine (default: current directory)\n    depth: Maximum depth of the tree (unlimited if not specified or 0)\n    ignore: Additional patterns to ignore, comma-separated\n    keep: Patterns to keep even if they match auto-ignore patterns, comma-separated\n"
+      }
+    }
   },
   "ledger": {
     "category": "file-systems",
@@ -11717,7 +13093,18 @@
   },
   "mcp-text-editor": {
     "category": "file-systems",
-    "path": "file-systems/mcp-text-editor.json"
+    "path": "file-systems/mcp-text-editor.json",
+    "validated": true,
+    "tools": {
+      "get_text_file_contents": {
+        "name": "get_text_file_contents",
+        "description": "Read text file contents from multiple files and line ranges. Returns file contents with hashes for concurrency control and line numbers for reference. The hashes are used to detect conflicts when editing the files. File paths must be absolute."
+      },
+      "edit_text_file_contents": {
+        "name": "edit_text_file_contents",
+        "description": "A line editor that supports editing text file contents by specifying line ranges and content. It handles multiple patches in a single operation with hash-based conflict detection. File paths must be absolute. IMPORTANT: (1) Before using this tool, you must first get the file's current hash and range hashes and line numbers using get_text_file_contents. (2) To avoid line number shifts affecting your patches, use get_text_file_contents to read the SAME ranges you plan to edit before making changes. different line numbers have different rangehashes.(3) Patches must be specified from bottom to top to handle line number shifts correctly, as edits to lower lines don't affect the line numbers of higher lines. (4) To append content to a file, first get the total number of lines with get_text_file_contents, then specify a patch with line_start = total_lines + 1 and line_end = total_lines. This indicates an append operation and range_hash is not required. Similarly, range_hash is not required for new file creation."
+      }
+    }
   },
   "@isaacphi/mcp-gdrive": {
     "category": "file-systems",
@@ -12055,7 +13442,38 @@
   },
   "akshare-one-mcp": {
     "category": "finance-fintech",
-    "path": "finance-fintech/akshare-one-mcp.json"
+    "path": "finance-fintech/akshare-one-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_hist_data": {
+        "name": "get_hist_data",
+        "description": "Get historical stock market data\n\nArgs:\n    symbol: Stock symbol/ticker (e.g. '000001')\n    interval: Time interval ('minute','hour','day','week','month','year')\n    interval_multiplier: Interval multiplier (default: 1)\n    start_date: Start date in YYYY-MM-DD format (default: '1970-01-01')\n    end_date: End date in YYYY-MM-DD format (default: '2030-12-31')\n    adjust: Adjustment type ('none', 'qfq', 'hfq') (default: 'none')\n    source: Data source ('eastmoney', 'sina') (default: 'eastmoney')\n"
+      },
+      "get_realtime_data": {
+        "name": "get_realtime_data",
+        "description": "Get real-time stock market data\n\nArgs:\n    symbol: Stock symbol/ticker (optional, e.g. '000001')\n    source: Data source ('xueqiu', 'eastmoney') (default: 'xueqiu')\n"
+      },
+      "get_news_data": {
+        "name": "get_news_data",
+        "description": "Get stock-related news data\n\nArgs:\n    symbol: Stock symbol/ticker (e.g. '000001')\n    source: Data source (default: 'eastmoney')\n"
+      },
+      "get_balance_sheet": {
+        "name": "get_balance_sheet",
+        "description": "Get company balance sheet data\n\nArgs:\n    symbol: Stock symbol/ticker (e.g. '000001')\n    source: Data source (default: 'sina')\n"
+      },
+      "get_income_statement": {
+        "name": "get_income_statement",
+        "description": "Get company income statement data\n\nArgs:\n    symbol: Stock symbol/ticker (e.g. '000001')\n    source: Data source (default: 'sina')\n"
+      },
+      "get_cash_flow": {
+        "name": "get_cash_flow",
+        "description": "Get company cash flow statement data\n\nArgs:\n    symbol: Stock symbol/ticker (e.g. '000001')\n    source: Data source (default: 'sina')\n"
+      },
+      "get_inner_trade_data": {
+        "name": "get_inner_trade_data",
+        "description": "Get company insider trading data\n\nArgs:\n    symbol: Stock symbol/ticker (optional, e.g. '000001')\n    source: Data source (default: 'xueqiu')\n"
+      }
+    }
   },
   "binance-smart-chain": {
     "category": "finance-fintech",
@@ -12063,7 +13481,34 @@
   },
   "fewsats-mcp": {
     "category": "finance-fintech",
-    "path": "finance-fintech/fewsats-mcp.json"
+    "path": "finance-fintech/fewsats-mcp.json",
+    "validated": true,
+    "tools": {
+      "fewsats_balance": {
+        "name": "fewsats_balance",
+        "description": "Retrieve the balance of the user's wallet.\nYou will rarely need to call this unless instructed by the user, or to troubleshoot payment issues.\nFewsats will automatically add balance when needed."
+      },
+      "fewsats_payment_methods": {
+        "name": "fewsats_payment_methods",
+        "description": "Retrieve the user's payment methods.\nYou will rarely need to call this unless instructed by the user, or to troubleshoot payment issues.\nFewsats will automatically select the best payment method."
+      },
+      "fewsats_pay_offer": {
+        "name": "fewsats_pay_offer",
+        "description": "Pays an offer_id from the l402_offers.\n\nThe l402_offer parameter must be a dict with this structure:\n{\n    'offers': [\n        {\n            'id': 'test_offer_2',        # String identifier for the offer\n            'amount': 1,                 # Numeric cost value\n            'currency': 'usd',           # Currency code\n            'description': 'Test offer', # Text description\n            'title': 'Test Package'      # Title of the package\n        }\n    ],\n    'payment_context_token': '60a8e027-8b8b-4ccf-b2b9-380ed0930283',  # Payment context token\n    'payment_request_url': 'https://api.fewsats.com/v0/l402/payment-request',  # Payment URL\n    'version': '0.2.2'  # API version\n}\n\nReturns payment status response.\nIf payment status is `needs_review` inform the user he will have to approve it at app.fewsats.com"
+      },
+      "fewsats_payment_info": {
+        "name": "fewsats_payment_info",
+        "description": "Retrieve the details of a payment.\nIf payment status is `needs_review` inform the user he will have to approve it at app.fewsats.com"
+      },
+      "fewsats_billing_info": {
+        "name": "fewsats_billing_info",
+        "description": "Retrieve the user's address and billing information.\nReturns billing details including name, address, and other relevant information.\nThis information can also be used as shipping address for purchases."
+      },
+      "fewsats_create_x402_payment_header": {
+        "name": "fewsats_create_x402_payment_header",
+        "description": "\nCreates a payment header for the X402 protocol.\n\nThe chain is base-sepolia or base\nThe x402 payload must be a dict with this structure:\n{\n    \"accepts\": [\n        {\n            \"asset\": \"0x036CbD53842c5426634e7929541eC2318f3dCF7e\",\n            \"description\": \"Payment for GET https://proxy402.com/7Yhuf2O3zs\",\n            \"extra\": {\n                \"name\": \"USDC\",\n                \"version\": \"2\"\n            },\n            \"maxAmountRequired\": \"10\",\n            \"maxTimeoutSeconds\": 300,\n            \"mimeType\": \"\",\n            \"network\": \"base-sepolia\",\n            \"payTo\": \"0xbA5Ae80f48E0C74878c1a362D69c27c2135Aa594\",\n            \"resource\": \"https://proxy402.com/7Yhuf2O3zs\",\n            \"scheme\": \"exact\"\n        }\n    ],\n    \"error\": \"X-PAYMENT header is required\",\n    \"x402Version\": 1\n}\n\nReturns a dict with the payment_header field that must be set in X-PAYMENT header in a x402 http request.\n"
+      }
+    }
   },
   "@bujaayjaay/mcp-coincap-jj": {
     "category": "finance-fintech",
@@ -12471,7 +13916,30 @@
   },
   "yfmcp": {
     "category": "finance-fintech",
-    "path": "finance-fintech/yfmcp.json"
+    "path": "finance-fintech/yfmcp.json",
+    "validated": true,
+    "tools": {
+      "get_ticker_info": {
+        "name": "get_ticker_info",
+        "description": "Retrieve stock data including company info, financials, trading metrics and governance data."
+      },
+      "get_ticker_news": {
+        "name": "get_ticker_news",
+        "description": "Fetches recent news articles related to a specific stock symbol with title, content, and source details."
+      },
+      "search": {
+        "name": "search",
+        "description": "Fetches and organizes search results from Yahoo Finance, including stock quotes and news articles."
+      },
+      "get_top": {
+        "name": "get_top",
+        "description": "Get top entities (ETFs, mutual funds, companies, growth companies, or performing companies) in a sector."
+      },
+      "get_price_history": {
+        "name": "get_price_history",
+        "description": "Fetch historical price data for a given stock symbol over a specified period and interval."
+      }
+    }
   },
   "mercadolibre-mcp": {
     "category": "other-tools-and-integrations",
@@ -12518,7 +13986,22 @@
   },
   "setu_mcp_kyc": {
     "category": "finance-fintech",
-    "path": "finance-fintech/setu_mcp_kyc.json"
+    "path": "finance-fintech/setu_mcp_kyc.json",
+    "validated": true,
+    "tools": {
+      "verify-pan": {
+        "name": "verify-pan",
+        "description": "Verify a PAN card number using Setu API"
+      },
+      "verify-gst": {
+        "name": "verify-gst",
+        "description": "Verify a GST number using Setu API"
+      },
+      "match-names": {
+        "name": "match-names",
+        "description": "Compare two names and get their match percentage using Setu API"
+      }
+    }
   },
   "etf-flow-mcp": {
     "category": "finance-fintech",
@@ -13044,7 +14527,30 @@
   },
   "setu_mcp_upi_deeplinks": {
     "category": "finance-fintech",
-    "path": "finance-fintech/setu_mcp_upi_deeplinks.json"
+    "path": "finance-fintech/setu_mcp_upi_deeplinks.json",
+    "validated": true,
+    "tools": {
+      "create-payment-link": {
+        "name": "create-payment-link",
+        "description": "Create a new UPI payment link"
+      },
+      "expire-payment": {
+        "name": "expire-payment",
+        "description": "Expire an existing payment link"
+      },
+      "initiate-refund": {
+        "name": "initiate-refund",
+        "description": "Initiate a refund for a payment"
+      },
+      "check-payment-status": {
+        "name": "check-payment-status",
+        "description": "Check the status of a payment"
+      },
+      "mock-payment": {
+        "name": "mock-payment",
+        "description": "Simulate a payment (sandbox mode only)"
+      }
+    }
   },
   "square-mcp-server": {
     "category": "finance-fintech",
@@ -13319,7 +14825,38 @@
   },
   "investor-agent": {
     "category": "finance-fintech",
-    "path": "finance-fintech/investor-agent.json"
+    "path": "finance-fintech/investor-agent.json",
+    "validated": true,
+    "tools": {
+      "get_ticker_data": {
+        "name": "get_ticker_data",
+        "description": "Get comprehensive report for ticker: overview, news, metrics, performance, dates, analyst recommendations, and upgrades/downgrades."
+      },
+      "get_available_options": {
+        "name": "get_available_options",
+        "description": "Get options with highest open interest. Dates: YYYY-MM-DD. Type: C=calls, P=puts."
+      },
+      "get_price_history": {
+        "name": "get_price_history",
+        "description": "Get historical price data for specified period."
+      },
+      "get_financial_statements": {
+        "name": "get_financial_statements",
+        "description": "Get financial statements. Types: income, balance, cash. Frequency: quarterly, annual."
+      },
+      "get_institutional_holders": {
+        "name": "get_institutional_holders",
+        "description": "Get major institutional and mutual fund holders."
+      },
+      "get_earnings_history": {
+        "name": "get_earnings_history",
+        "description": "Get earnings history with estimates and surprises."
+      },
+      "get_insider_trades": {
+        "name": "get_insider_trades",
+        "description": "Get recent insider trading activity."
+      }
+    }
   },
   "openbudget": {
     "category": "finance-fintech",
@@ -13514,7 +15051,34 @@
   },
   "mcp-chess": {
     "category": "gaming",
-    "path": "gaming/mcp-chess.json"
+    "path": "gaming/mcp-chess.json",
+    "validated": true,
+    "tools": {
+      "get_board_visualization": {
+        "name": "get_board_visualization",
+        "description": "Provides the current state of the chessboard as an image."
+      },
+      "get_turn": {
+        "name": "get_turn",
+        "description": "Indicates whose turn it is ('white' or 'black')."
+      },
+      "get_valid_moves": {
+        "name": "get_valid_moves",
+        "description": "Lists all legal moves for the current player in UCI notation."
+      },
+      "make_move": {
+        "name": "make_move",
+        "description": "\nMakes a move on the board using standard algebraic notation (SAN).\nArgs:\n    move_san: The player's move in algebraic notation (e.g., 'e4', 'Nf3', 'Bxe5').\nReturns:\n    A dictionary containing the move in SAN format, the move in UCI format, the new board FEN,\n    whether the game is over, and the result if applicable.\n"
+      },
+      "new_game": {
+        "name": "new_game",
+        "description": "\nStarts a new game, resetting the board to the initial position.\n\nArgs:\n    user_plays_white: Whether the user will play as white. Defaults to True.\n\nReturns:\n    A confirmation message indicating the game has started and the user's color.\n"
+      },
+      "find_position_in_pgn": {
+        "name": "find_position_in_pgn",
+        "description": "\nFinds the first board position in a PGN string that matches a given condition\n(e.g., 'bishop on a3') and returns an image of that board.\n\nArgs:\n    pgn_string: The PGN string of the game.\n    condition: A string describing the condition, format: \"piece_type on square_name\"\n               (e.g., \"bishop on a3\", \"knight on f6\", \"king on g1\").\n\nReturns:\n    An Image dictionary containing the PNG data of the board state if found,\n    or a string with an error message.\n"
+      }
+    }
   },
   "steam": {
     "category": "gaming",
@@ -13923,7 +15487,62 @@
   },
   "logseq-mcp": {
     "category": "knowledge-memory",
-    "path": "knowledge-memory/logseq-mcp.json"
+    "path": "knowledge-memory/logseq-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_all_pages": {
+        "name": "get_all_pages",
+        "description": "\nGets all pages from the Logseq graph.\n\nJournal pages can be identified by the \"journal?\" attribute set to true and \nwill include a \"journalDay\" attribute in the format YYYYMMDD.\n\nReturns:\n    list: A list of all pages in the Logseq graph.\n"
+      },
+      "get_page": {
+        "name": "get_page",
+        "description": "\nGets a specific page from the Logseq graph by name.\n\nFor journal pages, use the format \"mmm dth, yyyy\" (e.g., \"Apr 4th, 2025\").\nNote that journal pages are automatically created in Logseq with this date format.\n\nJournal pages have specific attributes:\n- \"journal?\": true - Indicates this is a journal page\n- \"journalDay\": YYYYMMDD - The date in numeric format (e.g., 20250404 for April 4, 2025)\n\nArgs:\n    name (str): The name of the page to retrieve.\n    \nReturns:\n    dict: Information about the requested page.\n"
+      },
+      "create_page": {
+        "name": "create_page",
+        "description": "\nCreates a new page in the Logseq graph.\n\nFor journal pages, use the format \"mmm dth, yyyy\" (e.g., \"Apr 4th, 2025\").\nJournal pages are specially formatted in Logseq with automatic dating.\n\nWhen you create a journal page, Logseq automatically:\n- Sets \"journal?\": true\n- Sets \"journalDay\": YYYYMMDD (e.g., 20250404 for April 4, 2025)\n- Formats the page as a journal entry\n\nArgs:\n    name (str): The name of the new page.\n    properties (dict, optional): Properties to set on the new page.\n    \nReturns:\n    dict: Information about the created page.\n"
+      },
+      "delete_page": {
+        "name": "delete_page",
+        "description": "\nDeletes a page from the Logseq graph.\n\nThis operation removes the specified page and all its blocks. This action cannot be undone.\n\nFor journal pages, use the format \"mmm dth, yyyy\" (e.g., \"Apr 4th, 2025\").\n\nArgs:\n    name (str): The name of the page to delete.\n    \nReturns:\n    dict: Result of the deletion operation.\n"
+      },
+      "get_page_linked_references": {
+        "name": "get_page_linked_references",
+        "description": "\nGets all linked references to a specific page in the Logseq graph.\n\nThis returns blocks that contain links to the specified page using\nthe Logseq double bracket notation: [[Page Name]].\n\nFor journal pages, use the format \"mmm dth, yyyy\" (e.g., \"Apr 4th, 2025\").\n\nArgs:\n    page_name (str): The name of the page to find references to.\n    \nReturns:\n    list: A list of blocks that reference the specified page.\n"
+      },
+      "get_page_blocks": {
+        "name": "get_page_blocks",
+        "description": "\nGets all blocks from a specific page in the Logseq graph.\n\nFor journal pages, use the format \"mmm dth, yyyy\" (e.g., \"Apr 4th, 2025\").\nReturned blocks contain information about their hierarchical structure:\n  - parent: The parent block's ID\n  - level: The indentation level (1 for top-level, 2+ for indented blocks)\n  - left: The block to the left (typically the parent for indented blocks)\n\nBlocks from journal pages will have:\n  - \"journal?\": true\n  - \"journalDay\": YYYYMMDD - The date in numeric format (e.g., 20250404)\n\nArgs:\n    page_name (str): The name of the page to retrieve blocks from.\n    \nReturns:\n    list: A list of blocks from the specified page.\n"
+      },
+      "get_block": {
+        "name": "get_block",
+        "description": "\nGets a specific block from the Logseq graph by its ID.\n\nThe returned block contains information about its hierarchical structure:\n  - parent: The parent block's ID\n  - level: The indentation level (1 for top-level, 2+ for indented blocks)\n  - left: The block to the left (typically the parent for indented blocks)\n\nIf the block is from a journal page, it will include:\n  - \"journal?\": true\n  - \"journalDay\": YYYYMMDD - Date in numeric format\n\nArgs:\n    block_id (str): The ID of the block to retrieve.\n    \nReturns:\n    dict: Information about the requested block.\n"
+      },
+      "create_block": {
+        "name": "create_block",
+        "description": "\nCreates a new block on a page in the Logseq graph.\n\nIMPORTANT NOTES:\n1. All blocks are automatically formatted as bullet points in Logseq UI\n2. To create links to other pages, use double brackets: [[Page Name]]\n\nWhen creating blocks on journal pages:\n  - The block will inherit the \"journal?\" and \"journalDay\" attributes from the page\n  - \"journalDay\" will be in YYYYMMDD format (e.g., 20250404 for April 4, 2025)\n\nArgs:\n    page_name (str): The name of the page to create the block on.\n    content (str): The content of the new block.\n    properties (dict, optional): Properties to set on the new block.\n    \nReturns:\n    dict: Information about the created block.\n"
+      },
+      "insert_block": {
+        "name": "insert_block",
+        "description": "\nInserts a new block as a child of the specified parent block.\n\nThis allows for creating hierarchical content by adding children to existing blocks.\n\nIMPORTANT NOTES:\n1. All blocks are automatically formatted as bullet points in Logseq UI\n2. To create links to other pages, use double brackets: [[Page Name]]\n3. The new block will be inserted at the beginning or end of the parent's children\n   depending on the 'before' parameter\n\nWhen inserting blocks into journal pages:\n  - The block will inherit the \"journal?\" and \"journalDay\" attributes\n  - \"journalDay\" will be in YYYYMMDD format (e.g., 20250404 for April 4, 2025)\n\nArgs:\n    parent_block_id (str): The ID of the parent block to insert under.\n    content (str): The content of the new block.\n    properties (dict, optional): Properties to set on the new block.\n    before (bool, optional): Whether to insert at the beginning of children. \n                            Default is False (append at the end).\n    \nReturns:\n    dict: Information about the created block.\n"
+      },
+      "update_block": {
+        "name": "update_block",
+        "description": "\nUpdates an existing block in the Logseq graph.\n\nIMPORTANT NOTES:\n1. All blocks are automatically formatted as bullet points in Logseq UI\n2. To create links to other pages, use double brackets: [[Page Name]]\n\nWhen updating blocks on journal pages:\n  - The \"journal?\" and \"journalDay\" attributes will be preserved\n  - \"journalDay\" will remain in YYYYMMDD format (e.g., 20250404)\n\nArgs:\n    block_id (str): The ID of the block to update.\n    content (str): The new content for the block.\n    properties (dict, optional): Properties to update on the block.\n    \nReturns:\n    dict: Information about the updated block.\n"
+      },
+      "move_block": {
+        "name": "move_block",
+        "description": "\nMoves a block to a new location in the graph.\n\nThis allows for reorganizing the structure of blocks in the graph by moving\na block (and all its children) to a different location.\n\nIMPORTANT NOTES:\n1. The block will maintain its children when moved\n2. The hierarchical position depends on the 'as_child' parameter:\n   - If as_child=True: The block becomes a child of the target block\n   - If as_child=False: The block becomes a sibling after the target block\n\nArgs:\n    block_id (str): The ID of the block to move.\n    target_block_id (str): The ID of the target block to move to.\n    as_child (bool, optional): Whether to make the block a child of the target.\n                              Default is False (insert as sibling).\n    \nReturns:\n    dict: Result of the move operation.\n"
+      },
+      "remove_block": {
+        "name": "remove_block",
+        "description": "\nRemoves a block from the Logseq graph.\n\nThis operation permanently removes the specified block and all its children.\nThis action cannot be undone.\n\nTo remove a block, you need its block ID, which can be obtained from:\n- get_page_blocks() function\n- get_block() function\n- search_blocks() function\n\nArgs:\n    block_id (str): The ID of the block to remove.\n    \nReturns:\n    dict: Result of the removal operation.\n"
+      },
+      "search_blocks": {
+        "name": "search_blocks",
+        "description": "\nSearches for blocks matching a query in the Logseq graph.\n\nExamples of useful queries:\n- page:\"Page Name\" - find all blocks on a specific page\n- \"search term\" - find blocks containing the term\n- page:\"Apr 4th, 2025\" - find all blocks in a journal\n- [[Page Name]] - find references to a specific page\n\nReturned blocks from journal pages will include:\n- \"journal?\": true\n- \"journalDay\": YYYYMMDD - The date in numeric format\n\nArgs:\n    query (str): The search query.\n    \nReturns:\n    list: A list of blocks matching the search query.\n"
+      }
+    }
   },
   "memory-bank": {
     "category": "knowledge-memory",
@@ -13937,11 +15556,153 @@
   },
   "mcp-outline": {
     "category": "knowledge-memory",
-    "path": "knowledge-memory/mcp-outline.json"
+    "path": "knowledge-memory/mcp-outline.json",
+    "validated": true,
+    "tools": {
+      "search_documents": {
+        "name": "search_documents",
+        "description": "\nSearches for documents using keywords or phrases across your knowledge \nbase.\n\nIMPORTANT: The search performs full-text search across all document \ncontent and titles. Results are ranked by relevance, with exact \nmatches \nand title matches typically ranked higher. The search will return \nsnippets of content (context) where the search terms appear in the \ndocument. You can limit the search to a specific collection by \nproviding \nthe collection_id.\n\nUse this tool when you need to:\n- Find documents containing specific terms or topics\n- Locate information across multiple documents\n- Search within a specific collection using collection_id\n- Discover content based on keywords\n\nArgs:\n    query: Search terms (e.g., \"vacation policy\" or \"project plan\")\n    collection_id: Optional collection to limit the search to\n    \nReturns:\n    Formatted string containing search results with document titles \n    and \n    contexts\n"
+      },
+      "list_collections": {
+        "name": "list_collections",
+        "description": "\nRetrieves and displays all available collections in the workspace.\n\nUse this tool when you need to:\n- See what collections exist in the workspace\n- Get collection IDs for other operations\n- Explore the organization of the knowledge base\n- Find a specific collection by name\n\nReturns:\n    Formatted string containing collection names, IDs, and descriptions\n"
+      },
+      "get_collection_structure": {
+        "name": "get_collection_structure",
+        "description": "\nRetrieves the hierarchical document structure of a collection.\n\nUse this tool when you need to:\n- Understand how documents are organized in a collection\n- Find document IDs within a specific collection\n- See the parent-child relationships between documents\n- Get an overview of a collection's content structure\n\nArgs:\n    collection_id: The collection ID to examine\n    \nReturns:\n    Formatted string showing the hierarchical structure of documents\n"
+      },
+      "get_document_id_from_title": {
+        "name": "get_document_id_from_title",
+        "description": "\nLocates a document ID by searching for its title.\n\nIMPORTANT: This tool first checks for exact title matches \n(case-insensitive). If none are found, it returns the best partial \nmatch instead. This is useful when you're not sure of the exact title \nbut need \nto reference a document in other operations. Results are more accurate \nwhen you provide more of the actual title in your query.\n\nUse this tool when you need to:\n- Find a document's ID when you only know its title\n- Get the document ID for use in other operations\n- Verify if a document with a specific title exists\n- Find the best matching document if exact title is unknown\n\nArgs:\n    query: Title to search for (can be exact or partial)\n    collection_id: Optional collection to limit the search to\n    \nReturns:\n    Document ID if found, or best match information\n"
+      },
+      "read_document": {
+        "name": "read_document",
+        "description": "\nRetrieves and displays the full content of a document.\n\nUse this tool when you need to:\n- Access the complete content of a specific document\n- Review document information in detail\n- Quote or reference document content\n- Analyze document contents\n\nArgs:\n    document_id: The document ID to retrieve\n    \nReturns:\n    Formatted string containing the document title and content\n"
+      },
+      "export_document": {
+        "name": "export_document",
+        "description": "\nExports a document as plain markdown text.\n\nUse this tool when you need to:\n- Get clean markdown content without formatting\n- Extract document content for external use\n- Process document content in another application\n- Share document content outside Outline\n\nArgs:\n    document_id: The document ID to export\n    \nReturns:\n    Document content in markdown format without additional formatting\n"
+      },
+      "create_document": {
+        "name": "create_document",
+        "description": "\nCreates a new document in a specified collection.\n\nUse this tool when you need to:\n- Add new content to a knowledge base\n- Create documentation, guides, or notes\n- Add a child document to an existing parent\n- Start a new document thread or topic\n\nArgs:\n    title: The document title\n    collection_id: The collection ID to create the document in\n    text: Optional markdown content for the document\n    parent_document_id: Optional parent document ID for nesting\n    publish: Whether to publish the document immediately (True) or \n        save as draft (False)\n    \nReturns:\n    Result message with the new document ID\n"
+      },
+      "update_document": {
+        "name": "update_document",
+        "description": "\n        Modifies an existing document's title or content.\n        \n        IMPORTANT: This tool replaces the document content rather than just \nadding to it.\n        To update a document with changed data, you need to first read the \ndocument,\n        add your changes to the content, and then send the complete document \nwith your changes.\n        \n        Use this tool when you need to:\n        - Edit or update document content\n        - Change a document's title\n        - Append new content to an existing document\n        - Fix errors or add information to documents\n        \n        Args:\n            document_id: The document ID to update\n            title: New title (if None, keeps existing title)\n            text: New content (if None, keeps existing content)\n            append: If True, adds text to the end of document instead of \n    replacing\n            \n        Returns:\n            Result message confirming update\n        "
+      },
+      "add_comment": {
+        "name": "add_comment",
+        "description": "\nAdds a comment to a document or replies to an existing comment.\n\nUse this tool when you need to:\n- Provide feedback on document content\n- Ask questions about specific information\n- Reply to another user's comment\n- Collaborate with others on document development\n\nArgs:\n    document_id: The document to comment on\n    text: The comment text (supports markdown)\n    parent_comment_id: Optional ID of a parent comment (for replies)\n    \nReturns:\n    Result message with the new comment ID\n"
+      },
+      "move_document": {
+        "name": "move_document",
+        "description": "\nRelocates a document to a different collection or parent document.\n\nIMPORTANT: When moving a document that has child documents (nested \ndocuments), all child documents will move along with it, maintaining \ntheir hierarchical structure. You must specify either collection_id or \nparent_document_id (or both).\n\nUse this tool when you need to:\n- Reorganize your document hierarchy\n- Move a document to a more relevant collection\n- Change a document's parent document\n- Restructure content organization\n\nArgs:\n    document_id: The document ID to move\n    collection_id: Target collection ID (if moving between collections)\n    parent_document_id: Optional parent document ID (for nesting)\n    \nReturns:\n    Result message confirming the move operation\n"
+      },
+      "archive_document": {
+        "name": "archive_document",
+        "description": "\nArchives a document to remove it from active use while preserving it.\n\nIMPORTANT: Archived documents are removed from collections but remain\nsearchable in the system. They won't appear in normal collection views\nbut can still be found through search or the archive list.\n\nUse this tool when you need to:\n- Remove outdated or inactive documents from view\n- Clean up collections while preserving document history\n- Preserve documents that are no longer relevant\n- Temporarily hide documents without deleting them\n\nArgs:\n    document_id: The document ID to archive\n    \nReturns:\n    Result message confirming archival\n"
+      },
+      "unarchive_document": {
+        "name": "unarchive_document",
+        "description": "\nRestores a previously archived document to active status.\n\nUse this tool when you need to:\n- Restore archived documents to active use\n- Access or reference previously archived content\n- Make archived content visible in collections again\n- Update and reuse archived documents\n\nArgs:\n    document_id: The document ID to unarchive\n    \nReturns:\n    Result message confirming restoration\n"
+      },
+      "delete_document": {
+        "name": "delete_document",
+        "description": "\nMoves a document to trash or permanently deletes it.\n\nIMPORTANT: When permanent=False (the default), documents are moved to \ntrash and retained for 30 days before being permanently deleted. \nDuring \nthis period, they can be restored using the restore_document tool. \nSetting permanent=True bypasses the trash and immediately deletes the \ndocument without any recovery option.\n\nUse this tool when you need to:\n- Remove unwanted or unnecessary documents\n- Delete obsolete content\n- Clean up workspace by removing documents\n- Permanently remove sensitive information (with permanent=True)\n\nArgs:\n    document_id: The document ID to delete\n    permanent: If True, permanently deletes the document without \n        recovery option\n    \nReturns:\n    Result message confirming deletion\n"
+      },
+      "restore_document": {
+        "name": "restore_document",
+        "description": "\nRecovers a document from the trash back to active status.\n\nUse this tool when you need to:\n- Retrieve accidentally deleted documents\n- Restore documents from trash to active use\n- Recover documents deleted within the last 30 days\n- Access content that was previously trashed\n\nArgs:\n    document_id: The document ID to restore\n    \nReturns:\n    Result message confirming restoration\n"
+      },
+      "list_archived_documents": {
+        "name": "list_archived_documents",
+        "description": "\nDisplays all documents that have been archived.\n\nUse this tool when you need to:\n- Find specific archived documents\n- Review what documents have been archived\n- Identify documents for possible unarchiving\n- Check archive status of workspace content\n\nReturns:\n    Formatted string containing list of archived documents\n"
+      },
+      "list_trash": {
+        "name": "list_trash",
+        "description": "\nDisplays all documents currently in the trash.\n\nUse this tool when you need to:\n- Find deleted documents that can be restored\n- Review what documents are pending permanent deletion\n- Identify documents to restore from trash\n- Verify if specific documents were deleted\n\nReturns:\n    Formatted string containing list of documents in trash\n"
+      },
+      "list_document_comments": {
+        "name": "list_document_comments",
+        "description": "\nRetrieves comments on a specific document with pagination support.\n\nIMPORTANT: By default, this returns up to 25 comments at a time. If \nthere are more than 25 comments on the document, you'll need to make \nmultiple calls with different offset values to get all comments. The \nresponse will indicate if there \nare more comments available.\n\nUse this tool when you need to:\n- Review feedback and discussions on a document\n- See all comments from different users\n- Find specific comments or questions\n- Track collaboration and input on documents\n\nArgs:\n    document_id: The document ID to get comments from\n    include_anchor_text: Whether to include the document text that \n        comments refer to\n    limit: Maximum number of comments to return (default: 25)\n    offset: Number of comments to skip for pagination (default: 0)\n    \nReturns:\n    Formatted string containing comments with author, date, and \n    optional anchor text\n"
+      },
+      "get_comment": {
+        "name": "get_comment",
+        "description": "\nRetrieves a specific comment by its ID.\n\nUse this tool when you need to:\n- View details of a specific comment\n- Reference or quote a particular comment\n- Check comment content and metadata\n- Find a comment mentioned elsewhere\n\nArgs:\n    comment_id: The comment ID to retrieve\n    include_anchor_text: Whether to include the document text that \n        the comment refers to\n    \nReturns:\n    Formatted string with the comment content and metadata\n"
+      },
+      "get_document_backlinks": {
+        "name": "get_document_backlinks",
+        "description": "\n        Finds all documents that link to a specific document.\n        \n        Use this tool when you need to:\n        - Discover references to a document across the workspace\n        - Identify dependencies between documents\n        - Find documents related to a specific document\n        - Understand document relationships and connections\n        \n        Args:\n            document_id: The document ID to find backlinks for\n            \n        Returns:\n            Formatted string listing all documents that link to the specified \ndocument\n        "
+      },
+      "create_collection": {
+        "name": "create_collection",
+        "description": "\n    Creates a new collection for organizing documents.\n    \n    Use this tool when you need to:\n    - Create a new section or category for documents\n    - Set up a workspace for a new project or team\n    - Organize content by department or topic\n    - Establish a separate space for related documents\n    \n    Args:\n        name: Name for the collection\n        description: Optional description of the collection's purpose\n        color: Optional hex color code for visual identification \n(e.g. #FF0000)\n        \n    Returns:\n        Result message with the new collection ID\n    "
+      },
+      "update_collection": {
+        "name": "update_collection",
+        "description": "\nModifies an existing collection's properties.\n\nUse this tool when you need to:\n- Rename a collection\n- Update a collection's description\n- Change a collection's color coding\n- Refresh collection metadata\n\nArgs:\n    collection_id: The collection ID to update\n    name: Optional new name for the collection\n    description: Optional new description\n    color: Optional new hex color code (e.g. #FF0000)\n    \nReturns:\n    Result message confirming update\n"
+      },
+      "delete_collection": {
+        "name": "delete_collection",
+        "description": "\n        Permanently removes a collection and all its documents.\n        \n        Use this tool when you need to:\n        - Remove an entire section of content\n        - Delete obsolete project collections\n        - Remove collections that are no longer needed\n        - Clean up workspace organization\n        \n        WARNING: This action cannot be undone and will delete all documents \nwithin the collection.\n        \n        Args:\n            collection_id: The collection ID to delete\n            \n        Returns:\n            Result message confirming deletion\n        "
+      },
+      "export_collection": {
+        "name": "export_collection",
+        "description": "\nExports all documents in a collection to a downloadable file.\n\nIMPORTANT: This tool starts an asynchronous export operation which may \ntake time to complete. The function returns information about the \noperation, including its status. When the operation is complete, the \nfile can be downloaded or accessed via Outline's UI. The export \npreserves the document hierarchy and includes all document content and \nstructure in the \nspecified format.\n\nUse this tool when you need to:\n- Create a backup of collection content\n- Share collection content outside of Outline\n- Convert collection content to other formats\n- Archive collection content for offline use\n\nArgs:\n    collection_id: The collection ID to export\n    format: Export format (\"outline-markdown\", \"json\", or \"html\")\n    \nReturns:\n    Information about the export operation and how to access the file\n"
+      },
+      "export_all_collections": {
+        "name": "export_all_collections",
+        "description": "\nExports the entire workspace content to a downloadable file.\n\nIMPORTANT: This tool starts an asynchronous export operation which may \ntake time to complete, especially for large workspaces. The function \nreturns information about the operation, including its status. When \nthe operation is complete, the file can be downloaded or accessed via \nOutline's UI. The export includes all collections, documents, and \ntheir \nhierarchies in the specified format.\n\nUse this tool when you need to:\n- Create a complete backup of all workspace content\n- Migrate content to another system\n- Archive all workspace documents\n- Get a comprehensive export of knowledge base\n\nArgs:\n    format: Export format (\"outline-markdown\", \"json\", or \"html\")\n    \nReturns:\n    Information about the export operation and how to access the file\n"
+      },
+      "ask_ai_about_documents": {
+        "name": "ask_ai_about_documents",
+        "description": "\n      Queries document content using natural language questions.\n      \n      Use this tool when you need to:\n      - Find specific information across multiple documents\n      - Get direct answers to questions about document content\n      - Extract insights from your knowledge base\n      - Answer questions like \"What is our vacation policy?\" or \"How do we \nonboard new clients?\"\n      \n      Args:\n          question: The natural language question to ask\n          collection_id: Optional collection to limit the search to\n          document_id: Optional document to limit the search to\n          \n      Returns:\n          AI-generated answer based on document content with sources\n      "
+      }
+    }
   },
   "memory-mcp-server": {
     "category": "knowledge-memory",
-    "path": "knowledge-memory/memory-mcp-server.json"
+    "path": "knowledge-memory/memory-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "create_entities": {
+        "name": "create_entities",
+        "description": "Create multiple new entities in the knowledge graph"
+      },
+      "create_relations": {
+        "name": "create_relations",
+        "description": "Create multiple new relations between entities in the knowledge graph. Relations should be in active voice"
+      },
+      "add_observations": {
+        "name": "add_observations",
+        "description": "Add new observations to existing entities in the knowledge graph"
+      },
+      "delete_entities": {
+        "name": "delete_entities",
+        "description": "Delete multiple entities and their associated relations from the knowledge graph"
+      },
+      "delete_observations": {
+        "name": "delete_observations",
+        "description": "Delete specific observations from entities in the knowledge graph"
+      },
+      "delete_relations": {
+        "name": "delete_relations",
+        "description": "Delete multiple relations from the knowledge graph"
+      },
+      "read_graph": {
+        "name": "read_graph",
+        "description": "Read the entire knowledge graph"
+      },
+      "search_nodes": {
+        "name": "search_nodes",
+        "description": "Search for nodes in the knowledge graph based on a query"
+      },
+      "open_nodes": {
+        "name": "open_nodes",
+        "description": "Open specific nodes in the knowledge graph by their names"
+      }
+    }
   },
   "tana-mcp": {
     "category": "knowledge-memory",
@@ -14051,7 +15812,18 @@
   },
   "awslabs.bedrock-kb-retrieval-mcp-server": {
     "category": "knowledge-memory",
-    "path": "knowledge-memory/awslabs-bedrock-kb-retrieval-mcp-server.json"
+    "path": "knowledge-memory/awslabs-bedrock-kb-retrieval-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "ListKnowledgeBases": {
+        "name": "ListKnowledgeBases",
+        "description": "List all available Amazon Bedrock Knowledge Bases and their data sources.\n\nThis tool returns a mapping of knowledge base IDs to their details, including:\n- name: The human-readable name of the knowledge base\n- data_sources: A list of data sources within the knowledge base, each with:\n  - id: The unique identifier of the data source\n  - name: The human-readable name of the data source\n\n## Example response structure:\n```json\n{\n    \"kb-12345\": {\n        \"name\": \"Customer Support KB\",\n        \"data_sources\": [\n            {\"id\": \"ds-abc123\", \"name\": \"Technical Documentation\"},\n            {\"id\": \"ds-def456\", \"name\": \"FAQs\"}\n        ]\n    },\n    \"kb-67890\": {\n        \"name\": \"Product Information KB\",\n        \"data_sources\": [\n            {\"id\": \"ds-ghi789\", \"name\": \"Product Specifications\"}\n        ]\n    }\n}\n```\n\n## How to use this information:\n1. Extract the knowledge base IDs (like \"kb-12345\") for use with the QueryKnowledgeBases tool\n2. Note the data source IDs if you want to filter queries to specific data sources\n3. Use the names to determine which knowledge base and data source(s) are most relevant to the user's query\n"
+      },
+      "QueryKnowledgeBases": {
+        "name": "QueryKnowledgeBases",
+        "description": "Query an Amazon Bedrock Knowledge Base using natural language.\n\n## Usage Requirements\n- You MUST first use the ListKnowledgeBases tool to get valid knowledge base IDs\n- You can query different knowledge bases or make multiple queries to the same knowledge base\n\n## Query Tips\n- Use clear, specific natural language queries for best results\n- You can use this tool MULTIPLE TIMES with different queries to gather comprehensive information\n- Break complex questions into multiple focused queries\n- Consider querying for factual information and explanations separately\n\n## Tool output format\nThe response contains multiple JSON objects (one per line), each representing a retrieved document with:\n- content: The text content of the document\n- location: The source location of the document\n- score: The relevance score of the document\n\n\n## Interpretation Best Practices\n1. Extract and combine key information from multiple results\n2. Consider the source and relevance score when evaluating information\n3. Use follow-up queries to clarify ambiguous or incomplete information\n4. If the response is not relevant, try a different query, knowledge base, and/or data source\n5. After a few attempts, ask the user for clarification or a different query.\n"
+      }
+    }
   },
   "mcp-server-logseq": {
     "category": "knowledge-memory",
@@ -14176,7 +15948,14 @@
   },
   "mindmap-mcp-server": {
     "category": "knowledge-memory",
-    "path": "knowledge-memory/mindmap-mcp-server.json"
+    "path": "knowledge-memory/mindmap-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "convert_markdown_to_mindmap": {
+        "name": "convert_markdown_to_mindmap",
+        "description": "Convert Markdown content to a mindmap mind map.\n\nArgs:\n    markdown_content: The Markdown content to convert\n\nReturns:\n    Either the HTML content or the file path to the generated HTML, \n    depending on the --return-type server argument\n"
+      }
+    }
   },
   "joplin": {
     "category": "knowledge-memory",
@@ -14236,7 +16015,54 @@
   },
   "mcpunk": {
     "category": "knowledge-memory",
-    "path": "knowledge-memory/mcpunk.json"
+    "path": "knowledge-memory/mcpunk.json",
+    "validated": true,
+    "tools": {
+      "get_a_joke": {
+        "name": "get_a_joke",
+        "description": "Get a really funny joke! For testing :)"
+      },
+      "configure_project": {
+        "name": "configure_project",
+        "description": "Configure a new project containing files.\n\nEach file in the project is split into 'chunks' - logical sections like functions,\nclasses, markdown sections, and import blocks.\n\nAfter configuring, a common workflow is:\n1. list_all_files_in_project to get an overview of the project (with\n   an initial limit on the depth of the search)\n2. Find files by function/class definition:\n   find_files_by_chunk_content(... [\"def my_funk\"])\n3. Find files by function/class usage:\n   find_files_by_chunk_content(... [\"my_funk\"])\n4. Determine which chunks in the found files are relevant:\n    find_matching_chunks_in_file(...)\n5. Get details about the chunks:\n   chunk_details(...)\n\nUse ~ (tilde) literally if the user specifies it in paths.\n"
+      },
+      "list_all_files_in_project": {
+        "name": "list_all_files_in_project",
+        "description": "List all files in a project, returning a file tree.\n\nThis is useful for getting an overview of the project, or specific\nsubdirectories of the project.\n\nA project may have many files, so you are suggested\nto start with a depth limit to get an overview, and then continue increasing\nthe depth limit with a filter to look at specific subdirectories.\n"
+      },
+      "find_files_by_chunk_content": {
+        "name": "find_files_by_chunk_content",
+        "description": "Step 1: Find files containing chunks with matching text.\n\nReturns file tree only showing which files contain matches.\nYou must use find_matching_chunks_in_file on each relevant file\nto see the actual matches.\n\nExample workflow:\n1. Find files:\n   files = find_files_by_chunk_content(project, [\"MyClass\"])\n2. For each file, find actual matches:\n   matches = find_matching_chunks_in_file(file, [\"MyClass\"])\n3. Get content:\n   content = chunk_details(file, match_id)\n"
+      },
+      "find_matching_chunks_in_file": {
+        "name": "find_matching_chunks_in_file",
+        "description": "Step 2: Find the actual matching chunks in a specific file.\n\nRequired after find_files_by_chunk_content or list_all_files_in_project to see\nmatches, as those tools only show files, not their contents.\n\nThis can be used for things like:\n  - Finding all chunks in a file that make reference to a specific function\n    (e.g. find_matching_chunks_in_file(..., [\"my_funk\"])\n  - Finding a chunk where a specific function is defined\n    (e.g. find_matching_chunks_in_file(..., [\"def my_funk\"])\n\nReturns array of {n: name, t: type, id: identifier, chars: length}\n"
+      },
+      "chunk_details": {
+        "name": "chunk_details",
+        "description": "Get full content of a specific chunk.\n\nReturns chunk content as string.\n\nCommon patterns:\n1. Final step after find_matching_chunks_in_file finds relevant chunks\n2. Examining implementations after finding definitions/uses\n"
+      },
+      "list_most_recently_checked_out_branches": {
+        "name": "list_most_recently_checked_out_branches",
+        "description": "List the n most recently checked out branches in the project"
+      },
+      "diff_with_ref": {
+        "name": "diff_with_ref",
+        "description": "Return a summary of the diff between HEAD and the given ref.\n\nYou probably want the ref  to be the 'base' branch like develop or main, off which\nPRs are made - and you can likely determine this by viewing the most recently\nchecked out branches.\n"
+      },
+      "add_tasks": {
+        "name": "add_tasks",
+        "description": "Add tasks to be completed by an LLM in the future.\n\nDo not add a task unless explicitly instructed to do so.\n\nWhen adding tasks, provide all required context.\nFor example: step 1 set up the ~/git/p1 and ~/git/p2 repos projects step 2 load the diff with\n    ref develop step 3 confirm that the function added in /examples/script.py is\n    consistent with the existing /examples/other_script.py file.\nThe common_prefix is prefixed to each task's action (if not None), it's provided\nto avoid having to repeat the common context for each task.\n\nCall this tool multiple times to add many tasks.\n"
+      },
+      "get_task": {
+        "name": "get_task",
+        "description": "Get a single task.\n\nDo not use this tool unless explicitly told to do so.\nAfter you complete the task, mark it as done by calling the `set_task_done` tool.\n"
+      },
+      "mark_task_done": {
+        "name": "mark_task_done",
+        "description": "Set a task as done wth a specific outcome.\n\nYou can call this multiple times to update the outcome.\n"
+      }
+    }
   },
   "graphiti": {
     "category": "knowledge-memory",
@@ -14993,7 +16819,82 @@
   },
   "mcp-server-aliyun-observability": {
     "category": "monitoring",
-    "path": "monitoring/mcp-server-aliyun-observability.json"
+    "path": "monitoring/mcp-server-aliyun-observability.json",
+    "validated": true,
+    "tools": {
+      "sls_list_projects": {
+        "name": "sls_list_projects",
+        "description": "列出阿里云日志服务中的所有项目。\n\n## 功能概述\n\n该工具可以列出指定区域中的所有SLS项目，支持通过项目名进行模糊搜索。如果不提供项目名称，则返回该区域的所有项目。\n\n## 使用场景\n\n- 当需要查找特定项目是否存在时\n- 当需要获取某个区域下所有可用的SLS项目列表时\n- 当需要根据项目名称的部分内容查找相关项目时\n\n## 返回数据结构\n\n返回的项目信息包含：\n- project_name: 项目名称\n- description: 项目描述\n- region_id: 项目所在区域\n\n## 查询示例\n\n- \"有没有叫 XXX 的 project\"\n- \"列出所有SLS项目\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    projectName: 项目名称查询字符串，支持模糊搜索\n    limit: 返回结果的最大数量，范围1-100，默认10\n    regionId: 阿里云区域ID,region id format like \"xx-xxx\",like \"cn-hangzhou\"\n\nReturns:\n    包含项目信息的字典列表，每个字典包含project_name、description和region_id\n"
+      },
+      "sls_list_logstores": {
+        "name": "sls_list_logstores",
+        "description": "列出SLS项目中的日志库。\n\n## 功能概述\n\n该工具可以列出指定SLS项目中的所有日志库，如果不选，则默认为日志库类型\n支持通过日志库名称进行模糊搜索。如果不提供日志库名称，则返回项目中的所有日志库。\n\n## 使用场景\n\n- 当需要查找特定项目下是否存在某个日志库时\n- 当需要获取项目中所有可用的日志库列表时\n- 当需要根据日志库名称的部分内容查找相关日志库时\n- 如果从上下文未指定 project参数，除非用户说了遍历，则可使用 sls_list_projects 工具获取项目列表\n\n## 是否指标库\n\n如果需要查找指标或者时序相关的库,请将is_metric_store参数设置为True\n\n## 查询示例\n\n- \"我想查询有没有 XXX 的日志库\"\n- \"某个 project 有哪些 log store\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    project: SLS项目名称，必须精确匹配\n    log_store: 日志库名称，支持模糊搜索\n    limit: 返回结果的最大数量，范围1-100，默认10\n    is_metric_store: 是否指标库，可选值为True或False，默认为False\n    region_id: 阿里云区域ID\n\nReturns:\n    日志库名称的字符串列表\n"
+      },
+      "sls_describe_logstore": {
+        "name": "sls_describe_logstore",
+        "description": "获取SLS日志库的结构信息。\n\n## 功能概述\n\n该工具用于获取指定SLS项目中日志库的索引信息和结构定义，包括字段类型、别名、是否大小写敏感等信息。\n\n## 使用场景\n\n- 当需要了解日志库的字段结构时\n- 当需要获取日志库的索引配置信息时\n- 当构建查询语句前需要了解可用字段时\n- 当需要分析日志数据结构时\n\n## 返回数据结构\n\n返回一个字典，键为字段名，值包含以下信息：\n- alias: 字段别名\n- sensitive: 是否大小写敏感\n- type: 字段类型\n- json_keys: JSON字段的子字段信息\n\n## 查询示例\n\n- \"我想查询 XXX 的日志库的 schema\"\n- \"我想查询 XXX 的日志库的 index\"\n- \"我想查询 XXX 的日志库的结构信息\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    project: SLS项目名称，必须精确匹配\n    log_store: SLS日志库名称，必须精确匹配\n    region_id: 阿里云区域ID\n\nReturns:\n    包含日志库结构信息的字典\n"
+      },
+      "sls_execute_sql_query": {
+        "name": "sls_execute_sql_query",
+        "description": "执行SLS日志查询。\n\n## 功能概述\n\n该工具用于在指定的SLS项目和日志库上执行查询语句，并返回查询结果。查询将在指定的时间范围内执行。 如果上下文没有提到具体的 SQL 语句，必须优先使用 sls_translate_text_to_sql_query 工具生成查询语句,无论问题有多简单\n\n## 使用场景\n\n- 当需要根据特定条件查询日志数据时\n- 当需要分析特定时间范围内的日志信息时\n- 当需要检索日志中的特定事件或错误时\n- 当需要统计日志数据的聚合信息时\n\n\n## 查询语法\n\n查询必须使用SLS有效的查询语法，而非自然语言。如果不了解日志库的结构，可以先使用sls_describe_logstore工具获取索引信息。\n\n## 时间范围\n\n查询必须指定时间范围：  if the query is generated by sls_translate_text_to_sql_query tool, should use the fromTimestampInSeconds and toTimestampInSeconds in the sls_translate_text_to_sql_query response\n- fromTimestampInSeconds: 开始时间戳（秒）\n- toTimestampInSeconds: 结束时间戳（秒）\n\n## 查询示例\n\n- \"帮我查询下 XXX 的日志信息\"\n- \"查找最近一小时内的错误日志\"\n\n## 错误处理\n- Column xxx can not be resolved 如果是 sls_translate_text_to_sql_query 工具生成的查询语句 可能存在查询列未开启统计，可以提示用户增加相对应的信息，或者调用 sls_describe_logstore 工具获取索引信息之后，要用户选择正确的字段或者提示用户对列开启统计。当确定列开启统计之后，可以再次调用sls_translate_text_to_sql_query 工具生成查询语句\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    project: SLS项目名称\n    logStore: SLS日志库名称\n    query: SLS查询语句\n    fromTimestamp: 查询开始时间戳（秒）\n    toTimestamp: 查询结束时间戳（秒）\n    limit: 返回结果的最大数量，范围1-100，默认10\n    regionId: 阿里云区域ID\n\nReturns:\n    查询结果列表，每个元素为一条日志记录\n"
+      },
+      "sls_translate_text_to_sql_query": {
+        "name": "sls_translate_text_to_sql_query",
+        "description": "将自然语言转换为SLS查询语句。当用户有明确的 logstore 查询需求，必须优先使用该工具来生成查询语句\n\n## 功能概述\n\n该工具可以将自然语言描述转换为有效的SLS查询语句，便于用户使用自然语言表达查询需求。用户有任何 SLS 日志查询需求时，都需要优先使用该工具。\n\n## 使用场景\n\n- 当用户不熟悉SLS查询语法时\n- 当需要快速构建复杂查询时\n- 当需要从自然语言描述中提取查询意图时\n\n## 使用限制\n\n- 仅支持生成SLS查询，不支持其他数据库的SQL如MySQL、PostgreSQL等\n- 生成的是查询语句，而非查询结果，需要配合sls_execute_query工具使用\n- 如果查询涉及ARMS应用，应优先使用arms_generate_trace_query工具\n- 需要对应的 log_sotre 已经设定了索引信息，如果生成的结果里面有字段没有索引或者开启统计，可能会导致查询失败，需要友好的提示用户增加相对应的索引信息\n\n## 最佳实践\n\n- 提供清晰简洁的自然语言描述\n- 不要在描述中包含项目或日志库名称\n- 如有需要，指定查询的时间范围\n- 首次生成的查询可能不完全符合要求，可能需要多次尝试\n\n## 查询示例\n\n- \"帮我生成下 XXX 的日志查询语句\"\n- \"查找最近一小时内的错误日志\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    text: 用于生成查询的自然语言文本\n    project: SLS项目名称\n    log_store: SLS日志库名称\n    region_id: 阿里云区域ID\n\nReturns:\n    生成的SLS查询语句\n"
+      },
+      "sls_diagnose_query": {
+        "name": "sls_diagnose_query",
+        "description": "诊断SLS查询语句。\n\n## 功能概述\n\n当 SLS 查询语句执行失败时，可以调用该工具，根据错误信息，生成诊断结果。诊断结果会包含查询语句的正确性、性能分析、优化建议等信息。\n\n## 使用场景\n\n- 当需要诊断SLS查询语句的正确性时\n- 当 SQL 执行错误需要查找原因时\n\n## 查询示例\n\n- \"帮我诊断下 XXX 的日志查询语句\"\n- \"帮我分析下 XXX 的日志查询语句\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    query: SLS查询语句\n    error_message: 错误信息\n    project: SLS项目名称\n    log_store: SLS日志库名称\n    region_id: 阿里云区域ID\n"
+      },
+      "sls_get_regions": {
+        "name": "sls_get_regions",
+        "description": "获取阿里云的部分区域列表。\n\n## 功能概述\n\n该工具用于获取阿里云的部分区域列表，便于在执行SLS查询时指定区域。\n\n## 使用场景\n\n- 当需要获取阿里云的部分区域列表时\n- 当需要根据区域进行SLS查询时\n- 当用户没有明确指定区域ID 时，可以调用该工具获取区域列表，并要求用户进行选择\n\n## 返回数据格式\n\n返回包含区域列表的字典，每个字典包含region_id和region_name。\n\n## 查询示例\n\n- \"获取阿里云的部分区域列表\"\n"
+      },
+      "sls_get_current_time": {
+        "name": "sls_get_current_time",
+        "description": "获取当前时间。\n\n## 功能概述\n1. 获取当前时间，会返回当前时间字符串和当前时间戳(毫秒)\n\n## 使用场景\n1. 只有当无法从聊天记录里面获取到当前时间时候才可以调用该工具\n"
+      },
+      "arms_search_apps": {
+        "name": "arms_search_apps",
+        "description": "搜索ARMS应用。\n\n## 功能概述\n\n该工具用于根据应用名称搜索ARMS应用，返回应用的基本信息，包括应用名称、PID、用户ID和类型。\n\n## 使用场景\n\n- 当需要查找特定名称的应用时\n- 当需要获取应用的PID以便进行其他ARMS操作时\n- 当需要检查用户拥有的应用列表时\n\n## 搜索条件\n\n- app_name_query必须是应用名称的一部分，而非自然语言\n- 搜索结果将分页返回，可以指定页码和每页大小\n\n## 返回数据结构\n\n返回一个字典，包含以下信息：\n- total: 符合条件的应用总数\n- page_size: 每页大小\n- page_number: 当前页码\n- trace_apps: 应用列表，每个应用包含app_name、pid、user_id和type\n\n## 查询示例\n\n- \"帮我查询下 XXX 的应用\"\n- \"找出名称包含'service'的应用\"\n\nArgs:\n    ctx: MCP上下文，用于访问ARMS客户端\n    app_name_query: 应用名称查询字符串\n    region_id: 阿里云区域ID\n    page_size: 每页大小，范围1-100，默认20\n    page_number: 页码，默认1\n\nReturns:\n    包含应用信息的字典\n"
+      },
+      "arms_generate_trace_query": {
+        "name": "arms_generate_trace_query",
+        "description": "生成ARMS应用的调用链查询语句。\n\n## 功能概述\n\n该工具用于将自然语言描述转换为ARMS调用链查询语句，便于分析应用性能和问题。\n\n## 使用场景\n\n- 当需要查询应用的调用链信息时\n- 当需要分析应用性能问题时\n- 当需要跟踪特定请求的执行路径时\n- 当需要分析服务间调用关系时\n\n## 查询处理\n\n工具会将自然语言问题转换为SLS查询，并返回：\n- 生成的SLS查询语句\n- 存储调用链数据的项目名\n- 存储调用链数据的日志库名\n\n## 查询上下文\n\n查询会考虑以下信息：\n- 应用的PID\n- 响应时间以纳秒存储，需转换为毫秒\n- 数据以span记录存储，查询耗时需要对符合条件的span进行求和\n- 服务相关信息使用serviceName字段\n- 如果用户明确提出要查询 trace信息，则需要在查询问题上question 上添加说明返回trace信息\n\n## 查询示例\n\n- \"帮我查询下 XXX 的 trace 信息\"\n- \"分析最近一小时内响应时间超过1秒的调用链\"\n\nArgs:\n    ctx: MCP上下文，用于访问ARMS和SLS客户端\n    user_id: 用户阿里云账号ID\n    pid: 应用的PID\n    region_id: 阿里云区域ID\n    question: 查询调用链的自然语言问题\n\nReturns:\n    包含查询信息的字典，包括sls_query、project和log_store\n"
+      },
+      "arms_profile_flame_analysis": {
+        "name": "arms_profile_flame_analysis",
+        "description": "分析ARMS应用火焰图性能热点。\n\n## 功能概述\n\n当应用存在性能问题且开启持续剖析时，可以调用该工具对ARMS应用火焰图性能热点进行分析，生成分析结果。分析结果会包含火焰图的性能热点问题、优化建议等信息。\n\n## 使用场景\n\n- 当需要分析ARMS应用火焰图性能问题时\n\n## 查询示例\n\n- \"帮我分析下ARMS应用 XXX 的火焰图性能热点\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    pid: ARMS应用监控服务PID\n    startMs: 分析的开始时间，通过get_current_time工具获取毫秒级时间戳\n    endMs: 分析的结束时间，通过get_current_time工具获取毫秒级时间戳\n    profileType: Profile类型，用于选择需要分析的Profile指标，支持CPU热点和内存热点，如'cpu'、'memory'\n    ip: ARMS应用服务主机地址，非必要参数，用于选择所在的服务机器，如有多个填写时以英文逗号\",\"分隔，如'192.168.0.1,192.168.0.2'，不填写默认查询服务所在的所有IP\n    thread: 服务线程名称，非必要参数，用于选择对应线程，如有多个填写时以英文逗号\",\"分隔，如'C1 CompilerThre,C2 CompilerThre'，不填写默认查询服务所有线程\n    threadGroup: 服务聚合线程组名称，非必要参数，用于选择对应线程组，如有多个填写时以英文逗号\",\"分隔，如'http-nio-*-exec-*,http-nio-*-ClientPoller-*'，不填写默认查询服务所有聚合线程组\n    regionId: 阿里云区域ID，如'cn-hangzhou'、'cn-shanghai'等\n"
+      },
+      "arms_diff_profile_flame_analysis": {
+        "name": "arms_diff_profile_flame_analysis",
+        "description": "对比两个时间段火焰图的性能变化。\n\n## 功能概述\n\n对应用在两个不同时间段内的性能进行分析，生成差分火焰图。通常用于发布前后或性能优化前后性能对比，帮助识别性能提升或退化。\n\n## 使用场景\n\n- 发布前后、性能优化前后不同时间段火焰图性能对比\n\n## 查询示例\n\n- \"帮我分析应用 XXX 在发布前后的性能变化情况\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    pid: ARMS应用监控服务PID\n    currentStartMs: 火焰图当前（基准）时间段的开始时间戳，通过get_current_time工具获取毫秒级时间戳\n    currentEndMs: 火焰图当前（基准）时间段的结束时间戳，通过get_current_time工具获取毫秒级时间戳\n    referenceStartMs: 火焰图对比时间段（参考时间段）的开始时间戳，通过get_current_time工具获取毫秒级时间戳\n    referenceEndMs: 火焰图对比时间段（参考时间段）的结束时间戳，通过get_current_time工具获取毫秒级时间戳\n    profileType: Profile类型，如'cpu'、'memory'\n    ip: ARMS应用服务主机地址，非必要参数，用于选择所在的服务机器，如有多个填写时以英文逗号\",\"分隔，如'192.168.0.1,192.168.0.2'，不填写默认查询服务所在的所有IP\n    thread: 服务线程名称，非必要参数，用于选择对应线程，如有多个填写时以英文逗号\",\"分隔，如'C1 CompilerThre,C2 CompilerThre'，不填写默认查询服务所有线程\n    threadGroup: 服务聚合线程组名称，非必要参数，用于选择对应线程组，如有多个填写时以英文逗号\",\"分隔，如'http-nio-*-exec-*,http-nio-*-ClientPoller-*'，不填写默认查询服务所有聚合线程组\n    regionId: 阿里云区域ID，如'cn-hangzhou'、'cn-shanghai'等\n"
+      },
+      "arms_get_application_info": {
+        "name": "arms_get_application_info",
+        "description": "\n根据 PID获取具体某个应用的信息，\n## 功能概述\n1. 获取ARMS应用信息，会返回应用的 PID，AppName,开发语言类型比如 java,python 等\n\n## 使用场景\n1. 当用户明确提出要查询某个应用的信息时，可以调用该工具\n2. 有场景需要获取应用的开发语言类型，可以调用该工具\n"
+      },
+      "arms_trace_quality_analysis": {
+        "name": "arms_trace_quality_analysis",
+        "description": "Trace 质量检测\n\n## 功能概述\n识别指定 traceId 的 Trace 是否存在完整性问题（断链）和性能问题（错慢调用）\n\n## 使用场景\n\n- 检测调用链是否存在问题\n\n## 查询示例\n\n- \"帮我分析调用链\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    traceId: 待分析的 Trace 的 traceId，必要参数\n    startMs: 分析的开始时间，通过get_current_time工具获取毫秒级时间戳\n    endMs: 分析的结束时间，通过get_current_time工具获取毫秒级时间戳\n    regionId: 阿里云区域ID，如'cn-hangzhou'、'cn-shanghai'等\n"
+      },
+      "arms_slow_trace_analysis": {
+        "name": "arms_slow_trace_analysis",
+        "description": "深入分析 Trace 慢调用根因\n\n## 功能概述\n\n针对 Trace 中的慢调用进行诊断分析，输出包含概述、根因、影响范围及解决方案的诊断报告。\n\n## 使用场景\n\n- 性能问题定位和修复\n\n## 查询示例\n\n- \"请分析 ${traceId} 这个 trace 慢的原因\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    traceId: 待分析的Trace的 traceId，必要参数\n    startMs: 分析的开始时间，通过get_current_time工具获取毫秒级时间戳\n    endMs: 分析的结束时间，通过get_current_time工具获取毫秒级时间戳\n    regionId: 阿里云区域ID，如'cn-hangzhou'、'cn-shanghai'等\n"
+      },
+      "arms_error_trace_analysis": {
+        "name": "arms_error_trace_analysis",
+        "description": "深入分析 Trace 错误根因\n\n## 功能概述\n\n针对 Trace 中的错误调用进行深入诊断分析，输出包含概述、根因、影响范围及解决方案的错误诊断报告。\n\n## 使用场景\n\n- 性能问题定位和修复\n\n## 查询示例\n\n- \"请分析 ${traceId} 这个 trace 发生错误的原因\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    traceId: 待分析的Trace的 traceId，必要参数\n    startMs: 分析的开始时间，通过get_current_time工具获取毫秒级时间戳\n    endMs: 分析的结束时间，通过get_current_time工具获取毫秒级时间戳\n    regionId: 阿里云区域ID，如'cn-hangzhou'、'cn-shanghai'等\n"
+      },
+      "cms_translate_text_to_promql": {
+        "name": "cms_translate_text_to_promql",
+        "description": "将自然语言转换为Prometheus PromQL查询语句。\n\n## 功能概述\n\n该工具可以将自然语言描述转换为有效的PromQL查询语句，便于用户使用自然语言表达查询需求。\n\n## 使用场景\n\n- 当用户不熟悉PromQL查询语法时\n- 当需要快速构建复杂查询时\n- 当需要从自然语言描述中提取查询意图时\n\n## 使用限制\n\n- 仅支持生成PromQL查询\n- 生成的是查询语句，而非查询结果\n- 禁止使用sls_execute_query工具执行，两者接口不兼容\n\n## 最佳实践\n\n- 提供清晰简洁的自然语言描述\n- 不要在描述中包含项目或时序库名称\n- 首次生成的查询可能不完全符合要求，可能需要多次尝试\n\n## 查询示例\n\n- \"帮我生成 XXX 的PromQL查询语句\"\n- \"查询每个namespace下的Pod数量\"\n\nArgs:\n    ctx: MCP上下文，用于访问SLS客户端\n    text: 用于生成查询的自然语言文本\n    project: SLS项目名称\n    metricStore: SLS时序库名称\n    regionId: 阿里云区域ID\n\nReturns:\n    生成的PromQL查询语句\n"
+      },
+      "cms_execute_promql_query": {
+        "name": "cms_execute_promql_query",
+        "description": "执行Prometheus指标查询。\n\n## 功能概述\n\n该工具用于在指定的SLS项目和时序库上执行查询语句，并返回查询结果。查询将在指定的时间范围内执行。\n如果上下文没有提到具体的 SQL 语句，必须优先使用 cms_translate_text_to_promql 工具生成查询语句,无论问题有多简单。\n如果上下文没有提到具体的时间戳，必须优先使用 sls_get_current_time 工具生成时间戳参数，默认为最近15分钟\n\n## 使用场景\n\n- 当需要根据特定条件查询日志数据时\n- 当需要分析特定时间范围内的日志信息时\n- 当需要检索日志中的特定事件或错误时\n- 当需要统计日志数据的聚合信息时\n\n\n## 查询语法\n\n查询必须使用PromQL有效的查询语法，而非自然语言。\n\n## 时间范围\n\n查询必须指定时间范围：\n- fromTimestampInSeconds: 开始时间戳（秒）\n- toTimestampInSeconds: 结束时间戳（秒）\n默认为最近15分钟，需要调用 sls_get_current_time 工具获取当前时间\n\n## 查询示例\n\n- \"帮我查询下 job xxx 的采集状态\"\n- \"查一下当前有多少个 Pod\"\n\n## 输出\n查询结果为：xxxxx\n对应的图示：将 image 中的 URL 连接到图示中，并展示在图示中。\n\nArgs:\n    ctx: MCP上下文，用于访问CMS客户端\n    project: SLS项目名称\n    metricStore: SLS日志库名称\n    query: PromQL查询语句\n    fromTimestampInSeconds: 查询开始时间戳（秒）\n    toTimestampInSeconds: 查询结束时间戳（秒）\n    regionId: 阿里云区域ID\n\nReturns:\n    查询结果列表，每个元素为一条日志记录\n"
+      }
+    }
   },
   "mcp-sentry-custom": {
     "category": "monitoring",
@@ -15191,11 +17092,25 @@
   },
   "searxng-simple-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/searxng-simple-mcp.json"
+    "path": "search-data-extraction/searxng-simple-mcp.json",
+    "validated": true,
+    "tools": {
+      "web_search": {
+        "name": "web_search",
+        "description": "\nPerform a web search using SearxNG and return formatted results.\n\nResults are returned in either text format (human-readable) or JSON format\ndepending on the result_format parameter selected.\n\n"
+      }
+    }
   },
   "backlinks-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/backlinks-mcp.json"
+    "path": "search-data-extraction/backlinks-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_backlinks_list": {
+        "name": "get_backlinks_list",
+        "description": "\nGet backlinks list for the specified domain\nArgs:\n    domain (str): The domain to query\nReturns:\n    List of backlinks for the domain, containing title, URL, domain rating, etc.\n"
+      }
+    }
   },
   "@cyanheads/pubmed-mcp-server": {
     "category": "search-data-extraction",
@@ -15347,7 +17262,18 @@
   },
   "vectara-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/vectara-mcp.json"
+    "path": "search-data-extraction/vectara-mcp.json",
+    "validated": true,
+    "tools": {
+      "ask_vectara": {
+        "name": "ask_vectara",
+        "description": "\nRun a RAG query using Vectara, returning search results with a generated response.\n\nArgs:\n    query: str, The user query to run - required.\n    corpus_keys: list[str], List of Vectara corpus keys to use for the search - required. Please ask the user to provide one or more corpus keys. \n    api_key: str, The Vectara API key - required.\n    n_sentences_before: int, Number of sentences before the answer to include in the context - optional, default is 2.\n    n_sentences_after: int, Number of sentences after the answer to include in the context - optional, default is 2.\n    lexical_interpolation: float, The amount of lexical interpolation to use - optional, default is 0.005.\n    max_used_search_results: int, The maximum number of search results to use - optional, default is 10.\n    generation_preset_name: str, The name of the generation preset to use - optional, default is \"vectara-summary-table-md-query-ext-jan-2025-gpt-4o\".\n    response_language: str, The language of the response - optional, default is \"eng\".\n\nReturns:\n    The response from Vectara, including the generated answer and the search results.\n"
+      },
+      "search_vectara": {
+        "name": "search_vectara",
+        "description": "\nRun a semantic search query using Vectara, without generation.\n\nArgs:\n    query: str, The user query to run - required.\n    corpus_keys: list[str], List of Vectara corpus keys to use for the search - required. Please ask the user to provide one or more corpus keys. \n    api_key: str, The Vectara API key - required.\n    n_sentences_before: int, Number of sentences before the answer to include in the context - optional, default is 2.\n    n_sentences_after: int, Number of sentences after the answer to include in the context - optional, default is 2.\n    lexical_interpolation: float, The amount of lexical interpolation to use - optional, default is 0.005.\n\nReturns:\n    The response from Vectara, including the matching search results.\n"
+      }
+    }
   },
   "orion-vision-mcp": {
     "category": "search-data-extraction",
@@ -15366,7 +17292,22 @@
   },
   "youtube-dlp-server": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/youtube-dlp-server.json"
+    "path": "search-data-extraction/youtube-dlp-server.json",
+    "validated": true,
+    "tools": {
+      "get-video-info": {
+        "name": "get-video-info",
+        "description": "Extract detailed information from a YouTube video URL without downloading"
+      },
+      "get-video-subtitles": {
+        "name": "get-video-subtitles",
+        "description": "Extract subtitles and captions from a YouTube video"
+      },
+      "get-top-comments": {
+        "name": "get-top-comments",
+        "description": "Extract top comments from a YouTube video (sorted by likes)"
+      }
+    }
   },
   "@suthio/brave-deep-research-mcp": {
     "category": "search-data-extraction",
@@ -15419,7 +17360,26 @@
   },
   "mcp-hn": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/mcp-hn.json"
+    "path": "search-data-extraction/mcp-hn.json",
+    "validated": true,
+    "tools": {
+      "get_stories": {
+        "name": "get_stories",
+        "description": "Get stories from Hacker News. The options are `top`, `new`, `ask_hn`, `show_hn` for types of stories. This doesn't include the comments. Use `get_story_info` to get the comments."
+      },
+      "get_user_info": {
+        "name": "get_user_info",
+        "description": "Get user info from Hacker News, including the stories they've submitted"
+      },
+      "search_stories": {
+        "name": "search_stories",
+        "description": "Search stories from Hacker News. It is generally recommended to use simpler queries to get a broader set of results (less than 5 words). Very targetted queries may not return any results."
+      },
+      "get_story_info": {
+        "name": "get_story_info",
+        "description": "Get detailed story info from Hacker News, including the comments"
+      }
+    }
   },
   "news-mcp-server": {
     "category": "search-data-extraction",
@@ -15487,11 +17447,25 @@
   },
   "mcp-search-linkup": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/mcp-search-linkup.json"
+    "path": "search-data-extraction/mcp-search-linkup.json",
+    "validated": true,
+    "tools": {
+      "search-web": {
+        "name": "search-web",
+        "description": "Search the web in real time using Linkup. Use this tool whenever the user needs trusted facts, news, or source-backed information. Returns comprehensive content from the most relevant sources."
+      }
+    }
   },
   "mcp-google-cse": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/mcp-google-cse.json"
+    "path": "search-data-extraction/mcp-google-cse.json",
+    "validated": true,
+    "tools": {
+      "google_search": {
+        "name": "google_search",
+        "description": "Search the custom search engine using the search term. Regular query arguments can also be used, like appending site:reddit.com or after:2024-04-30. If available and/or requested, the links of the search results should be used in a follow-up request using a different tool to get the full content. Example: \"claude.ai features site:reddit.com after:2024-04-30\""
+      }
+    }
   },
   "gnews": {
     "category": "search-data-extraction",
@@ -15552,7 +17526,30 @@
   },
   "mcp-server-pacman": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/mcp-server-pacman.json"
+    "path": "search-data-extraction/mcp-server-pacman.json",
+    "validated": true,
+    "tools": {
+      "search_package": {
+        "name": "search_package",
+        "description": "Search for packages in package indices (PyPI, npm, crates.io, Terraform Registry)"
+      },
+      "package_info": {
+        "name": "package_info",
+        "description": "Get detailed information about a specific package"
+      },
+      "search_docker_image": {
+        "name": "search_docker_image",
+        "description": "Search for Docker images in Docker Hub"
+      },
+      "docker_image_info": {
+        "name": "docker_image_info",
+        "description": "Get detailed information about a specific Docker image"
+      },
+      "terraform_module_latest_version": {
+        "name": "terraform_module_latest_version",
+        "description": "Get the latest version of a Terraform module"
+      }
+    }
   },
   "twitter-noauth": {
     "category": "other-tools-and-integrations",
@@ -15733,7 +17730,42 @@
   },
   "mcp-server-reddit": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/mcp-server-reddit.json"
+    "path": "search-data-extraction/mcp-server-reddit.json",
+    "validated": true,
+    "tools": {
+      "get_frontpage_posts": {
+        "name": "get_frontpage_posts",
+        "description": "Get hot posts from Reddit frontpage"
+      },
+      "get_subreddit_info": {
+        "name": "get_subreddit_info",
+        "description": "Get information about a subreddit"
+      },
+      "get_subreddit_hot_posts": {
+        "name": "get_subreddit_hot_posts",
+        "description": "Get hot posts from a specific subreddit"
+      },
+      "get_subreddit_new_posts": {
+        "name": "get_subreddit_new_posts",
+        "description": "Get new posts from a specific subreddit"
+      },
+      "get_subreddit_top_posts": {
+        "name": "get_subreddit_top_posts",
+        "description": "Get top posts from a specific subreddit"
+      },
+      "get_subreddit_rising_posts": {
+        "name": "get_subreddit_rising_posts",
+        "description": "Get rising posts from a specific subreddit"
+      },
+      "get_post_content": {
+        "name": "get_post_content",
+        "description": "Get detailed content of a specific post"
+      },
+      "get_post_comments": {
+        "name": "get_post_comments",
+        "description": "Get comments from a post"
+      }
+    }
   },
   "space-frontiers-search": {
     "category": "search-data-extraction",
@@ -15768,7 +17800,26 @@
   },
   "arxiv-mcp-server": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/arxiv-mcp-server.json"
+    "path": "search-data-extraction/arxiv-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "search_papers": {
+        "name": "search_papers",
+        "description": "Search for papers on arXiv with advanced filtering and query optimization.\n\nQUERY CONSTRUCTION GUIDELINES:\n- Use QUOTED PHRASES for exact matches: \"multi-agent systems\", \"neural networks\", \"machine learning\"\n- Combine related concepts with OR: \"AI agents\" OR \"software agents\" OR \"intelligent agents\"  \n- Use field-specific searches for precision:\n  - ti:\"exact title phrase\" - search in titles only\n  - au:\"author name\" - search by author\n  - abs:\"keyword\" - search in abstracts only\n- Use ANDNOT to exclude unwanted results: \"machine learning\" ANDNOT \"survey\"\n- For best results, use 2-4 core concepts rather than long keyword lists\n\nADVANCED SEARCH PATTERNS:\n- Field + phrase: ti:\"transformer architecture\" for papers with exact title phrase\n- Multiple fields: au:\"Smith\" AND ti:\"quantum\" for author Smith's quantum papers  \n- Exclusions: \"deep learning\" ANDNOT (\"survey\" OR \"review\") to exclude survey papers\n- Broad + narrow: \"artificial intelligence\" AND (robotics OR \"computer vision\")\n\nCATEGORY FILTERING (highly recommended for relevance):\n- cs.AI: Artificial Intelligence\n- cs.MA: Multi-Agent Systems  \n- cs.LG: Machine Learning\n- cs.CL: Computation and Language (NLP)\n- cs.CV: Computer Vision\n- cs.RO: Robotics\n- cs.HC: Human-Computer Interaction\n- cs.CR: Cryptography and Security\n- cs.DB: Databases\n\nEXAMPLES OF EFFECTIVE QUERIES:\n- ti:\"reinforcement learning\" with categories: [\"cs.LG\", \"cs.AI\"] - for RL papers by title\n- au:\"Hinton\" AND \"deep learning\" with categories: [\"cs.LG\"] - for Hinton's deep learning work\n- \"multi-agent\" ANDNOT \"survey\" with categories: [\"cs.MA\"] - exclude survey papers\n- abs:\"transformer\" AND ti:\"attention\" with categories: [\"cs.CL\"] - attention papers with transformer abstracts\n\nDATE FILTERING: Use YYYY-MM-DD format for historical research:\n- date_to: \"2015-12-31\" - for foundational/classic work (pre-2016)\n- date_from: \"2020-01-01\" - for recent developments (post-2020)\n- Both together for specific time periods\n\nRESULT QUALITY: Results sorted by RELEVANCE (most relevant papers first), not just newest papers.\nThis ensures you get the most pertinent results regardless of publication date.\n\nTIPS FOR FOUNDATIONAL RESEARCH:\n- Use date_to: \"2010-12-31\" to find classic papers on BDI, SOAR, ACT-R\n- Combine with field searches: ti:\"BDI\" AND abs:\"belief desire intention\"  \n- Try author searches: au:\"Rao\" AND \"BDI\" for Anand Rao's foundational BDI work"
+      },
+      "download_paper": {
+        "name": "download_paper",
+        "description": "Download a paper and create a resource for it"
+      },
+      "list_papers": {
+        "name": "list_papers",
+        "description": "List all existing papers available as resources"
+      },
+      "read_paper": {
+        "name": "read_paper",
+        "description": "Read the full content of a stored paper in markdown format"
+      }
+    }
   },
   "local-code-search": {
     "category": "search-data-extraction",
@@ -15811,7 +17862,30 @@
   },
   "ddg-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/ddg-mcp.json"
+    "path": "search-data-extraction/ddg-mcp.json",
+    "validated": true,
+    "tools": {
+      "ddg-text-search": {
+        "name": "ddg-text-search",
+        "description": "Search the web for text results using DuckDuckGo"
+      },
+      "ddg-image-search": {
+        "name": "ddg-image-search",
+        "description": "Search the web for images using DuckDuckGo"
+      },
+      "ddg-news-search": {
+        "name": "ddg-news-search",
+        "description": "Search for news articles using DuckDuckGo"
+      },
+      "ddg-video-search": {
+        "name": "ddg-video-search",
+        "description": "Search for videos using DuckDuckGo"
+      },
+      "ddg-ai-chat": {
+        "name": "ddg-ai-chat",
+        "description": "Chat with DuckDuckGo AI"
+      }
+    }
   },
   "imdb": {
     "category": "search-data-extraction",
@@ -15920,7 +17994,50 @@
   },
   "cryo-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/cryo-mcp.json"
+    "path": "search-data-extraction/cryo-mcp.json",
+    "validated": true,
+    "tools": {
+      "list_datasets": {
+        "name": "list_datasets",
+        "description": "Return a list of all available cryo datasets"
+      },
+      "query_dataset": {
+        "name": "query_dataset",
+        "description": "\nDownload blockchain data and return the file paths where the data is stored.\n\nIMPORTANT WORKFLOW NOTE: When running SQL queries, use this function first to download\ndata, then use the returned file paths with query_sql() to execute SQL on those files.\n\nExample workflow for SQL:\n1. First download data: result = query_dataset('transactions', blocks='1000:1010', output_format='parquet')\n2. Get file paths: files = result.get('files', [])\n3. Run SQL query: query_sql(\"SELECT * FROM read_parquet('/path/to/file.parquet')\", files=files)\n\nDATASET-SPECIFIC PARAMETERS:\nFor datasets that require specific address parameters (like 'balances', 'erc20_transfers', etc.),\nALWAYS use the 'contract' parameter to pass ANY Ethereum address. For example:\n\n- For 'balances' dataset: Use contract parameter for the address you want balances for\n  query_dataset('balances', blocks='1000:1010', contract='0x123...')\n\n- For 'logs' or 'erc20_transfers': Use contract parameter for contract address\n  query_dataset('logs', blocks='1000:1010', contract='0x123...')\n\nTo check what parameters a dataset requires, always use lookup_dataset() first:\nlookup_dataset('balances')  # Will show required parameters\n\nArgs:\n    dataset: The name of the dataset to query (e.g., 'logs', 'transactions', 'balances')\n    blocks: Block range specification as a string (e.g., '1000:1010')\n    start_block: Start block number as integer (alternative to blocks)\n    end_block: End block number as integer (alternative to blocks)\n    use_latest: If True, query the latest block\n    blocks_from_latest: Number of blocks before the latest to include (e.g., 10 = latest-10 to latest)\n    contract: Contract address to filter by - IMPORTANT: Use this parameter for ALL address-based filtering\n      regardless of the parameter name in the native cryo command (address, contract, etc.)\n    output_format: Output format (json, csv, parquet) - use 'parquet' for SQL queries\n    include_columns: Columns to include alongside the defaults\n    exclude_columns: Columns to exclude from the defaults\n\nReturns:\n    Dictionary containing file paths where the downloaded data is stored\n"
+      },
+      "lookup_dataset": {
+        "name": "lookup_dataset",
+        "description": "\nLook up a specific dataset and return detailed information about it. IMPORTANT: Always use this\nfunction before querying a new dataset to understand its required parameters and schema.\n\nThe returned information includes:\n1. Required parameters for the dataset (IMPORTANT for datasets like 'balances' that need an address)\n2. Schema details showing available columns and data types\n3. Example queries for the dataset\n\nWhen the dataset requires specific parameters like 'address' (for 'balances'),\nALWAYS use the 'contract' parameter in query_dataset() to pass these values.\n\nExample:\nFor 'balances' dataset, lookup_dataset('balances') will show it requires an 'address' parameter.\nYou should then query it using:\nquery_dataset('balances', blocks='1000:1010', contract='0x1234...')\n\nArgs:\n    name: The name of the dataset to look up\n    sample_start_block: Optional start block for sample data (integer)\n    sample_end_block: Optional end block for sample data (integer)\n    use_latest_sample: If True, use the latest block for sample data\n    sample_blocks_from_latest: Number of blocks before the latest to include in sample\n    \nReturns:\n    Detailed information about the dataset including schema and available fields\n"
+      },
+      "get_transaction_by_hash": {
+        "name": "get_transaction_by_hash",
+        "description": "\nGet detailed information about a transaction by its hash\n\nArgs:\n    tx_hash: The transaction hash to look up\n    \nReturns:\n    Detailed information about the transaction\n"
+      },
+      "get_latest_ethereum_block": {
+        "name": "get_latest_ethereum_block",
+        "description": "\nGet information about the latest Ethereum block\n\nReturns:\n    Information about the latest block including block number\n"
+      },
+      "query_sql": {
+        "name": "query_sql",
+        "description": "\nRun a SQL query against downloaded blockchain data files\n\nIMPORTANT WORKFLOW: This function should be used after calling query_dataset\nto download data. Use the file paths returned by query_dataset as input to this function.\n\nWorkflow steps:\n1. Download data: result = query_dataset('transactions', blocks='1000:1010', output_format='parquet')\n2. Get file paths: files = result.get('files', [])\n3. Execute SQL using either:\n   - Direct table references: query_sql(\"SELECT * FROM transactions\", files=files)\n   - Or read_parquet(): query_sql(\"SELECT * FROM read_parquet('/path/to/file.parquet')\", files=files)\n\nTo see the schema of a file, use get_sql_table_schema(file_path) before writing your query.\n\nDuckDB supports both approaches:\n1. Direct table references (simpler): \"SELECT * FROM blocks\"\n2. read_parquet function (explicit): \"SELECT * FROM read_parquet('/path/to/file.parquet')\"\n\nArgs:\n    query: SQL query to execute - can use simple table names or read_parquet()\n    files: List of parquet file paths to query (typically from query_dataset results)\n    include_schema: Whether to include schema information in the result\n    \nReturns:\n    Query results and metadata\n"
+      },
+      "list_available_sql_tables": {
+        "name": "list_available_sql_tables",
+        "description": "\nList all available parquet files that can be queried with SQL\n\nUSAGE NOTES:\n- This function lists parquet files that have already been downloaded\n- Each file can be queried using read_parquet('/path/to/file.parquet') in your SQL\n- For each file, this returns the file path, dataset type, and other metadata\n- Use these file paths in your SQL queries with query_sql()\n\nReturns:\n    List of available files and their metadata\n"
+      },
+      "get_sql_table_schema": {
+        "name": "get_sql_table_schema",
+        "description": "\nGet the schema and sample data for a specific parquet file\n\nWORKFLOW NOTE: Use this function to explore the structure of parquet files\nbefore writing SQL queries against them. This will show you:\n1. All available columns and their data types\n2. Sample data from the file\n3. Total row count\n\nUsage example:\n1. Get list of files: files = list_available_sql_tables()\n2. For a specific file: schema = get_sql_table_schema(files[0]['path'])\n3. Use columns in your SQL: query_sql(\"SELECT column1, column2 FROM read_parquet('/path/to/file.parquet')\")\n\nArgs:\n    file_path: Path to the parquet file (from list_available_sql_tables or query_dataset)\n    \nReturns:\n    Table schema information including columns, data types, and sample data\n"
+      },
+      "query_blockchain_sql": {
+        "name": "query_blockchain_sql",
+        "description": "\nDownload blockchain data and run SQL query in a single step\n\nCONVENIENCE FUNCTION: This combines query_dataset and query_sql into one call.\n\nYou can write SQL queries using either approach:\n1. Simple table references: \"SELECT * FROM blocks LIMIT 10\"\n2. Explicit read_parquet: \"SELECT * FROM read_parquet('/path/to/file.parquet') LIMIT 10\"\n\nDATASET-SPECIFIC PARAMETERS:\nFor datasets that require specific address parameters (like 'balances', 'erc20_transfers', etc.),\nALWAYS use the 'contract' parameter to pass ANY Ethereum address. For example:\n\n- For 'balances' dataset: Use contract parameter for the address you want balances for\n  query_blockchain_sql(\n      sql_query=\"SELECT * FROM balances\",\n      dataset=\"balances\",\n      blocks='1000:1010',\n      contract='0x123...'  # Address you want balances for\n  )\n\nExamples:\n```\n# Using simple table name\nquery_blockchain_sql(\n    sql_query=\"SELECT * FROM blocks LIMIT 10\",\n    dataset=\"blocks\",\n    blocks_from_latest=100\n)\n\n# Using read_parquet() (the path will be automatically replaced)\nquery_blockchain_sql(\n    sql_query=\"SELECT * FROM read_parquet('/any/path.parquet') LIMIT 10\",\n    dataset=\"blocks\",\n    blocks_from_latest=100\n)\n```\n\nALTERNATIVE WORKFLOW (more control):\nIf you need more control, you can separate the steps:\n1. Download data: result = query_dataset('blocks', blocks_from_latest=100, output_format='parquet')\n2. Inspect schema: schema = get_sql_table_schema(result['files'][0])\n3. Run SQL query: query_sql(\"SELECT * FROM blocks\", files=result['files'])\n\nArgs:\n    sql_query: SQL query to execute - using table names or read_parquet()\n    dataset: The specific dataset to query (e.g., 'transactions', 'logs', 'balances')\n             If None, will be extracted from the SQL query\n    blocks: Block range specification as a string (e.g., '1000:1010')\n    start_block: Start block number (alternative to blocks)\n    end_block: End block number (alternative to blocks)\n    use_latest: If True, query the latest block\n    blocks_from_latest: Number of blocks before the latest to include\n    contract: Contract address to filter by - IMPORTANT: Use this parameter for ALL address-based filtering\n      regardless of the parameter name in the native cryo command (address, contract, etc.)\n    force_refresh: Force download of new data even if it exists\n    include_schema: Include schema information in the result\n    \nReturns:\n    SQL query results and metadata\n"
+      },
+      "get_sql_examples": {
+        "name": "get_sql_examples",
+        "description": "\nGet example SQL queries for different blockchain datasets with DuckDB\n\nSQL WORKFLOW TIPS:\n1. First download data: result = query_dataset('dataset_name', blocks='...', output_format='parquet')\n2. Inspect schema: schema = get_sql_table_schema(result['files'][0])\n3. Run SQL: query_sql(\"SELECT * FROM read_parquet('/path/to/file.parquet')\", files=result['files'])\n\nOR use the combined approach:\n- query_blockchain_sql(sql_query=\"SELECT * FROM read_parquet('...')\", dataset='blocks', blocks='...')\n\nReturns:\n    Dictionary of example queries categorized by dataset type and workflow patterns\n"
+      }
+    }
   },
   "twikit": {
     "category": "search-data-extraction",
@@ -15928,7 +18045,34 @@
   },
   "agora-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/agora-mcp.json"
+    "path": "search-data-extraction/agora-mcp.json",
+    "validated": true,
+    "tools": {
+      "agora_search": {
+        "name": "agora_search",
+        "description": "\nSearch for products matching the query in Agora.\n\nArgs:\n    q: The search query.\n    count: The number of products to return per page.\n    page: The page number.\n    price_min: The minimum price. Optional\n    price_max: The maximum price. Optional\n    sort: The sort field: price:relevance.\n    order: The sort order: asc or desc.\n    \nReturns:\n    The search results.\n"
+      },
+      "agora_get_product_detail": {
+        "name": "agora_get_product_detail",
+        "description": "\nGet details for a specific product in Agora.\n\nArgs:\n    slug: The product slug, it usually looks something like 'royal-blue-waxed-shoe-laces-6f2049ef-0d08-4a79-8937-025bb596092f-1718242165922'\n    \nReturns:\n    The product details.\n"
+      },
+      "agora_get_payment_offers": {
+        "name": "agora_get_payment_offers",
+        "description": "\nGet the payment offers for a product in Agora. Some products do not have variants, in such cases use the product_id as variant_id too.\nBefore calling this tool, check if the user has already provided the shipping address and user information. \nOtherwise, ask the user for the shipping address and user information.\n\nIf the user does not provide an `addressName`, use the `firstname` and `lastname` to populate it.\nArgs:\n    slug: The product slug.\n    product_id: The product ID as str delimited by escaped double quotes\n    variant_id: The product variant ID as str delimited by escaped double quotes\n    quantity: The quantity to purchase.\n    shipping_address: The shipping address.\n    user: The user information.\n    \nExample:\n    product_id = \"\\\"1234567890\\\"\"\n    variant_id = \"\\\"1234567890\\\"\"\n    shipping_address = {\n        \"addressName\": \"John Doe\",\n        \"addressFirst\": \"123 Main St\",\n        \"city\": \"New York\",\n        \"state\": \"NY\",\n        \"country\": \"US\",\n        \"zipCode\": \"10001\"\n    }\n    \n    user = {\n        \"firstname\": \"John\",\n        \"lastname\": \"Doe\",\n        \"email\": \"john@example.com\",\n    }\n    \nReturns:\n    L402 offer that can be paid by L402-compatible clients.\n"
+      },
+      "agora_get_order": {
+        "name": "agora_get_order",
+        "description": "\nGet details for a specific order in Agora.\n\nArgs:\n    order_id: The order ID.\n    \nReturns:\n    The order details.\n"
+      },
+      "agora_get_user_orders": {
+        "name": "agora_get_user_orders",
+        "description": "\nGet all orders for the current user.\n\nReturns:\n    A list of orders.\n"
+      },
+      "agora_get_user_info": {
+        "name": "agora_get_user_info",
+        "description": "\nGet the current user's profile and shipping addresses in Agora.\n\nReturns:\n    Dict containing user profile info (firstname, lastname, email) and list of shipping addresses\n"
+      }
+    }
   },
   "newsnow-mcp-server": {
     "category": "search-data-extraction",
@@ -16253,7 +18397,18 @@
   },
   "rapidocr-mcp": {
     "category": "search-data-extraction",
-    "path": "search-data-extraction/rapidocr-mcp.json"
+    "path": "search-data-extraction/rapidocr-mcp.json",
+    "validated": true,
+    "tools": {
+      "ocr_by_content": {
+        "name": "ocr_by_content",
+        "description": "Perform OCR recognition on base64 encoded image content.\n\nArgs:\n    base64_data: Base64 encoded image content string\n\nReturns:\n    List[TextContent]: List of recognized text content\n"
+      },
+      "ocr_by_path": {
+        "name": "ocr_by_path",
+        "description": "Perform OCR recognition on an image file.\n\nArgs:\n    path: Path to the image file\n\nReturns:\n    List[TextContent]: List of recognized text content\n"
+      }
+    }
   },
   "jina-ai-web-search": {
     "category": "search-data-extraction",
@@ -17787,7 +19942,74 @@
   },
   "fpl-mcp": {
     "category": "sports",
-    "path": "sports/fpl-mcp.json"
+    "path": "sports/fpl-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_team": {
+        "name": "get_team",
+        "description": "Get any team's players, captain, and other details for a specific gameweek\n\nArgs:\n    team_id: FPL team ID (required)\n    gameweek: Gameweek number (defaults to current gameweek)\n    \nReturns:\n    Detailed team information including player details, captain, and value\n"
+      },
+      "get_my_team": {
+        "name": "get_my_team",
+        "description": "Get your own FPL team for a specific gameweek\n\nArgs:\n    gameweek: Gameweek number (defaults to current gameweek)\n    \nReturns:\n    Detailed team information including player details, captain, and value\n    \nNote:\n    This uses your authenticated team ID from the FPL credentials.\n    To get another team's details, use get_team and provide a team_id.\n"
+      },
+      "get_manager": {
+        "name": "get_manager",
+        "description": "Get detailed information about an FPL manager\n\nArgs:\n    team_id: FPL team ID to look up\n    \nReturns:\n    Manager information including history, name, team details, and leagues\n"
+      },
+      "get_manager_info": {
+        "name": "get_manager_info",
+        "description": "Get detailed information about an FPL manager\n\nArgs:\n    team_id: FPL team ID (defaults to authenticated user)\n\nReturns:\n    Manager info with leagues and performance stats\n"
+      },
+      "get_league_standings": {
+        "name": "get_league_standings",
+        "description": "Get standings for a specified FPL league\n\nArgs:\n    league_id: ID of the league to fetch\n    \nReturns:\n    League information with standings and team details\n"
+      },
+      "get_league_analytics": {
+        "name": "get_league_analytics",
+        "description": "Get rich analytics for a Fantasy Premier League mini-league\n\nReturns visualization-optimized data for various types of league analysis.\n\nArgs:\n    league_id: ID of the league to analyze\n    analysis_type: Type of analysis to perform:\n        - \"overview\": General league overview (default)\n        - \"historical\": Historical performance analysis\n        - \"team_composition\": Team composition analysis\n        - \"decisions\": Captain and transfer decision analysis\n        - \"fixtures\": Fixture difficulty comparison\n    start_gw: Starting gameweek (defaults to 1 or use \"current-N\" format)\n    end_gw: Ending gameweek (defaults to current)\n    \nReturns:\n    Rich analytics data structured for visualization\n"
+      },
+      "get_player_information": {
+        "name": "get_player_information",
+        "description": "Get detailed information and statistics for a specific player\n\nArgs:\n    player_id: FPL player ID (if provided, takes precedence over player_name)\n    player_name: Player name to search for (used if player_id not provided)\n    start_gameweek: Starting gameweek for filtering player history\n    end_gameweek: Ending gameweek for filtering player history\n    include_history: Whether to include gameweek-by-gameweek history\n    include_fixtures: Whether to include upcoming fixtures\n\nReturns:\n    Comprehensive player information including stats and history\n"
+      },
+      "search_fpl_players": {
+        "name": "search_fpl_players",
+        "description": "Search for FPL players by name with optional filtering\n\nArgs:\n    query: Player name or partial name to search for\n    position: Optional position filter (GKP, DEF, MID, FWD)\n    team: Optional team name filter\n    limit: Maximum number of results to return\n\nReturns:\n    List of matching players with details\n"
+      },
+      "check_fpl_authentication": {
+        "name": "check_fpl_authentication",
+        "description": "Check if FPL authentication is working correctly\n\nReturns:\n    Authentication status and basic team information\n"
+      },
+      "get_gameweek_status": {
+        "name": "get_gameweek_status",
+        "description": "Get precise information about current, previous, and next gameweeks\n\nReturns:\n    Detailed information about gameweek timing, including exact status\n"
+      },
+      "analyze_player_fixtures": {
+        "name": "analyze_player_fixtures",
+        "description": "Analyze upcoming fixtures for a player and provide a difficulty rating\n\nArgs:\n    player_name: Player name to search for\n    num_fixtures: Number of upcoming fixtures to analyze (default: 5)\n\nReturns:\n    Analysis of player's upcoming fixtures with difficulty ratings\n"
+      },
+      "get_blank_gameweeks": {
+        "name": "get_blank_gameweeks",
+        "description": "Get information about upcoming blank gameweeks where teams don't have fixtures\n\nArgs:\n    num_gameweeks: Number of upcoming gameweeks to check (default: 5)\n\nReturns:\n    Information about blank gameweeks and affected teams\n"
+      },
+      "get_double_gameweeks": {
+        "name": "get_double_gameweeks",
+        "description": "Get information about upcoming double gameweeks where teams play multiple times\n\nArgs:\n    num_gameweeks: Number of upcoming gameweeks to check (default: 5)\n\nReturns:\n    Information about double gameweeks and affected teams\n"
+      },
+      "analyze_players": {
+        "name": "analyze_players",
+        "description": "Filter and analyze FPL players based on multiple criteria\n\nArgs:\n    position: Player position (e.g., \"midfielders\", \"defenders\")\n    team: Team name filter\n    min_price: Minimum player price in millions\n    max_price: Maximum player price in millions\n    min_points: Minimum total points\n    min_ownership: Minimum ownership percentage\n    max_ownership: Maximum ownership percentage\n    form_threshold: Minimum form rating\n    include_gameweeks: Whether to include gameweek-by-gameweek data\n    num_gameweeks: Number of recent gameweeks to include\n    sort_by: Metric to sort results by (default: total_points)\n    sort_order: Sort direction (\"asc\" or \"desc\")\n    limit: Maximum number of players to return\n    \nReturns:\n    Filtered player data with summary statistics\n"
+      },
+      "analyze_fixtures": {
+        "name": "analyze_fixtures",
+        "description": "Analyze upcoming fixtures for players, teams, or positions\n\nArgs:\n    entity_type: Type of entity to analyze (\"player\", \"team\", or \"position\")\n    entity_name: Name of the specific entity\n    num_gameweeks: Number of gameweeks to look ahead\n    include_blanks: Whether to include blank gameweek info\n    include_doubles: Whether to include double gameweek info\n    \nReturns:\n    Fixture analysis with difficulty ratings and summary\n"
+      },
+      "compare_players": {
+        "name": "compare_players",
+        "description": "Compare multiple players across various metrics\n\nArgs:\n    player_names: List of player names to compare (2-5 players recommended)\n    metrics: List of metrics to compare\n    include_gameweeks: Whether to include gameweek-by-gameweek comparison\n    num_gameweeks: Number of recent gameweeks to include in comparison\n    include_fixture_analysis: Whether to include fixture analysis including blanks and doubles\n    \nReturns:\n    Detailed comparison of players across the specified metrics\n"
+      }
+    }
   },
   "spurs-blog-(pounding-the-rock)": {
     "category": "sports",
@@ -18065,7 +20287,22 @@
   },
   "hh-jira-mcp-server": {
     "category": "support-service-management",
-    "path": "support-service-management/hh-jira-mcp-server.json"
+    "path": "support-service-management/hh-jira-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "search_team_active_portfolios": {
+        "name": "search_team_active_portfolios",
+        "description": ""
+      },
+      "create_task": {
+        "name": "create_task",
+        "description": ""
+      },
+      "set_defence_checked": {
+        "name": "set_defence_checked",
+        "description": ""
+      }
+    }
   },
   "@shortcut/mcp": {
     "category": "support-service-management",
@@ -18571,7 +20808,74 @@
   },
   "devrev-mcp": {
     "category": "support-service-management",
-    "path": "support-service-management/devrev-mcp.json"
+    "path": "support-service-management/devrev-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_current_user": {
+        "name": "get_current_user",
+        "description": "Fetch the current DevRev user details. When the user specifies 'me' in the query, this tool should be called to get the user details."
+      },
+      "get_vista": {
+        "name": "get_vista",
+        "description": "Retrieve information about a vista in DevRev using its ID. In DevRev a vista is a sprint board which contains sprints (or vista group items). The reponse of this tool will contain the sprint (or vista group item) IDs that you can use to filter on sprints."
+      },
+      "search": {
+        "name": "search",
+        "description": "Search DevRev using the provided query"
+      },
+      "get_work": {
+        "name": "get_work",
+        "description": "Get all information about a DevRev work item (issue, ticket) using its ID"
+      },
+      "create_work": {
+        "name": "create_work",
+        "description": "Create a new work item (issue, ticket) in DevRev"
+      },
+      "update_work": {
+        "name": "update_work",
+        "description": "Update an existing work item (issue, ticket) in DevRev"
+      },
+      "list_works": {
+        "name": "list_works",
+        "description": "List all work items (issues, tickets) in DevRev"
+      },
+      "get_part": {
+        "name": "get_part",
+        "description": "Get information about a part (enhancement) in DevRev using its ID"
+      },
+      "create_part": {
+        "name": "create_part",
+        "description": "Create a new part (enhancement) in DevRev"
+      },
+      "update_part": {
+        "name": "update_part",
+        "description": "Update an existing part (enhancement) in DevRev"
+      },
+      "list_parts": {
+        "name": "list_parts",
+        "description": "List all parts (enhancements) in DevRev"
+      },
+      "list_meetings": {
+        "name": "list_meetings",
+        "description": "List meetings in DevRev"
+      },
+      "valid_stage_transition": {
+        "name": "valid_stage_transition",
+        "description": "gets a list of valid stage transition for a given work item (issue, ticket) or part (enhancement). Use this before updating stage of the work item or part to ensure the transition is valid."
+      },
+      "add_timeline_entry": {
+        "name": "add_timeline_entry",
+        "description": "Add a timeline entry to a work item (issue, ticket) or part (enhancement)"
+      },
+      "get_sprints": {
+        "name": "get_sprints",
+        "description": "Get active or planned sprints for a given part ID. Use this to get the sprints for an issue based on its part."
+      },
+      "list_subtypes": {
+        "name": "list_subtypes",
+        "description": "List all subtypes in DevRev for a given leaf type"
+      }
+    }
   },
   "devrev": {
     "category": "support-service-management",
@@ -19064,7 +21368,18 @@
   },
   "caltrain-mcp": {
     "category": "travel-transportation",
-    "path": "travel-transportation/caltrain-mcp.json"
+    "path": "travel-transportation/caltrain-mcp.json",
+    "validated": true,
+    "tools": {
+      "next_trains": {
+        "name": "next_trains",
+        "description": "Return the next few scheduled Caltrain departures.\n\nArgs:\n    origin: Station name (e.g. 'San Jose Diridon', 'Palo Alto', 'San Francisco').\n            Supports common abbreviations like 'SF' for San Francisco, 'SJ' for San Jose.\n            If station is not found, use list_stations() to see all available options.\n    destination: Station name (e.g. 'San Francisco', 'Mountain View', 'Tamien').\n                 Supports common abbreviations like 'SF' for San Francisco, 'SJ' for San Jose.\n                 If station is not found, use list_stations() to see all available options.\n    when_iso: Optional ISO-8601 datetime (local time). Default: now.\n\nNote: If you get a \"Station not found\" error, try using the list_stations() tool first\nto see exact station names, then retry with the correct spelling.\n"
+      },
+      "list_stations": {
+        "name": "list_stations",
+        "description": "List all available Caltrain stations.\n\nThis tool is useful when you need to find the exact station names, especially if\nthe next_trains() tool returns a \"Station not found\" error. Station names are\ncase-insensitive and support some common abbreviations like 'SF' and 'SJ'.\n\nReturns a formatted list of all Caltrain stations that can be used as origin\nor destination in the next_trains() tool.\n"
+      }
+    }
   },
   "georgia-511": {
     "category": "travel-transportation",
@@ -19754,7 +22069,34 @@
   },
   "git-mcp": {
     "category": "version-control",
-    "path": "version-control/git-mcp.json"
+    "path": "version-control/git-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_last_git_tag": {
+        "name": "get_last_git_tag",
+        "description": "Find the last git tag in the repository\n\nArgs:\n    repo_name: Name of the git repository\n\nReturns:\n    Dictionary containing tag version and date\n"
+      },
+      "list_commits_since_last_tag": {
+        "name": "list_commits_since_last_tag",
+        "description": "List commit messages since main HEAD and the last git tag\n\nArgs:\n    repo_name: Name of the git repository\n    max_count: Maximum number of commits to return\n\nReturns:\n    List of dictionaries containing commit hash, author, date, and message\n"
+      },
+      "list_repositories": {
+        "name": "list_repositories",
+        "description": "List all git repositories in the configured path\n\nReturns:\n    List of repository names\n"
+      },
+      "create_git_tag": {
+        "name": "create_git_tag",
+        "description": "Create a new git tag in the repository\n\nArgs:\n    repo_name: Name of the git repository\n    tag_name: Name of the tag to create\n    message: Optional message for annotated tag\n\nReturns:\n    Dictionary containing status and tag information\n"
+      },
+      "push_git_tag": {
+        "name": "push_git_tag",
+        "description": "Push a git tag to the default remote\n\nArgs:\n    repo_name: Name of the git repository\n    tag_name: Name of the tag to push\n\nReturns:\n    Dictionary containing status and information about the operation\n"
+      },
+      "refresh_repository": {
+        "name": "refresh_repository",
+        "description": "Refresh repository by checking out main branch and pulling all remotes\n\nArgs:\n    repo_name: Name of the git repository\n\nReturns:\n    Dictionary containing status and information about the operation\n"
+      }
+    }
   },
   "git-pr-description-generator": {
     "category": "version-control",
@@ -19797,7 +22139,14 @@
   },
   "mcp-server-diff-python": {
     "category": "version-control",
-    "path": "version-control/mcp-server-diff-python.json"
+    "path": "version-control/mcp-server-diff-python.json",
+    "validated": true,
+    "tools": {
+      "get-unified-diff": {
+        "name": "get-unified-diff",
+        "description": "Get the difference between two text articles in Unified diff format. Use this when you want to extract the difference between texts."
+      }
+    }
   },
   "git": {
     "category": "version-control",
@@ -20304,7 +22653,42 @@
   },
   "rqbit-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/rqbit-mcp.json"
+    "path": "other-tools-and-integrations/rqbit-mcp.json",
+    "validated": true,
+    "tools": {
+      "list_torrents": {
+        "name": "list_torrents",
+        "description": "List all torrents."
+      },
+      "download_torrent": {
+        "name": "download_torrent",
+        "description": "Download a torrent from a magnet link, HTTP URL, or local file."
+      },
+      "get_torrent_details": {
+        "name": "get_torrent_details",
+        "description": "Get details for a specific torrent by its ID or infohash."
+      },
+      "get_torrent_stats": {
+        "name": "get_torrent_stats",
+        "description": "Get stats and status for a specific torrent by its ID or infohash."
+      },
+      "delete_torrent": {
+        "name": "delete_torrent",
+        "description": "Delete a torrent and its files."
+      },
+      "start_torrent": {
+        "name": "start_torrent",
+        "description": "Start (resume) a torrent."
+      },
+      "pause_torrent": {
+        "name": "pause_torrent",
+        "description": "Pause a torrent."
+      },
+      "forget_torrent": {
+        "name": "forget_torrent",
+        "description": "Forget a torrent, keeping the files."
+      }
+    }
   },
   "openscad-3d-model-generator": {
     "category": "other-tools-and-integrations",
@@ -20414,7 +22798,74 @@
   },
   "imagesorcery-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/imagesorcery-mcp.json"
+    "path": "other-tools-and-integrations/imagesorcery-mcp.json",
+    "validated": true,
+    "tools": {
+      "blur": {
+        "name": "blur",
+        "description": "\nBlur specified rectangular or polygonal areas of an image using OpenCV.\n\nThis tool allows blurring multiple rectangular or polygonal areas of an image with customizable\nblur strength. Each area can be a rectangle defined by a bounding box \n[x1, y1, x2, y2] or a polygon defined by a list of points.\n\nThe blur_strength parameter controls the intensity of the blur effect. Higher values\nresult in stronger blur. It must be an odd number (default is 15).\n\nIf `invert_areas` is True, the tool will blur everything EXCEPT the specified areas.\nReturns:\n    Path to the image with blurred areas\n"
+      },
+      "change_color": {
+        "name": "change_color",
+        "description": "\nChange the color palette of an image.\n\nThis tool applies a predefined color transformation to an image.\nCurrently supported palettes are 'grayscale' and 'sepia'.\n\nReturns:\n    Path to the image with the new color palette.\n"
+      },
+      "crop": {
+        "name": "crop",
+        "description": "\nCrop an image using OpenCV's NumPy slicing approach\nwith OpenMCP's bounding box annotations.\n\nReturns:\n    Path to the cropped image\n"
+      },
+      "detect": {
+        "name": "detect",
+        "description": "\nDetect objects in an image using models from Ultralytics.\n\nThis tool requires pre-downloaded models. Use the download-yolo-models\ncommand to download models before using this tool.\n\nIf objects aren't common, consider using a specialized model.\n\nThis tool can optionally return segmentation masks or polygons if a segmentation\nmodel (e.g., one ending in '-seg.pt') is used.\n\nReturns:\n    Dictionary containing the input image path and a list of detected objects.\n    Each object includes its class name, confidence score, and bounding box.\n    If return_geometry is True, it also includes a 'mask' (numpy array) or\n    'polygon' (list of points).\n"
+      },
+      "draw_arrows": {
+        "name": "draw_arrows",
+        "description": "\nDraw arrows on an image using OpenCV.\n\nThis tool allows adding multiple arrows to an image with customizable\nstart and end points, color, thickness, and tip length.\n\nEach arrow is defined by its start point (x1, y1) and end point (x2, y2).\nThe 'tip_length' is relative to the arrow's length (e.g., 0.1 means 10%).\n\nReturns:\n    Path to the image with drawn arrows\n"
+      },
+      "draw_circles": {
+        "name": "draw_circles",
+        "description": "\nDraw circles on an image using OpenCV.\n\nThis tool allows adding multiple circles to an image with customizable\ncenter, radius, color, thickness, and fill option.\n\nEach circle is defined by its center coordinates (center_x, center_y) and radius.\n\nReturns:\n    Path to the image with drawn circles\n"
+      },
+      "draw_lines": {
+        "name": "draw_lines",
+        "description": "\nDraw lines on an image using OpenCV.\n\nThis tool allows adding multiple lines to an image with customizable\nstart and end points, color, and thickness.\n\nEach line is defined by its start point (x1, y1) and end point (x2, y2).\n\nReturns:\n    Path to the image with drawn lines\n"
+      },
+      "draw_rectangles": {
+        "name": "draw_rectangles",
+        "description": "\nDraw rectangles on an image using OpenCV.\n\nThis tool allows adding multiple rectangles to an image with customizable\nposition, color, thickness, and fill option.\n\nEach rectangle is defined by two points: (x1, y1) for the top-left corner\nand (x2, y2) for the bottom-right corner.\n\nReturns:\n    Path to the image with drawn rectangles\n"
+      },
+      "draw_texts": {
+        "name": "draw_texts",
+        "description": "\nDraw text on an image using OpenCV.\n\nThis tool allows adding multiple text elements to an image with customizable\nposition, font, size, color, and thickness.\n\nAvailable font_face options:\n- 'FONT_HERSHEY_SIMPLEX' (default)\n- 'FONT_HERSHEY_PLAIN'\n- 'FONT_HERSHEY_DUPLEX'\n- 'FONT_HERSHEY_COMPLEX'\n- 'FONT_HERSHEY_TRIPLEX'\n- 'FONT_HERSHEY_COMPLEX_SMALL'\n- 'FONT_HERSHEY_SCRIPT_SIMPLEX'\n- 'FONT_HERSHEY_SCRIPT_COMPLEX'\n\nReturns:\n    Path to the image with drawn text\n"
+      },
+      "fill": {
+        "name": "fill",
+        "description": "\nFill specified rectangular or polygonal areas of an image with a color and opacity.\n\nThis tool allows filling multiple areas of an image with a customizable\ncolor and opacity. Each area can be a rectangle defined by a bounding box \n[x1, y1, x2, y2] or a polygon defined by a list of points.\n\nThe 'opacity' parameter controls the transparency of the fill. 1.0 is fully opaque,\n0.0 is fully transparent. Default is 0.5.\nThe 'color' is in BGR format, e.g., [255, 0, 0] for blue. Default is black.\n\nIf the `color` is set to `None`, the specified area will be made fully transparent,\neffectively deleting it (similar to ImageMagick). In this case, the `opacity`\nparameter is ignored.\n\nIf `invert_areas` is True, the tool will fill everything EXCEPT the specified areas.\nReturns:\n    Path to the image with filled areas\n"
+      },
+      "find": {
+        "name": "find",
+        "description": "\nFind objects in an image based on a text description.\n\nThis tool uses open-vocabulary detection models to find objects matching a text description.\nIt requires pre-downloaded YOLOE models that support text prompts (e.g. yoloe-11l-seg.pt).\n\nThis tool can optionally return segmentation masks or polygons.\n\nReturns:\n    Dictionary containing the input image path and a list of found objects.\n    Each object includes its confidence score and bounding box. If return_geometry\n    is True, it also includes a 'mask' (numpy array) or 'polygon' (list of points).\n"
+      },
+      "get_metainfo": {
+        "name": "get_metainfo",
+        "description": "\nGet metadata information about an image file.\n\nReturns:\n    Dictionary containing metadata about the image (size, dimensions,\n    format, etc.)\n"
+      },
+      "ocr": {
+        "name": "ocr",
+        "description": "\nPerforms Optical Character Recognition (OCR) on an image using EasyOCR.\n\nThis tool extracts text from images in various languages. The default language is English,\nbut you can specify other languages using their language codes (e.g., 'en', 'ru', 'fr', etc.).\n\nReturns:\n    Dictionary containing the input image path and a list of detected text segments\n    with their text content, confidence scores, and bounding box coordinates.\n"
+      },
+      "overlay": {
+        "name": "overlay",
+        "description": "\nOverlays one image on top of another, handling transparency.\n\nThis tool places an overlay image onto a base image at a specified (x, y)\ncoordinate. If the overlay image has an alpha channel (e.g., a transparent PNG),\nit will be blended correctly with the base image. If the overlay extends\nbeyond the boundaries of the base image, it will be cropped.\n\nReturns:\n    Path to the resulting image.\n"
+      },
+      "resize": {
+        "name": "resize",
+        "description": "\nResize an image using OpenCV.\n\nThe function can resize an image in three ways:\n1. By specifying both width and height\n2. By specifying either width or height (preserving aspect ratio)\n3. By specifying a scale factor\n\nReturns:\n    Path to the resized image\n"
+      },
+      "rotate": {
+        "name": "rotate",
+        "description": "\nRotate an image using imutils.rotate_bound function.\n\nThe function rotates the image by the specified angle in degrees.\nPositive angles represent counterclockwise rotation.\nThe rotate_bound function ensures the entire rotated image is visible\nby automatically adjusting the output image size.\n\nReturns:\n    Path to the rotated image\n"
+      }
+    }
   },
   "heybeauty-mcp": {
     "category": "other-tools-and-integrations",
@@ -20769,7 +23220,50 @@
   },
   "mcp-applemusic": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-applemusic.json"
+    "path": "other-tools-and-integrations/mcp-applemusic.json",
+    "validated": true,
+    "tools": {
+      "itunes_play": {
+        "name": "itunes_play",
+        "description": "Start playback in Music (iTunes)."
+      },
+      "itunes_pause": {
+        "name": "itunes_pause",
+        "description": "Pause playback in Music (iTunes)."
+      },
+      "itunes_next": {
+        "name": "itunes_next",
+        "description": "Skip to the next track."
+      },
+      "itunes_previous": {
+        "name": "itunes_previous",
+        "description": "Return to the previous track."
+      },
+      "itunes_search": {
+        "name": "itunes_search",
+        "description": "\nSearch the Music library for tracks whose names contain the given query.\nReturns a list of tracks formatted as \"Track Name - Artist\".\n"
+      },
+      "itunes_play_song": {
+        "name": "itunes_play_song",
+        "description": "\nPlay the first track whose name exactly matches the given song name.\nReturns a confirmation message.\n"
+      },
+      "itunes_create_playlist": {
+        "name": "itunes_create_playlist",
+        "description": "\nCreate a new playlist with the given name and add tracks to it.\n'songs' should be a comma-separated list of exact track names.\nReturns a confirmation message including the number of tracks added.\n"
+      },
+      "itunes_library": {
+        "name": "itunes_library",
+        "description": "\nReturn a summary of the Music library, including total tracks and user playlists.\n"
+      },
+      "itunes_current_song": {
+        "name": "itunes_current_song",
+        "description": "\nGet information about the currently playing track.\nReturns the track name, artist, and album.\n"
+      },
+      "itunes_all_songs": {
+        "name": "itunes_all_songs",
+        "description": "\nGet a list of all songs in the Music library.\nReturns a formatted list of all tracks with their names and artists.\n"
+      }
+    }
   },
   "claude-enhancements": {
     "category": "other-tools-and-integrations",
@@ -21209,7 +23703,14 @@
   },
   "mcp-server-calculator": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-server-calculator.json"
+    "path": "other-tools-and-integrations/mcp-server-calculator.json",
+    "validated": true,
+    "tools": {
+      "calculate": {
+        "name": "calculate",
+        "description": "Calculates/evaluates the given expression."
+      }
+    }
   },
   "sandbox-fusion": {
     "category": "other-tools-and-integrations",
@@ -21280,7 +23781,22 @@
   },
   "haiguitang-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/haiguitang-mcp.json"
+    "path": "other-tools-and-integrations/haiguitang-mcp.json",
+    "validated": true,
+    "tools": {
+      "get_prompt": {
+        "name": "get_prompt",
+        "description": "获取海龟汤游戏的玩法"
+      },
+      "get_puzzle": {
+        "name": "get_puzzle",
+        "description": "获取一个谜题的完整内容\n\nArgs:\n    puzzle_title: 海龟汤的标题\n\nReturns:\n    选择结果信息\n"
+      },
+      "list_puzzles_tool": {
+        "name": "list_puzzles_tool",
+        "description": "列出所有可用的谜题\n\nReturns:\n    谜题列表\n"
+      }
+    }
   },
   "deepseek-thinker-mcp": {
     "category": "other-tools-and-integrations",
@@ -21392,7 +23908,18 @@
   },
   "time-mcp-local": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/time-mcp-local.json"
+    "path": "other-tools-and-integrations/time-mcp-local.json",
+    "validated": true,
+    "tools": {
+      "get_current_time": {
+        "name": "get_current_time",
+        "description": "Get current time in a specific timezones"
+      },
+      "convert_time": {
+        "name": "convert_time",
+        "description": "Convert time between timezones"
+      }
+    }
   },
   "cort-mcp": {
     "category": "other-tools-and-integrations",
@@ -21439,11 +23966,145 @@
   },
   "kroger-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/kroger-mcp.json"
+    "path": "other-tools-and-integrations/kroger-mcp.json",
+    "validated": true,
+    "tools": {
+      "search_locations": {
+        "name": "search_locations",
+        "description": "\nSearch for Kroger store locations near a zip code.\n\nArgs:\n    zip_code: Zip code to search near (uses environment default if not provided)\n    radius_in_miles: Search radius in miles (1-100)\n    limit: Number of results to return (1-200)\n    chain: Filter by specific chain name\n\nReturns:\n    Dictionary containing location search results\n"
+      },
+      "get_location_details": {
+        "name": "get_location_details",
+        "description": "\nGet detailed information about a specific Kroger store location.\n\nArgs:\n    location_id: The unique identifier for the store location\n\nReturns:\n    Dictionary containing detailed location information\n"
+      },
+      "set_preferred_location": {
+        "name": "set_preferred_location",
+        "description": "\nSet a preferred store location for future operations.\n\nArgs:\n    location_id: The unique identifier for the store location\n\nReturns:\n    Dictionary confirming the preferred location has been set\n"
+      },
+      "get_preferred_location": {
+        "name": "get_preferred_location",
+        "description": "\nGet the currently set preferred store location.\n\nReturns:\n    Dictionary containing the preferred location information\n"
+      },
+      "check_location_exists": {
+        "name": "check_location_exists",
+        "description": "\nCheck if a location exists in the Kroger system.\n\nArgs:\n    location_id: The unique identifier for the store location\n\nReturns:\n    Dictionary indicating whether the location exists\n"
+      },
+      "get_product_images": {
+        "name": "get_product_images",
+        "description": "\nGet an image for a specific product from the requested perspective.\n\nUse get_product_details first to see what perspectives are available (typically \"front\", \"back\", \"left\", \"right\").\n\nArgs:\n    product_id: The unique product identifier\n    perspective: The image perspective to retrieve (default: \"front\")\n    location_id: Store location ID (uses preferred if not provided)\n\nReturns:\n    The product image from the requested perspective\n"
+      },
+      "search_products": {
+        "name": "search_products",
+        "description": "\nSearch for products at a Kroger store.\n\nArgs:\n    search_term: Product search term (e.g., \"milk\", \"bread\", \"organic apples\")\n    location_id: Store location ID (uses preferred location if not provided)\n    limit: Number of results to return (1-50)\n    fulfillment: Filter by fulfillment method (csp=curbside pickup, delivery, pickup)\n    brand: Filter by brand name\n\nReturns:\n    Dictionary containing product search results\n"
+      },
+      "get_product_details": {
+        "name": "get_product_details",
+        "description": "\nGet detailed information about a specific product.\n\nArgs:\n    product_id: The unique product identifier\n    location_id: Store location ID for pricing/availability (uses preferred if not provided)\n\nReturns:\n    Dictionary containing detailed product information\n"
+      },
+      "search_products_by_id": {
+        "name": "search_products_by_id",
+        "description": "\nSearch for products by their specific product ID.\n\nArgs:\n    product_id: The product ID to search for\n    location_id: Store location ID (uses preferred location if not provided)\n\nReturns:\n    Dictionary containing matching products\n"
+      },
+      "add_items_to_cart": {
+        "name": "add_items_to_cart",
+        "description": "\nAdd a single item to the user's Kroger cart and track it locally.\n\nIf the user doesn't specifically indicate a preference for pickup or delivery,\nyou should ask them which modality they prefer before calling this tool.\n\nArgs:\n    product_id: The product ID or UPC to add to cart\n    quantity: Quantity to add (default: 1)\n    modality: Fulfillment method - PICKUP or DELIVERY\n\nReturns:\n    Dictionary confirming the item was added to cart\n"
+      },
+      "bulk_add_to_cart": {
+        "name": "bulk_add_to_cart",
+        "description": "\nAdd multiple items to the user's Kroger cart in a single operation.\n\nIf the user doesn't specifically indicate a preference for pickup or delivery,\nyou should ask them which modality they prefer before calling this tool.\n\nArgs:\n    items: List of items to add. Each item should have:\n           - product_id: The product ID or UPC\n           - quantity: Quantity to add (default: 1)\n           - modality: PICKUP or DELIVERY (default: PICKUP)\n\nReturns:\n    Dictionary with results for each item\n"
+      },
+      "view_current_cart": {
+        "name": "view_current_cart",
+        "description": "\nView the current cart contents tracked locally.\n\nNote: This tool can only see items that were added via this MCP server.\nThe Kroger API does not provide permission to query the actual user cart contents.\n\nReturns:\n    Dictionary containing current cart items and summary\n"
+      },
+      "remove_from_cart": {
+        "name": "remove_from_cart",
+        "description": "\nRemove an item from the local cart tracking only.\n\nIMPORTANT: This tool CANNOT remove items from the actual Kroger cart in the app/website.\nIt only updates our local tracking to stay in sync. The user must remove the item from\ntheir actual cart through the Kroger app or website themselves.\n\nUse this tool only when:\n1. The user has already removed an item from their Kroger cart through the app/website\n2. You need to update the local tracking to reflect that change\n\nArgs:\n    product_id: The product ID to remove\n    modality: Specific modality to remove (if None, removes all instances)\n\nReturns:\n    Dictionary confirming the removal from local tracking\n"
+      },
+      "clear_current_cart": {
+        "name": "clear_current_cart",
+        "description": "\nClear all items from the local cart tracking only.\n\nIMPORTANT: This tool CANNOT remove items from the actual Kroger cart in the app/website.\nIt only clears our local tracking. The user must remove items from their actual cart\nthrough the Kroger app or website themselves.\n\nUse this tool only when:\n1. The user has already cleared their Kroger cart through the app/website\n2. You need to update the local tracking to reflect that change\n3. Or when the local tracking is out of sync with the actual cart\n\nReturns:\n    Dictionary confirming the local cart tracking was cleared\n"
+      },
+      "mark_order_placed": {
+        "name": "mark_order_placed",
+        "description": "\nMark the current cart as an order that has been placed and move it to order history.\nUse this after you've completed checkout on the Kroger website/app.\n\nArgs:\n    order_notes: Optional notes about the order\n\nReturns:\n    Dictionary confirming the order was recorded\n"
+      },
+      "view_order_history": {
+        "name": "view_order_history",
+        "description": "\nView the history of placed orders.\n\nNote: This tool can only see orders that were explicitly marked as placed via this MCP server.\nThe Kroger API does not provide permission to query the actual order history from Kroger's systems.\n\nArgs:\n    limit: Number of recent orders to show (1-50)\n\nReturns:\n    Dictionary containing order history\n"
+      },
+      "list_chains": {
+        "name": "list_chains",
+        "description": "\nGet a list of all Kroger-owned chains.\n\nReturns:\n    Dictionary containing chain information\n"
+      },
+      "get_chain_details": {
+        "name": "get_chain_details",
+        "description": "\nGet detailed information about a specific Kroger chain.\n\nArgs:\n    chain_name: Name of the chain to get details for\n\nReturns:\n    Dictionary containing chain details\n"
+      },
+      "check_chain_exists": {
+        "name": "check_chain_exists",
+        "description": "\nCheck if a chain exists in the Kroger system.\n\nArgs:\n    chain_name: Name of the chain to check\n\nReturns:\n    Dictionary indicating whether the chain exists\n"
+      },
+      "list_departments": {
+        "name": "list_departments",
+        "description": "\nGet a list of all available departments in Kroger stores.\n\nReturns:\n    Dictionary containing department information\n"
+      },
+      "get_department_details": {
+        "name": "get_department_details",
+        "description": "\nGet detailed information about a specific department.\n\nArgs:\n    department_id: The unique identifier for the department\n\nReturns:\n    Dictionary containing department details\n"
+      },
+      "check_department_exists": {
+        "name": "check_department_exists",
+        "description": "\nCheck if a department exists in the Kroger system.\n\nArgs:\n    department_id: The department ID to check\n\nReturns:\n    Dictionary indicating whether the department exists\n"
+      },
+      "get_user_profile": {
+        "name": "get_user_profile",
+        "description": "\nGet the authenticated user's Kroger profile information.\n\nReturns:\n    Dictionary containing user profile data\n"
+      },
+      "test_authentication": {
+        "name": "test_authentication",
+        "description": "\nTest if the current authentication token is valid.\n\nReturns:\n    Dictionary indicating authentication status\n"
+      },
+      "get_authentication_info": {
+        "name": "get_authentication_info",
+        "description": "\nGet information about the current authentication state and token.\n\nReturns:\n    Dictionary containing authentication information\n"
+      },
+      "force_reauthenticate": {
+        "name": "force_reauthenticate",
+        "description": "\nForce re-authentication by clearing the current authentication token.\nUse this if you're having authentication issues or need to log in as a different user.\n\nReturns:\n    Dictionary indicating the re-authentication was initiated\n"
+      },
+      "get_current_datetime": {
+        "name": "get_current_datetime",
+        "description": "\nGet the current system date and time.\n\nThis tool is useful for comparing with cart checkout dates, order history,\nor any other time-sensitive operations.\n\nReturns:\n    Dictionary containing current date and time information\n"
+      },
+      "start_authentication": {
+        "name": "start_authentication",
+        "description": "\nStart the OAuth authentication flow with Kroger.\n\nThis tool returns a URL that the user needs to open in their browser\nto authenticate with Kroger. After authorization, the user will be\nredirected to a callback URL that they need to copy and paste back.\n\nReturns:\n    Dictionary with authorization URL and instructions\n"
+      },
+      "complete_authentication": {
+        "name": "complete_authentication",
+        "description": "\nComplete the OAuth flow using the redirect URL from Kroger.\n\nAfter opening the auth URL in your browser and authorizing the app,\nyou'll be redirected to a callback URL. Copy that entire URL and\npass it to this tool to complete the authentication process.\n\nArgs:\n    redirect_url: The full URL from your browser after authorization\n    \nReturns:\n    Dictionary indicating authentication status\n"
+      }
+    }
   },
   "awslabs.aws-documentation-mcp-server": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/awslabs-aws-documentation-mcp-server.json"
+    "path": "other-tools-and-integrations/awslabs-aws-documentation-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "read_documentation": {
+        "name": "read_documentation",
+        "description": "Fetch and convert an AWS documentation page to markdown format.\n\n## Usage\n\nThis tool retrieves the content of an AWS documentation page and converts it to markdown format.\nFor long documents, you can make multiple calls with different start_index values to retrieve\nthe entire content in chunks.\n\n## URL Requirements\n\n- Must be from the docs.aws.amazon.com domain\n- Must end with .html\n\n## Example URLs\n\n- https://docs.aws.amazon.com/AmazonS3/latest/userguide/bucketnamingrules.html\n- https://docs.aws.amazon.com/lambda/latest/dg/lambda-invocation.html\n\n## Output Format\n\nThe output is formatted as markdown text with:\n- Preserved headings and structure\n- Code blocks for examples\n- Lists and tables converted to markdown format\n\n## Handling Long Documents\n\nIf the response indicates the document was truncated, you have several options:\n\n1. **Continue Reading**: Make another call with start_index set to the end of the previous response\n2. **Stop Early**: For very long documents (>30,000 characters), if you've already found the specific information needed, you can stop reading\n\nArgs:\n    ctx: MCP context for logging and error handling\n    url: URL of the AWS documentation page to read\n    max_length: Maximum number of characters to return\n    start_index: On return output starting at this character index\n\nReturns:\n    Markdown content of the AWS documentation\n"
+      },
+      "search_documentation": {
+        "name": "search_documentation",
+        "description": "Search AWS documentation using the official AWS Documentation Search API.\n\n## Usage\n\nThis tool searches across all AWS documentation for pages matching your search phrase.\nUse it to find relevant documentation when you don't have a specific URL.\n\n## Search Tips\n\n- Use specific technical terms rather than general phrases\n- Include service names to narrow results (e.g., \"S3 bucket versioning\" instead of just \"versioning\")\n- Use quotes for exact phrase matching (e.g., \"AWS Lambda function URLs\")\n- Include abbreviations and alternative terms to improve results\n\n## Result Interpretation\n\nEach result includes:\n- rank_order: The relevance ranking (lower is more relevant)\n- url: The documentation page URL\n- title: The page title\n- context: A brief excerpt or summary (if available)\n\nArgs:\n    ctx: MCP context for logging and error handling\n    search_phrase: Search phrase to use\n    limit: Maximum number of results to return\n\nReturns:\n    List of search results with URLs, titles, and context snippets\n"
+      },
+      "recommend": {
+        "name": "recommend",
+        "description": "Get content recommendations for an AWS documentation page.\n\n## Usage\n\nThis tool provides recommendations for related AWS documentation pages based on a given URL.\nUse it to discover additional relevant content that might not appear in search results.\n\n## Recommendation Types\n\nThe recommendations include four categories:\n\n1. **Highly Rated**: Popular pages within the same AWS service\n2. **New**: Recently added pages within the same AWS service - useful for finding newly released features\n3. **Similar**: Pages covering similar topics to the current page\n4. **Journey**: Pages commonly viewed next by other users\n\n## When to Use\n\n- After reading a documentation page to find related content\n- When exploring a new AWS service to discover important pages\n- To find alternative explanations of complex concepts\n- To discover the most popular pages for a service\n- To find newly released information by using a service's welcome page URL and checking the **New** recommendations\n\n## Finding New Features\n\nTo find newly released information about a service:\n1. Find any page belong to that service, typically you can try the welcome page\n2. Call this tool with that URL\n3. Look specifically at the **New** recommendation type in the results\n\n## Result Interpretation\n\nEach recommendation includes:\n- url: The documentation page URL\n- title: The page title\n- context: A brief description (if available)\n\nArgs:\n    ctx: MCP context for logging and error handling\n    url: URL of the AWS documentation page to get recommendations for\n\nReturns:\n    List of recommended pages with URLs, titles, and context\n"
+      }
+    }
   },
   "registry": {
     "category": "other-tools-and-integrations",
@@ -21473,7 +24134,14 @@
   },
   "think_mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/think_mcp.json"
+    "path": "other-tools-and-integrations/think_mcp.json",
+    "validated": true,
+    "tools": {
+      "think": {
+        "name": "think",
+        "description": "Use the tool to think about something. It will not obtain new information or change the database, \nbut just append the thought to the log. Use it when complex reasoning or some cache memory is needed.\n    "
+      }
+    }
   },
   "@thomaswawra/server-spotify": {
     "category": "other-tools-and-integrations",
@@ -21821,7 +24489,26 @@
   },
   "mcp-think-tool": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-think-tool.json"
+    "path": "other-tools-and-integrations/mcp-think-tool.json",
+    "validated": true,
+    "tools": {
+      "think": {
+        "name": "think",
+        "description": "Use this tool to think about something. It will not obtain new information or change anything, \nbut just append the thought to the log. Use it when complex reasoning or cache memory is needed.\n\nArgs:\n    thought: A thought to think about. This can be structured reasoning, step-by-step analysis,\n            policy verification, or any other mental process that helps with problem-solving.\n"
+      },
+      "get_thoughts": {
+        "name": "get_thoughts",
+        "description": "Retrieve all thoughts recorded in the current session.\n\nThis tool helps review the thinking process that has occurred so far.\n"
+      },
+      "clear_thoughts": {
+        "name": "clear_thoughts",
+        "description": "Clear all recorded thoughts from the current session.\n\nUse this to start fresh if the thinking process needs to be reset.\n"
+      },
+      "get_thought_stats": {
+        "name": "get_thought_stats",
+        "description": "Get statistics about the thoughts recorded in the current session."
+      }
+    }
   },
   "spotify-mcp": {
     "category": "other-tools-and-integrations",
@@ -22272,7 +24959,22 @@
   },
   "casual-mcp-server-words": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/casual-mcp-server-words.json"
+    "path": "other-tools-and-integrations/casual-mcp-server-words.json",
+    "validated": true,
+    "tools": {
+      "define": {
+        "name": "define",
+        "description": "Get the definition(s) of an English word."
+      },
+      "example_usage": {
+        "name": "example_usage",
+        "description": "Get example usage of a word, if available."
+      },
+      "synonyms": {
+        "name": "synonyms",
+        "description": "Get synonyms for a word, if available."
+      }
+    }
   },
   "mochi-flashcards": {
     "category": "other-tools-and-integrations",
@@ -22286,7 +24988,18 @@
   },
   "mcp-slicer": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-slicer.json"
+    "path": "other-tools-and-integrations/mcp-slicer.json",
+    "validated": true,
+    "tools": {
+      "list_nodes": {
+        "name": "list_nodes",
+        "description": "\nList MRML nodes via the Slicer Web Server API.\n\nThe filter_type parameter specifies the type of node information to retrieve.\nPossible values include \"names\" (node names), \"ids\" (node IDs), and \"properties\" (node properties).\nThe default value is \"names\".\n\nThe class_name, name, and id parameters are optional and can be used to further filter nodes.\nThe class_name parameter allows filtering nodes by class name.\nThe name parameter allows filtering nodes by name.\nThe id parameter allows filtering nodes by ID.\n\nExamples:\n- List the names of all nodes: {\"tool\": \"list_nodes\", \"arguments\": {\"filter_type\": \"names\"}}\n- List the IDs of nodes of a specific class: {\"tool\": \"list_nodes\", \"arguments\": {\"filter_type\": \"ids\", \"class_name\": \"vtkMRMLModelNode\"}}\n- List the properties of nodes with a specific name: {\"tool\": \"list_nodes\", \"arguments\": {\"filter_type\": \"properties\", \"name\": \"MyModel\"}}\n- List nodes with a specific ID: {\"tool\": \"list_nodes\", \"arguments\": {\"filter_type\": \"ids\", \"id\": \"vtkMRMLModelNode123\"}}\n\nReturns a dictionary containing node information.\nIf filter_type is \"names\" or \"ids\", the returned dictionary contains a \"nodes\" key, whose value is a list containing node names or IDs.\nExample: {\"nodes\": [\"node1\", \"node2\", ...]} or {\"nodes\": [\"id1\", \"id2\", ...]}\nIf filter_type is \"properties\", the returned dictionary contains a \"nodes\" key, whose value is a dictionary containing node properties.\nExample: {\"nodes\": {\"node1\": {\"property1\": \"value1\", \"property2\": \"value2\"}, ...}}\nIf an error occurs, a dictionary containing an \"error\" key is returned, whose value is a string describing the error.\n"
+      },
+      "execute_python_code": {
+        "name": "execute_python_code",
+        "description": "\nExecute Python code in 3D Slicer.\n\nParameters:\ncode (str): The Python code to execute.\n\nThe code parameter is a string containing the Python code to be executed in 3D Slicer's Python environment.\nThe code should be executable by Python's `exec()` function. To get return values, the code should assign the result to a variable named `__execResult`.\n\nExamples:\n- Create a sphere model: {\"tool\": \"execute_python_code\", \"arguments\": {\"code\": \"sphere = slicer.vtkMRMLModelNode(); slicer.mrmlScene.AddNode(sphere); sphere.SetName('MySphere'); __execResult = sphere.GetID()\"}}\n- Get the number of nodes in the current scene: {\"tool\": \"execute_python_code\", \"arguments\": {\"code\": \"__execResult = len(slicer.mrmlScene.GetNodes())\"}}\n- Calculate 1+1: {\"tool\": \"execute_python_code\", \"arguments\": {\"code\": \"__execResult = 1 + 1\"}}\n\nReturns:\n    dict: A dictionary containing the execution result.\n\n    If the code execution is successful, the dictionary will contain the following key-value pairs:\n    - \"success\": True\n    - \"message\": The result of the code execution. If the code assigns the result to `__execResult`, the value of `__execResult` is returned, otherwise it returns empty.\n\n    If the code execution fails, the dictionary will contain the following key-value pairs:\n    - \"success\": False\n    - \"message\": A string containing an error message indicating the cause of the failure. The error message may come from the Slicer Web Server or the Python interpreter.\n\nExamples:\n- Successful execution: {\"success\": True, \"message\": 2}  # Assuming the result of 1+1 is 2\n- Successful execution: {\"success\": True, \"message\": \"vtkMRMLScene1\"} # Assuming the created sphere id is vtkMRMLScene1\n- Python execution error: {\"success\": False, \"message\": \"Server error: name 'slicer' is not defined\"}\n- Connection error: {\"success\": False, \"message\": \"Connection error: ...\"}\n- HTTP error: {\"success\": False, \"message\": \"HTTP Error 404: Not Found\"}\n"
+      }
+    }
   },
   "tmf620-product-catalog-management": {
     "category": "other-tools-and-integrations",
@@ -22390,7 +25103,86 @@
   },
   "owl-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/owl-mcp.json"
+    "path": "other-tools-and-integrations/owl-mcp.json",
+    "validated": true,
+    "tools": {
+      "add_axiom": {
+        "name": "add_axiom",
+        "description": "\nAdd an axiom to the ontology using OWL functional syntax.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    axiom_str: String representation of the axiom in OWL functional syntax\n             e.g., \"SubClassOf(:Dog :Animal)\"\n\nReturns:\n    str: Success message or error\n"
+      },
+      "add_axioms": {
+        "name": "add_axioms",
+        "description": "\nAdds a list of axioms to the ontology, using OWL functional syntax.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    axiom_strs: List of string representation of the axiom in OWL functional syntax\n             e.g., [\"SubClassOf(:Dog :Animal)\", ...]\n\nReturns:\n    str: Success message or error\n"
+      },
+      "remove_axiom": {
+        "name": "remove_axiom",
+        "description": "\nRemove an axiom from the ontology using OWL functional syntax.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    axiom_str: String representation of the axiom in OWL functional syntax\n\nReturns:\n    str: Success message or error\n"
+      },
+      "find_axioms": {
+        "name": "find_axioms",
+        "description": "\nFind axioms matching a pattern in the ontology.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    pattern: A string pattern to match against axiom strings\n            (simple substring matching)\n    limit: (int) Maximum number of axioms to return (default: 100)\n    include_labels: If True, include human-readable labels after ## in the output\n    annotation_property: Optional annotation property IRI to use for labels \n                        (defaults to rdfs:label)\n\nReturns:\n    list[str]: List of matching axiom strings\n"
+      },
+      "get_all_axioms": {
+        "name": "get_all_axioms",
+        "description": "\nGet all axioms in the ontology as strings.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    limit: Maximum number of axioms to return (default: 100)\n    include_labels: If True, include human-readable labels after ## in the output\n    annotation_property: Optional annotation property IRI to use for labels \n                        (defaults to rdfs:label)\n\nReturns:\n    list[str]: List of all axiom strings\n"
+      },
+      "add_prefix": {
+        "name": "add_prefix",
+        "description": "\nAdd a prefix mapping to the ontology.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    prefix: The prefix string (e.g., \"ex\")\n    uri: The URI the prefix maps to (e.g., \"http://example.org/\")\n\nNote that usually an ontology will contain standard prefixes for rdf, rdfs, owl, xsd\n\nReturns:\n    str: Success message\n"
+      },
+      "ontology_metadata": {
+        "name": "ontology_metadata",
+        "description": "\nGet metadata about the ontology.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n\nReturns:\n    list[str]: List of metadata items\n"
+      },
+      "list_configured_ontologies": {
+        "name": "list_configured_ontologies",
+        "description": "\nList all ontologies defined in the configuration.\n\nReturns:\n    List[OntologyConfigInfo]: List of configured ontologies\n"
+      },
+      "configure_ontology": {
+        "name": "configure_ontology",
+        "description": "\nAdd or update an ontology in the configuration.\n\nArgs:\n    name: A unique name for the ontology\n    path: Absolute path to the ontology file\n    metadata_axioms: List of metadata axioms as strings\n    readonly: Whether the ontology is read-only (default: False)\n    description: Optional description\n    preferred_serialization: Optional preferred serialization format\n    annotation_property: Optional annotation property IRI for labels (default: rdfs:label)\n\nReturns:\n    str: Success or error message\n"
+      },
+      "remove_ontology_config": {
+        "name": "remove_ontology_config",
+        "description": "\nRemove an ontology from the configuration.\n\nArgs:\n    name: Name of the ontology to remove\n\nReturns:\n    str: Success or error message\n"
+      },
+      "get_ontology_config": {
+        "name": "get_ontology_config",
+        "description": "\nGet configuration for a specific ontology.\n\nArgs:\n    name: Name of the ontology\n\nReturns:\n    Optional[OntologyConfigInfo]: The ontology configuration or None if not found\n"
+      },
+      "register_ontology_in_config": {
+        "name": "register_ontology_in_config",
+        "description": "\nRegister an existing ontology in the configuration system.\n\nThis allows you to save preferences and metadata for frequently used ontologies,\nmaking them accessible by name in future sessions.\n\nArgs:\n    owl_file_path: Absolute path to the ontology file\n    name: Optional custom name for the ontology (defaults to filename without extension)\n    readonly: Whether the ontology should be read-only (defaults to current setting if loaded)\n    description: Optional description for the ontology\n    preferred_serialization: Optional preferred serialization format\n    annotation_property: Optional annotation property IRI for labels (defaults to current setting if loaded)\n\nReturns:\n    str: Name of the registered ontology\n"
+      },
+      "load_and_register_ontology": {
+        "name": "load_and_register_ontology",
+        "description": "\nLoad an ontology and register it in the configuration system in one step.\n\nArgs:\n    owl_file_path: Absolute path to the ontology file\n    name: Optional name for the ontology (defaults to filename stem)\n    readonly: Whether the ontology should be read-only (default: False)\n    create_if_not_exists: If True, create the file if it doesn't exist (default: True)\n    description: Optional description of the ontology\n    preferred_serialization: Optional preferred serialization format\n    metadata_axioms: Optional list of metadata axioms to add to the ontology\n    annotation_property: Optional annotation property IRI for labels (default: rdfs:label)\n    \nReturns:\n    str: Success message\n"
+      },
+      "add_axiom_by_name": {
+        "name": "add_axiom_by_name",
+        "description": "\nAdd an axiom to a configured ontology using its name.\n\nArgs:\n    ontology_name: Name of the ontology as defined in configuration\n    axiom_str: String representation of the axiom in OWL functional syntax\n\nReturns:\n    str: Success message or error\n"
+      },
+      "remove_axiom_by_name": {
+        "name": "remove_axiom_by_name",
+        "description": "\nRemove an axiom from a configured ontology using its name.\n\nArgs:\n    ontology_name: Name of the ontology as defined in configuration\n    axiom_str: String representation of the axiom in OWL functional syntax\n\nReturns:\n    str: Success message or error\n"
+      },
+      "find_axioms_by_name": {
+        "name": "find_axioms_by_name",
+        "description": "\nFind axioms matching a pattern in a configured ontology using its name.\n\nArgs:\n    ontology_name: Name of the ontology as defined in configuration\n    pattern: A string pattern to match against axiom strings\n    limit: Maximum number of axioms to return (default: 100)\n    include_labels: If True, include human-readable labels after ## in the output\n    annotation_property: Optional annotation property IRI to use for labels \n                        (defaults to rdfs:label)\n\nReturns:\n    list[str]: List of matching axiom strings or empty list if ontology not found\n"
+      },
+      "add_prefix_by_name": {
+        "name": "add_prefix_by_name",
+        "description": "\nAdd a prefix mapping to a configured ontology using its name.\n\nArgs:\n    ontology_name: Name of the ontology as defined in configuration\n    prefix: The prefix string (e.g., \"ex:\")\n    uri: The URI the prefix maps to (e.g., \"http://example.org/\")\n\nReturns:\n    str: Success message or error\n"
+      },
+      "get_labels_for_iri": {
+        "name": "get_labels_for_iri",
+        "description": "\nGet all labels for a given IRI.\n\nArgs:\n    owl_file_path: Absolute path to the OWL file\n    iri: The IRI to get labels for (as a string)\n    annotation_property: Optional annotation property IRI to use for labels\n                        (defaults to rdfs:label if None)\n\nReturns:\n    List[str]: List of label strings\n"
+      },
+      "get_labels_for_iri_by_name": {
+        "name": "get_labels_for_iri_by_name",
+        "description": "\nGet all labels for a given IRI in a configured ontology.\n\nArgs:\n    ontology_name: Name of the ontology as defined in configuration\n    iri: The IRI to get labels for (as a string)\n    annotation_property: Optional annotation property IRI to use for labels\n                        (defaults to rdfs:label if None)\n\nReturns:\n    List[str]: List of label strings or empty list if ontology not found\n"
+      }
+    }
   },
   "just-prompt-(multi-llm-provider)": {
     "category": "other-tools-and-integrations",
@@ -22621,7 +25413,22 @@
   },
   "mcp-ollama": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-ollama.json"
+    "path": "other-tools-and-integrations/mcp-ollama.json",
+    "validated": true,
+    "tools": {
+      "list_models": {
+        "name": "list_models",
+        "description": "List all downloaded Ollama models"
+      },
+      "show_model": {
+        "name": "show_model",
+        "description": "Get detailed information about a specific model\n\nArgs:\n    name: Name of the model to show information about\n"
+      },
+      "ask_model": {
+        "name": "ask_model",
+        "description": "Ask a question to a specific Ollama model\n\nArgs:\n    model: Name of the model to use (e.g., 'llama2')\n    question: The question to ask the model\n"
+      }
+    }
   },
   "dust": {
     "category": "other-tools-and-integrations",
@@ -22756,7 +25563,14 @@
   },
   "mcp-timeserver": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-timeserver.json"
+    "path": "other-tools-and-integrations/mcp-timeserver.json",
+    "validated": true,
+    "tools": {
+      "get-current-time": {
+        "name": "get-current-time",
+        "description": "Get the current time in the configured local timezone"
+      }
+    }
   },
   "@ibraheem4/eventbrite-mcp": {
     "category": "other-tools-and-integrations",
@@ -23284,7 +26098,30 @@
   },
   "ygg-torrent-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/ygg-torrent-mcp.json"
+    "path": "other-tools-and-integrations/ygg-torrent-mcp.json",
+    "validated": true,
+    "tools": {
+      "prepare_search_query": {
+        "name": "prepare_search_query",
+        "description": "Always use this tool to prepare a query for `search_torrents`.\nProperly split the user's intention and the actual search query (space-separated keywords) to avoid unfruitful results.\n# Instructions:\n- `user_intent`: Must reflect user's overall intention (e.g., \"last episode of Breaking Bad\", \"season 5 of Breaking Bad\", \"complete series of Breaking Bad\").\n- `search_query`: The actual search terms, consisting of lowercase, space-separated keywords. Do not add generic terms (e.g., \"movie\", \"series\"), common prefixes (e.g., \"the\", \"a\", \"and\"), or extra information (e.g., episode name, resolution, codec). For TV series, use `sXXeYY` for specific episodes (e.g., \"breaking bad s05e16\"), `sXX` for complete seasons (e.g., \"breaking bad s05\") and only the show name for complete series (e.g., \"breaking bad\").\n- For non-French language, if requested, just add 'multi' to the query\n"
+      },
+      "search_torrents": {
+        "name": "search_torrents",
+        "description": "Searches for torrents on YggTorrent using a query (space-separated keywords) and returns a list of torrent results.\n# Instructions:\n- To be called after `prepare_search_query`.\n- Provide **only** `query`, except if user mentions other parameters.\n- Prioritize results using the following hierarchy: is 1080p > smaller file size > is x265 > max seeders+leechers.\n- Recommend up to 3 of the best results, **always** providing filename, file size, seeders/leechers, date, source, and an ultra concise reason.\n- If the search results are too broad, suggest the user provide more specific keywords.\n- Keep recommendations and suggestions concise."
+      },
+      "get_torrent_details": {
+        "name": "get_torrent_details",
+        "description": "Get details from YggTorrent about a specific torrent by id."
+      },
+      "get_magnet_link": {
+        "name": "get_magnet_link",
+        "description": "Get the magnet link from YggTorrent for a specific torrent by id."
+      },
+      "download_torrent_file": {
+        "name": "download_torrent_file",
+        "description": "Download the torrent file from YggTorrent for a specific torrent by id."
+      }
+    }
   },
   "ntlk-mcp-002": {
     "category": "other-tools-and-integrations",
@@ -23351,7 +26188,18 @@
   },
   "interactive-feedback": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/interactive-feedback.json"
+    "path": "other-tools-and-integrations/interactive-feedback.json",
+    "validated": true,
+    "tools": {
+      "interactive_feedback": {
+        "name": "interactive_feedback",
+        "description": "\nRequests user input via GUI after AI displays complete response in chat.\n\nUSAGE FLOW:\n1. AI displays complete response in chat dialog\n2. AI calls this tool to collect user input\n3. Tool returns user feedback only\n\nThis tool collects user input, not for displaying AI responses.\nAI responses must appear in chat dialog before calling this tool.\n\nPARAMETER REQUIREMENTS:\n- AI MUST provide BOTH 'message' and 'full_response' parameters\n- Both parameters cannot be empty or whitespace-only\n- MCP service will automatically select which content to display based on user's display_mode setting\n\nUSAGE PATTERN:\n\n# Step 1: AI displays complete response in chat\n# Step 2: AI calls tool with BOTH parameters\ninteractive_feedback(\n    message=\"你希望我实现这些更改吗？\",  # Required: concise question\n    full_response=\"我分析了你的代码，发现了3个问题...\",  # Required: complete response\n    predefined_options=[\"修复方案A\", \"修复方案B\", \"让我想想\"]\n)\n\nNote: MCP service automatically selects appropriate content based on user's display mode configuration.\n"
+      },
+      "optimize_user_input": {
+        "name": "optimize_user_input",
+        "description": "\n使用配置的 LLM API 来优化或强化用户输入的文本。\n\n此功能可以帮助用户将口语化的、可能存在歧义的输入，转化为更结构化、\n更清晰、更便于 AI 模型理解的文本。\n\nArgs:\n    original_text: 用户的原始输入文本\n    mode: 优化模式\n        - 'optimize': 一键优化，使用预设的通用优化指令\n        - 'reinforce': 提示词强化，使用用户自定义的强化指令\n    reinforcement_prompt: 在 'reinforce' 模式下用户的自定义指令\n\nReturns:\n    str: 优化后的文本或错误信息\n"
+      }
+    }
   },
   "websocket-enhancer": {
     "category": "other-tools-and-integrations",
@@ -23375,7 +26223,42 @@
   },
   "anki-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/anki-mcp.json"
+    "path": "other-tools-and-integrations/anki-mcp.json",
+    "validated": true,
+    "tools": {
+      "add-notes": {
+        "name": "add-notes",
+        "description": "Add one or more notes to Anki"
+      },
+      "check-connection": {
+        "name": "check-connection",
+        "description": "Check connection to Anki"
+      },
+      "list-decks": {
+        "name": "list-decks",
+        "description": "List all available decks in Anki"
+      },
+      "get-cards-reviewed": {
+        "name": "get-cards-reviewed",
+        "description": "Get the number of cards reviewed by day"
+      },
+      "list-models": {
+        "name": "list-models",
+        "description": "List all available note models in Anki"
+      },
+      "get-model-fields": {
+        "name": "get-model-fields",
+        "description": "Get all field names and descriptions for a specific Anki note model"
+      },
+      "find-notes": {
+        "name": "find-notes",
+        "description": "Find notes matching a query in Anki"
+      },
+      "update-notes": {
+        "name": "update-notes",
+        "description": "Update one or more existing notes in Anki"
+      }
+    }
   },
   "agentrpc": {
     "category": "other-tools-and-integrations",
@@ -23401,7 +26284,14 @@
   },
   "mcp-sleep": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-sleep.json"
+    "path": "other-tools-and-integrations/mcp-sleep.json",
+    "validated": true,
+    "tools": {
+      "sleep": {
+        "name": "sleep",
+        "description": "If you need to wait for a few seconds to continue with the task you are performing ."
+      }
+    }
   },
   "sound-effects": {
     "category": "other-tools-and-integrations",
@@ -23554,7 +26444,50 @@
   },
   "sherlock-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/sherlock-mcp.json"
+    "path": "other-tools-and-integrations/sherlock-mcp.json",
+    "validated": true,
+    "tools": {
+      "search": {
+        "name": "search",
+        "description": "\nSearch for available domains matching the query.\nReturns search results with available/unavailable domains, their prices in USD cents, and a search ID needed for purchase requests.\nThe query can be a full domain name with or without the TLD but not subdomains or text.\n\nValid queries: \n    - \"example\"\n    - \"example.com\" \n    - \"my-domain\"\n\nInvalid queries:\n    - \"www.example.com\"  # no subdomains\n    - \"this is a search\" # no spaces\n    - \"sub.domain.com\"   # no subdomains\n"
+      },
+      "claim_account": {
+        "name": "claim_account",
+        "description": "\nLinks an email address to an AI agent's account for web interface access and account recovery.\n\nImportant notes:\n- Only accounts without an existing email can be linked\n- Each email can only be linked to one account\n- This method is rarely needed since emails are also set during domain registration\n"
+      },
+      "set_contact_information": {
+        "name": "set_contact_information",
+        "description": "\nSet the contact information that will be used for domain purchases and ICANN registration.\nContact information must be set before attempting any domain purchases.\n\nAll fields are required:\n    first_name: First name\n    last_name: Last name\n    email: Email address\n    address: Street address\n    city: City\n    state: Two-letter state code for US/Canada (e.g., 'CA', 'NY') or province name (e.g., 'Madrid')\n    postal_code: Postal code\n    country: Two-letter country code ('US', 'ES', 'FR')\n"
+      },
+      "get_contact_information": {
+        "name": "get_contact_information",
+        "description": "\nRetrieve the currently configured contact information that will be used for domain purchases and ICANN registration.\n"
+      },
+      "get_purchase_offers": {
+        "name": "get_purchase_offers",
+        "description": "\nRequest available payment options for a domain.\nThis method returns an L402 offer, which includes details such as offer_id, amount, currency, and more.\nThe returned offer can be processed by any tool supporting L402 offers.\nThe TLD .ai mandates a minimum registration and renewal period of two years. So inform the user that they need to purchase a 2 year package when they request a .ai domain.\n\nThe L402 offer structure:\n{\n    'offers': [\n        {\n            'offer_id': 'example_offer_id',  # String identifier for the offer\n            'amount': 100,                 # Numeric cost value in USD cents\n            'currency': 'usd',             # Currency code\n            'description': 'Example offer', # Text description\n            'title': 'Example Package'      # Title of the package\n        }\n    ],\n    'payment_context_token': 'example_token',  # Payment context token\n    'payment_request_url': 'https://api.example.com/payment-request',  # Payment URL\n    'version': '0.2.2'  # API version\n}\n\nsid: Search ID from a previous search request\ndomain: Domain name to purchase from the search results related to `sid`\n"
+      },
+      "domains": {
+        "name": "domains",
+        "description": "\nList domains owned by the authenticated user.\nEach domain object contains:\n    id (str): Unique domain identifier (domain_id in other methods)\n    domain_name (str): The registered domain name\n    created_at (str): ISO timestamp of domain creation\n    expires_at (str): ISO timestamp of domain expiration\n    auto_renew (bool): Whether domain is set to auto-renew\n    locked (bool): Domain transfer lock status\n    private (bool): WHOIS privacy protection status\n    nameservers (list): List of nameserver hostnames\n    status (str): Domain status (e.g. 'active')\n"
+      },
+      "dns_records": {
+        "name": "dns_records",
+        "description": "\nGet DNS records for a domain.\n\ndomain_id: Domain UUID (e.g: 'd1234567-89ab-cdef-0123-456789abcdef')\nEach DNS record contains:\n    id (str): Unique record identifier\n    type (str): DNS record type (e.g. 'A', 'CNAME', 'MX', 'TXT')\n    name (str): DNS record name\n    value (str): DNS record value\n    ttl (int): Time to live in seconds\n"
+      },
+      "create_dns": {
+        "name": "create_dns",
+        "description": "\nCreate a new DNS record for a domain.\n\ndomain_id: Domain UUID (e.g., 'd1234567-89ab-cdef-0123-456789abcdef')\ntype: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', etc.)\nname: Subdomain or record name (e.g., 'www' creates www.yourdomain.com)\nvalue: Record value (e.g., IP address for A records, domain for CNAME)\nttl: Time To Live in seconds (default: 3600)\n"
+      },
+      "update_dns": {
+        "name": "update_dns",
+        "description": "\nUpdate an existing DNS record for a domain.\n\nNOTE: Updating a record will change its record id.\ndomain_id: Domain UUID (e.g., 'd1234567-89ab-cdef-0123-456789abcdef')\nrecord_id: DNS record UUID to update\ntype: DNS record type ('A', 'AAAA', 'CNAME', 'MX', 'TXT', etc.)\nname: Subdomain or record name (e.g., 'www' for www.yourdomain.com)\nvalue: New record value (e.g., IP address for A records)\nttl: Time To Live in seconds (default: 3600)\n"
+      },
+      "delete_dns": {
+        "name": "delete_dns",
+        "description": "\nDelete a DNS record for a domain.\n\ndomain_id: Domain UUID (e.g., 'd1234567-89ab-cdef-0123-456789abcdef')\nrecord_id: DNS record ID to delete\n"
+      }
+    }
   },
   "grpc-bridge": {
     "category": "other-tools-and-integrations",
@@ -23806,7 +26739,14 @@
   },
   "mcp-datetime": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/mcp-datetime.json"
+    "path": "other-tools-and-integrations/mcp-datetime.json",
+    "validated": true,
+    "tools": {
+      "get_datetime": {
+        "name": "get_datetime",
+        "description": "Get current date and time in various formats"
+      }
+    }
   },
   "needle": {
     "category": "other-tools-and-integrations",
@@ -24058,12 +26998,6 @@
     "validated": false,
     "tools": {}
   },
-  "mixpanel-analytics": {
-    "category": "uncategorized",
-    "path": "uncategorized/mixpanel-analytics.json",
-    "validated": false,
-    "tools": {}
-  },
   "@mshaaban0/contentful-delivery-mcp-server": {
     "category": "uncategorized",
     "path": "uncategorized/mshaaban0-contentful-delivery-mcp-server.json",
@@ -42595,7 +45529,38 @@
   },
   "random-number-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/random-number-mcp.json"
+    "path": "other-tools-and-integrations/random-number-mcp.json",
+    "validated": true,
+    "tools": {
+      "random_int": {
+        "name": "random_int",
+        "description": "Generate a random integer between low and high (inclusive).\n\nArgs:\n    low: Lower bound (inclusive)\n    high: Upper bound (inclusive)\n\nReturns:\n    Random integer between low and high\n"
+      },
+      "random_float": {
+        "name": "random_float",
+        "description": "Generate a random float between low and high.\n\nArgs:\n    low: Lower bound (default 0.0)\n    high: Upper bound (default 1.0)\n\nReturns:\n    Random float between low and high\n"
+      },
+      "random_choices": {
+        "name": "random_choices",
+        "description": "Choose k items from population with replacement, optionally weighted.\n\nArgs:\n    population: List of items to choose from\n    k: Number of items to choose (default 1)\n    weights: Optional weights for each item (default None for equal weights)\n\nReturns:\n    List of k chosen items\n"
+      },
+      "random_shuffle": {
+        "name": "random_shuffle",
+        "description": "Return a new list with items in random order.\n\nArgs:\n    items: List of items to shuffle\n\nReturns:\n    New list with items in random order\n"
+      },
+      "random_sample": {
+        "name": "random_sample",
+        "description": "Choose k unique items from population without replacement.\n\nArgs:\n    population: List of items to choose from\n    k: Number of items to choose\n\nReturns:\n    List of k unique chosen items\n"
+      },
+      "secure_token_hex": {
+        "name": "secure_token_hex",
+        "description": "Generate a secure random hex token.\n\nArgs:\n    nbytes: Number of random bytes to generate (default 32)\n\nReturns:\n    Hex string containing 2*nbytes characters\n"
+      },
+      "secure_random_int": {
+        "name": "secure_random_int",
+        "description": "Generate a secure random integer below upper_bound.\n\nArgs:\n    upper_bound: Upper bound (exclusive)\n\nReturns:\n    Random integer in range [0, upper_bound)\n"
+      }
+    }
   },
   "my-mcp-server": {
     "category": "other-tools-and-integrations",
@@ -43527,7 +46492,14 @@
   },
   "orly-mcp": {
     "category": "other-tools-and-integrations",
-    "path": "other-tools-and-integrations/orly-mcp.json"
+    "path": "other-tools-and-integrations/orly-mcp.json",
+    "validated": true,
+    "tools": {
+      "generate_orly_cover": {
+        "name": "generate_orly_cover",
+        "description": "Generate an O'RLY? book cover image.\n    \n    This tool creates a parody book cover in the style of O'Reilly books with custom title, subtitle, author, and styling options.\n    The generated image will be displayed directly in the chat.\n\n    Args:\n        title (str): The main title for the book cover\n        subtitle (str): The subtitle text (appears at the top)\n        author (str): The author name (appears at the bottom right)\n        image_code (str, optional): Image code 1-40 for the animal/object on the cover. Defaults to random.\n        theme (str, optional): Color theme 0-16. Defaults to random.\n        guide_text_placement (str, optional): Where to place \"guide\" text - 'top_left', 'top_right', 'bottom_left', 'bottom_right'. Defaults to 'bottom_right'.\n        guide_text (str, optional): The guide text to display. Defaults to 'The Definitive Guide' As often as possible, try not to just use \"The Definitive Guide\" but something more creative.\n\n    Returns:\n        Image: The generated O'RLY? book cover image that will be displayed in chat.\n    "
+      }
+    }
   },
   "image-dimensions": {
     "category": "other-tools-and-integrations",
@@ -44108,11 +47080,36 @@
     "validated": false,
     "tools": {}
   },
-  "@mcp-postgres-server": {
+  "mcp-postgres-server": {
     "category": "databases",
     "path": "databases/mcp-postgres-server.json",
-    "validated": false,
-    "tools": {}
+    "validated": true,
+    "tools": {
+      "connect_db": {
+        "name": "connect_db",
+        "description": "Connect to PostgreSQL database. NOTE: Default connection exists - only use when requested or if other commands fail"
+      },
+      "query": {
+        "name": "query",
+        "description": "Execute a SELECT query"
+      },
+      "execute": {
+        "name": "execute",
+        "description": "Execute an INSERT, UPDATE, or DELETE query"
+      },
+      "list_schemas": {
+        "name": "list_schemas",
+        "description": "List all schemas in the database"
+      },
+      "list_tables": {
+        "name": "list_tables",
+        "description": "List tables in the database"
+      },
+      "describe_table": {
+        "name": "describe_table",
+        "description": "Get table structure"
+      }
+    }
   },
   "@mcp-mongodb-atlas": {
     "category": "databases",
@@ -44217,9 +47214,28 @@
       }
     }
   },
-  "mcp_12306": {
+  "train_12306": {
     "category": "travel-transportation",
-    "path": "travel-transportation/py-train-12306.json"
+    "path": "travel-transportation/py-train-12306.json",
+    "validated": true,
+    "tools": {
+      "query_tickets": {
+        "name": "query_tickets",
+        "description": "查询火车票信息，只需要传入出发车站名、到达车站名、出发日期、乘客类型，如: 北京, 汉口, 2025-07-15, ADULT"
+      },
+      "query_train_info": {
+        "name": "query_train_info",
+        "description": "查询火车车次信息，包括时刻表、途径站、停靠时间等信息"
+      },
+      "query_train_price": {
+        "name": "query_train_price",
+        "description": "查询火车的车票价格，需要出发车站名，到达车站名，出发日期"
+      },
+      "get_station_code": {
+        "name": "get_station_code",
+        "description": "获取车站中文名的code(代号/代码)"
+      }
+    }
   },
   "mcp-12306": {
     "category": "travel-transportation",
@@ -44228,5 +47244,315 @@
   "mcp-server-12306": {
     "category": "travel-transportation",
     "path": "travel-transportation/py-12306-mcp-server.json"
+  },
+  "mixpanel-mcp-server": {
+    "category": "uncategorized",
+    "path": "uncategorized/mixpanel-analytics.json",
+    "validated": true,
+    "tools": {
+      "mixpanel_track_event": {
+        "name": "mixpanel_track_event",
+        "description": "Track a custom event in Mixpanel"
+      },
+      "mixpanel_track_pageview": {
+        "name": "mixpanel_track_pageview",
+        "description": "Track a page view event in Mixpanel"
+      },
+      "mixpanel_track_signup": {
+        "name": "mixpanel_track_signup",
+        "description": "Track a signup event and create a user profile in Mixpanel"
+      },
+      "mixpanel_set_user_profile": {
+        "name": "mixpanel_set_user_profile",
+        "description": "Update a user's profile properties in Mixpanel"
+      }
+    }
+  },
+  "discord-mcp": {
+    "category": "communication",
+    "path": "communication/discord-mcp.json",
+    "validated": true,
+    "tools": {
+      "discord_send_message": {
+        "name": "discord_send_message",
+        "description": "Send a message to a Discord channel, optionally with up to 10 files"
+      },
+      "discord_edit_message": {
+        "name": "discord_edit_message",
+        "description": "Edit a previously sent message"
+      },
+      "discord_delete_message": {
+        "name": "discord_delete_message",
+        "description": "Delete a message"
+      },
+      "discord_add_reaction": {
+        "name": "discord_add_reaction",
+        "description": "Add a reaction to a message"
+      },
+      "discord_remove_reaction": {
+        "name": "discord_remove_reaction",
+        "description": "Remove a reaction from a message"
+      },
+      "discord_get_message_history": {
+        "name": "discord_get_message_history",
+        "description": "Get message history from a Discord channel with optional filtering"
+      },
+      "discord_search_messages": {
+        "name": "discord_search_messages",
+        "description": "Search for messages in a Discord channel with text query and filters"
+      },
+      "discord_get_message": {
+        "name": "discord_get_message",
+        "description": "Get a specific message by ID with full attachment details"
+      },
+      "discord_list_attachments": {
+        "name": "discord_list_attachments",
+        "description": "List all attachments in a Discord channel from recent messages"
+      },
+      "discord_download_attachment": {
+        "name": "discord_download_attachment",
+        "description": "Download a Discord attachment and return it as MCP file reference"
+      },
+      "discord_cleanup_download": {
+        "name": "discord_cleanup_download",
+        "description": "Clean up a previously downloaded Discord attachment file"
+      },
+      "discord_get_channel": {
+        "name": "discord_get_channel",
+        "description": "Get information about a Discord channel"
+      },
+      "discord_get_dm_channels": {
+        "name": "discord_get_dm_channels",
+        "description": "Get list of DM channels for the current user"
+      },
+      "discord_create_dm": {
+        "name": "discord_create_dm",
+        "description": "Create or get existing DM channel with a user"
+      },
+      "discord_get_friends": {
+        "name": "discord_get_friends",
+        "description": "Get list of friends for the current user"
+      },
+      "discord_add_friend": {
+        "name": "discord_add_friend",
+        "description": "Send a friend request to a user"
+      },
+      "discord_remove_friend": {
+        "name": "discord_remove_friend",
+        "description": "Remove a friend or cancel a friend request"
+      },
+      "discord_update_presence": {
+        "name": "discord_update_presence",
+        "description": "Update your Discord presence/status"
+      },
+      "discord_clear_presence": {
+        "name": "discord_clear_presence",
+        "description": "Clear your Discord presence/activity"
+      }
+    }
+  },
+  "discord-mcp-server": {
+    "category": "communication",
+    "path": "communication/discord-mcp-server.json",
+    "validated": false,
+    "tools": {}
+  },
+  "mcp-google-analytics": {
+    "category": "data-platforms",
+    "path": "data-platforms/mcp-google-analytics.json",
+    "validated": true,
+    "tools": {
+      "run_report": {
+        "name": "run_report",
+        "description": "\nRun a basic Google Analytics report with specified metrics and dimensions.\n\nArgs:\n    metrics: List of metrics to include (e.g., ['activeUsers', 'sessions'])\n    dimensions: Optional list of dimensions (e.g., ['date', 'deviceCategory'])\n    date_range_start: Start date in YYYY-MM-DD format or NdaysAgo format (default: 7daysAgo)\n    date_range_end: End date in YYYY-MM-DD format or 'today' (default: today)\n    row_limit: Maximum number of rows to return (default: 10)\n"
+      },
+      "get_accounts": {
+        "name": "get_accounts",
+        "description": "\nGet a list of all Google Analytics accounts that the authenticated user has access to.\n"
+      },
+      "get_properties": {
+        "name": "get_properties",
+        "description": "\nGet a list of all properties within a Google Analytics account.\n\nArgs:\n    account_id: The Google Analytics account ID\n"
+      },
+      "get_metadata": {
+        "name": "get_metadata",
+        "description": "\nGet metadata about available metrics and dimensions in Google Analytics.\n"
+      }
+    }
+  },
+  "@toolsdk.ai/google-analytics-mcp": {
+    "category": "marketing",
+    "path": "marketing/google-analytics-mcp-server.json",
+    "validated": false,
+    "tools": {}
+  },
+  "@toolsdk.ai/mixpanel-mcp-server": {
+    "category": "uncategorized",
+    "path": "uncategorized/mixpanel-analytics-toolsdk.json",
+    "validated": true,
+    "tools": {
+      "mixpanel_track_event": {
+        "name": "mixpanel_track_event",
+        "description": "Track a custom event in Mixpanel"
+      },
+      "mixpanel_track_pageview": {
+        "name": "mixpanel_track_pageview",
+        "description": "Track a page view event in Mixpanel"
+      },
+      "mixpanel_track_signup": {
+        "name": "mixpanel_track_signup",
+        "description": "Track a signup event and create a user profile in Mixpanel"
+      },
+      "mixpanel_set_user_profile": {
+        "name": "mixpanel_set_user_profile",
+        "description": "Update a user's profile properties in Mixpanel"
+      }
+    }
+  },
+  "@executeautomation/playwright-mcp-server": {
+    "category": "browser-automation",
+    "path": "browser-automation/playwright-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "start_codegen_session": {
+        "name": "start_codegen_session",
+        "description": "Start a new code generation session to record Playwright actions"
+      },
+      "end_codegen_session": {
+        "name": "end_codegen_session",
+        "description": "End a code generation session and generate the test file"
+      },
+      "get_codegen_session": {
+        "name": "get_codegen_session",
+        "description": "Get information about a code generation session"
+      },
+      "clear_codegen_session": {
+        "name": "clear_codegen_session",
+        "description": "Clear a code generation session without generating a test"
+      },
+      "playwright_navigate": {
+        "name": "playwright_navigate",
+        "description": "Navigate to a URL"
+      },
+      "playwright_screenshot": {
+        "name": "playwright_screenshot",
+        "description": "Take a screenshot of the current page or a specific element"
+      },
+      "playwright_click": {
+        "name": "playwright_click",
+        "description": "Click an element on the page"
+      },
+      "playwright_iframe_click": {
+        "name": "playwright_iframe_click",
+        "description": "Click an element in an iframe on the page"
+      },
+      "playwright_iframe_fill": {
+        "name": "playwright_iframe_fill",
+        "description": "Fill an element in an iframe on the page"
+      },
+      "playwright_fill": {
+        "name": "playwright_fill",
+        "description": "fill out an input field"
+      },
+      "playwright_select": {
+        "name": "playwright_select",
+        "description": "Select an element on the page with Select tag"
+      },
+      "playwright_hover": {
+        "name": "playwright_hover",
+        "description": "Hover an element on the page"
+      },
+      "playwright_upload_file": {
+        "name": "playwright_upload_file",
+        "description": "Upload a file to an input[type='file'] element on the page"
+      },
+      "playwright_evaluate": {
+        "name": "playwright_evaluate",
+        "description": "Execute JavaScript in the browser console"
+      },
+      "playwright_console_logs": {
+        "name": "playwright_console_logs",
+        "description": "Retrieve console logs from the browser with filtering options"
+      },
+      "playwright_close": {
+        "name": "playwright_close",
+        "description": "Close the browser and release all resources"
+      },
+      "playwright_get": {
+        "name": "playwright_get",
+        "description": "Perform an HTTP GET request"
+      },
+      "playwright_post": {
+        "name": "playwright_post",
+        "description": "Perform an HTTP POST request"
+      },
+      "playwright_put": {
+        "name": "playwright_put",
+        "description": "Perform an HTTP PUT request"
+      },
+      "playwright_patch": {
+        "name": "playwright_patch",
+        "description": "Perform an HTTP PATCH request"
+      },
+      "playwright_delete": {
+        "name": "playwright_delete",
+        "description": "Perform an HTTP DELETE request"
+      },
+      "playwright_expect_response": {
+        "name": "playwright_expect_response",
+        "description": "Ask Playwright to start waiting for a HTTP response. This tool initiates the wait operation but does not wait for its completion."
+      },
+      "playwright_assert_response": {
+        "name": "playwright_assert_response",
+        "description": "Wait for and validate a previously initiated HTTP response wait operation."
+      },
+      "playwright_custom_user_agent": {
+        "name": "playwright_custom_user_agent",
+        "description": "Set a custom User Agent for the browser"
+      },
+      "playwright_get_visible_text": {
+        "name": "playwright_get_visible_text",
+        "description": "Get the visible text content of the current page"
+      },
+      "playwright_get_visible_html": {
+        "name": "playwright_get_visible_html",
+        "description": "Get the HTML content of the current page. By default, all <script> tags are removed from the output unless removeScripts is explicitly set to false."
+      },
+      "playwright_go_back": {
+        "name": "playwright_go_back",
+        "description": "Navigate back in browser history"
+      },
+      "playwright_go_forward": {
+        "name": "playwright_go_forward",
+        "description": "Navigate forward in browser history"
+      },
+      "playwright_drag": {
+        "name": "playwright_drag",
+        "description": "Drag an element to a target location"
+      },
+      "playwright_press_key": {
+        "name": "playwright_press_key",
+        "description": "Press a keyboard key"
+      },
+      "playwright_save_as_pdf": {
+        "name": "playwright_save_as_pdf",
+        "description": "Save the current page as a PDF file"
+      },
+      "playwright_click_and_switch_tab": {
+        "name": "playwright_click_and_switch_tab",
+        "description": "Click a link and switch to the newly opened tab"
+      }
+    }
+  },
+  "@mcp-server/google-search-mcp": {
+    "category": "search-data-extraction",
+    "path": "search-data-extraction/google-search-mcp-server.json",
+    "validated": true,
+    "tools": {
+      "search": {
+        "name": "search",
+        "description": ""
+      }
+    }
   }
 }