MCP 服务器

发现优秀的 MCP 服务器

通过 MCP 服务器扩展您的代理能力，拥有 12,252 个能力。

研究与数据1,246

Crawl4AI Web Scraper MCP Server

MCP服务器利用crawl4ai进行网络爬虫，并使用基于LLM的内容提取（Markdown、文本片段、智能提取）。专为AI代理集成而设计。

IoT Realm MCP Server 🌐🔌

🌐🔌 一个 MCP 服务器，它通过模型上下文协议将来自 IoT Realm 设备的实时传感器数据（例如基于 ESP32 的 DHT11 客户端）暴露给 LLM。这使得 AI 代理能够访问、分析和处理实时环境数据。

greptimedb-mcp-server

镜子 (jìng zi)

中国城市天气查询 MCP 服务

MedifinderMCP Server

消息通信协议（MCP）服务器，用于促进系统组件和药品库存数据库之间安全、标准化的通信。提供 RESTful 接口，用于基于位置的药品搜索、可用性查询，以及针对 WhatsApp 集成的优化消息传递。

YouTube Transcript MCP Server

Awesome MCP Servers

一个全面的模型上下文协议 (MCP) 服务器集合，按功能分类。该存储库旨在帮助开发者和人工智能爱好者发现并利用各种可用于不同应用的 MCP 服务器。

Memory MCP 服务器

一键启动 memory mcp，对外提供 SSE 服务。

Fetch MCP Server

MCP 服务器从互联网获取基于 URL 的信息

Model Context Protocol

Okay, here are some resources to help you understand MCPs (presumably referring to Minecraft Protocol) and interact with an MCP server, translated into Chinese: **Understanding the Minecraft Protocol (理解 Minecraft 协议):** * **Wiki.vg (Wiki.vg):** This is the *definitive* resource for the Minecraft protocol. It's highly technical but contains detailed information about packet structures, data types, and the handshake process. * **Chinese Translation:** 虽然 Wiki.vg 主要以英文编写，但它是理解 Minecraft 协议的权威资源。它包含关于数据包结构、数据类型和握手过程的详细信息。 * **Minecraft Protocol Documentation (Minecraft 协议文档):** Search for "Minecraft Protocol Documentation" on Google. You might find community-maintained documentation or older versions of the official documentation. Be aware that the protocol changes with each Minecraft version. * **Chinese Translation:** 在 Google 上搜索 "Minecraft 协议文档"。你可能会找到社区维护的文档或旧版本的官方文档。请注意，该协议会随着每个 Minecraft 版本而更改。 * **Packet Analyzers (数据包分析器):** Tools like Wireshark can capture and analyze network traffic. You can use them to observe the packets exchanged between a Minecraft client and server. This is a more advanced technique but can be very helpful for debugging. * **Chinese Translation:** 像 Wireshark 这样的工具可以捕获和分析网络流量。你可以使用它们来观察 Minecraft 客户端和服务器之间交换的数据包。这是一种更高级的技术，但对于调试非常有用。 * **Minecraft Source Code (Minecraft 源代码):** If you have access to the Minecraft source code (e.g., through decompilation or modding), you can directly examine how the game handles the protocol. This is the most in-depth approach. * **Chinese Translation:** 如果你有权访问 Minecraft 源代码（例如，通过反编译或模组），你可以直接检查游戏如何处理协议。这是最深入的方法。 **Interacting with an MCP Server (与 MCP 服务器交互):** * **Libraries and APIs (库和 API):** Use libraries specifically designed for interacting with Minecraft servers. Popular options include: * **Python:** `mcstatus`, `nbt` * **Java:** `MinecraftForge`, `Spigot API`, `Paper API` (for server-side plugins, but can be used for client interaction with some effort) * **Node.js:** `minecraft-protocol` * **Chinese Translation:** 使用专门为与 Minecraft 服务器交互而设计的库。流行的选项包括： * **Python:** `mcstatus`, `nbt` * **Java:** `MinecraftForge`, `Spigot API`, `Paper API` (用于服务器端插件，但也可以通过一些努力用于客户端交互) * **Node.js:** `minecraft-protocol` * **Example Code (示例代码):** Search for example code snippets that demonstrate how to connect to a Minecraft server, send commands, and receive data. Look for examples using the libraries mentioned above. * **Chinese Translation:** 搜索示例代码片段，这些代码片段演示了如何连接到 Minecraft 服务器、发送命令和接收数据。查找使用上述库的示例。 * **Minecraft Server APIs (Minecraft 服务器 API):** If you're interacting with a server that has custom APIs (e.g., through a plugin), you'll need to consult the documentation for that specific API. * **Chinese Translation:** 如果你正在与具有自定义 API 的服务器（例如，通过插件）交互，则需要查阅该特定 API 的文档。 * **Reverse Engineering (逆向工程):** If no documentation is available, you might need to reverse engineer the server's behavior by observing its responses to different commands. This is a more advanced technique. * **Chinese Translation:** 如果没有可用的文档，你可能需要通过观察服务器对不同命令的响应来逆向工程服务器的行为。这是一种更高级的技术。 **Important Considerations (重要注意事项):** * **Minecraft Version (Minecraft 版本):** The Minecraft protocol changes frequently. Make sure your code is compatible with the specific version of Minecraft you're targeting. * **Chinese Translation:** Minecraft 协议经常更改。确保你的代码与你所针对的特定 Minecraft 版本兼容。 * **Authentication (身份验证):** Many servers require authentication. You'll need to handle the authentication process correctly. * **Chinese Translation:** 许多服务器需要身份验证。你需要正确处理身份验证过程。 * **Rate Limiting (速率限制):** Servers often have rate limits to prevent abuse. Be mindful of these limits and avoid sending too many requests too quickly. * **Chinese Translation:** 服务器通常具有速率限制以防止滥用。请注意这些限制，并避免过快地发送太多请求。 * **Server-Side Mods/Plugins (服务器端模组/插件):** Be aware that server-side mods or plugins can modify the protocol or add custom commands. * **Chinese Translation:** 请注意，服务器端模组或插件可以修改协议或添加自定义命令。 **Where to Find Help (在哪里寻求帮助):** * **Stack Overflow (Stack Overflow):** A great resource for asking programming questions. Use the `minecraft` tag. * **Chinese Translation:** 一个提问编程问题的好资源。使用 `minecraft` 标签。 * **Minecraft Forums (Minecraft 论坛):** For general Minecraft-related questions. * **Chinese Translation:** 用于一般的 Minecraft 相关问题。 * **Discord Servers (Discord 服务器):** Many Minecraft communities have Discord servers where you can ask for help. * **Chinese Translation:** 许多 Minecraft 社区都有 Discord 服务器，你可以在其中寻求帮助。 **Key Terms (关键术语):** * **Packet (数据包):** A unit of data transmitted between the client and server. * **Handshake (握手):** The initial exchange of information between the client and server to establish a connection. * **NBT (命名二进制标签):** A data format used to store complex data structures in Minecraft. * **API (应用程序编程接口):** A set of functions and procedures that allow different software components to interact. This should give you a good starting point. Good luck!

edgar-sec-mcp

一个用于从 EDGAR 获取数据的 MCP 服务器 (Yī gè yòng yú cóng EDGAR huòqǔ shùjù de MCP fúwùqì) **Breakdown:** * **一个 (yī gè):** A * **用于 (yòng yú):** Used for / For * **从 (cóng):** From * **EDGAR:** EDGAR (The acronym is usually kept as is) * **获取 (huòqǔ):** To get / To obtain / To acquire * **数据 (shùjù):** Data * **的 (de):** Of (possessive particle) * **MCP 服务器 (MCP fúwùqì):** MCP Server

OKX MCP Server

Vidu MCP Server

镜子 (jìng zi)

eSignatures NDA Tutorial

Okay, here's a tutorial on creating NDAs (Non-Disclosure Agreements) using eSignatures MCP Server. I'll provide a general outline and key considerations, as the specific steps will depend on your exact configuration and the features you're using within eSignatures MCP Server. **General Workflow:** 1. **Prepare the NDA Document:** 2. **Configure the eSignatures MCP Server:** 3. **Initiate the Signing Process:** 4. **Sign the NDA:** 5. **Verification and Storage:** **Detailed Steps:** **1. Prepare the NDA Document:** * **Create the NDA:** Use a word processor (like Microsoft Word, Google Docs, or LibreOffice) to create your NDA document. Ensure it includes all necessary clauses, such as: * **Parties Involved:** Clearly identify the disclosing party and the receiving party. * **Definition of Confidential Information:** Be specific about what constitutes confidential information (e.g., trade secrets, customer lists, financial data, etc.). * **Obligations of the Receiving Party:** Outline the restrictions on using and disclosing the confidential information. * **Exclusions:** Specify any information that is *not* considered confidential (e.g., information already publicly available). * **Term:** Define the duration of the NDA. * **Governing Law:** Specify the jurisdiction that will govern the agreement. * **Signatures:** Leave space for the signatures and dates. * **Save as PDF:** Save the NDA document as a PDF file. This is the standard format for e-signatures. PDF/A format is often preferred for long-term archiving. **2. Configure the eSignatures MCP Server:** * **Access the MCP Server Administration Interface:** Log in to the eSignatures MCP Server administration panel. The URL and login credentials will be provided by your system administrator. * **Configure Users/Recipients:** * **Add Users:** Ensure that all potential signers (both internal and external) are registered as users within the MCP Server. This may involve creating user accounts or integrating with an existing directory service (e.g., Active Directory, LDAP). * **Define Roles (Optional):** If your workflow requires different levels of access or approval, define roles within the system. * **Configure Signing Certificates (if applicable):** * **Internal Signers:** If internal users will be using digital certificates for signing, ensure that their certificates are properly configured within the MCP Server. This may involve importing certificates or integrating with a Certificate Authority (CA). * **External Signers:** For external signers, you may need to provide options for them to obtain or use digital certificates, or use alternative signing methods (e.g., click-to-sign, OTP). * **Configure Workflow (if applicable):** * **Define the Signing Order:** If the NDA needs to be signed by multiple parties in a specific order, configure the workflow to enforce this order. * **Set Reminders:** Configure automatic reminders to be sent to signers who have not yet completed the signing process. * **Define Escalation Rules:** Set up escalation rules to notify administrators if a document is not signed within a certain timeframe. * **Configure Branding (Optional):** Customize the appearance of the signing interface with your company logo and branding. * **Configure Security Settings:** Review and adjust security settings to ensure the confidentiality and integrity of the signed documents. This may include encryption settings, access controls, and audit logging. **3. Initiate the Signing Process:** * **Upload the NDA Document:** Upload the PDF version of the NDA to the eSignatures MCP Server. * **Specify Recipients:** Add the recipients (signers) to the document. You'll typically need to provide their names and email addresses. * **Define Signature Fields:** Use the MCP Server's tools to define the signature fields within the document. This specifies where each signer needs to place their signature. You can also add other fields, such as date fields, text fields, or checkboxes. * **Set Signing Options:** Choose the signing method for each recipient (e.g., digital certificate, click-to-sign, OTP). * **Send the Document for Signing:** Initiate the signing process. The MCP Server will send email notifications to the recipients with instructions on how to sign the document. **4. Sign the NDA:** * **Recipient Receives Notification:** The recipient receives an email notification with a link to the document. * **Recipient Accesses the Document:** The recipient clicks the link and is directed to the eSignatures MCP Server interface. * **Recipient Reviews the Document:** The recipient reviews the NDA document carefully. * **Recipient Signs the Document:** The recipient follows the instructions to sign the document. This may involve: * **Digital Certificate:** Selecting their digital certificate and entering their PIN. * **Click-to-Sign:** Clicking a button to indicate their agreement. * **OTP (One-Time Password):** Entering a code sent to their email or phone. * **Signature is Applied:** The recipient's signature (or electronic representation of their signature) is applied to the document in the designated signature field. * **Document is Sealed:** The eSignatures MCP Server seals the document to prevent tampering. This typically involves applying a digital signature to the entire document. **5. Verification and Storage:** * **Verification:** The eSignatures MCP Server provides tools to verify the authenticity and integrity of the signed document. This allows you to confirm that the document has not been tampered with since it was signed. * **Storage:** The signed NDA is stored securely within the eSignatures MCP Server. You can typically configure the storage location and retention policies. * **Audit Trail:** The eSignatures MCP Server maintains an audit trail of all actions related to the document, including who signed it, when it was signed, and any other relevant events. * **Download:** Authorized users can download the signed NDA document in PDF format. **Important Considerations:** * **Legal Compliance:** Ensure that your use of e-signatures complies with all applicable laws and regulations in your jurisdiction (e.g., ESIGN Act in the US, eIDAS Regulation in the EU). * **Security:** Implement strong security measures to protect the confidentiality and integrity of the signed documents. * **User Training:** Provide adequate training to users on how to use the eSignatures MCP Server and how to sign documents electronically. * **Integration:** Consider integrating the eSignatures MCP Server with your other business systems (e.g., CRM, ERP) to streamline your workflows. * **Backup and Disaster Recovery:** Implement a robust backup and disaster recovery plan to protect your signed documents from data loss. * **Specific MCP Server Features:** Consult the eSignatures MCP Server documentation for detailed information on the specific features and configuration options available to you. The exact steps may vary depending on the version and configuration of your server. **Example Scenario (Simplified):** 1. **Prepare NDA:** Create an NDA in Word and save it as `NDA.pdf`. 2. **Log in to MCP Server:** Access the MCP Server admin interface. 3. **Add Users:** Add "john.doe@example.com" and "jane.smith@example.com" as users. 4. **Upload NDA:** Upload `NDA.pdf`. 5. **Add Recipients:** Add John Doe and Jane Smith as recipients. 6. **Define Signature Fields:** Use the drag-and-drop interface to place signature fields for John Doe and Jane Smith. 7. **Send for Signing:** Initiate the signing process. 8. **John and Jane Receive Emails:** They receive emails with links to sign the NDA. 9. **John and Jane Sign:** They click the links, review the NDA, and click the "Sign" button. 10. **Signed NDA Stored:** The signed NDA is stored in the MCP Server, and an audit trail is created. **Disclaimer:** This is a general tutorial and may not cover all aspects of using eSignatures MCP Server. Consult the official documentation and your system administrator for specific instructions and guidance. I am not a legal professional, and this information should not be considered legal advice. Always consult with an attorney to ensure that your NDAs and e-signature processes comply with all applicable laws and regulations. --- Now, let's translate this into Chinese. I'll provide a simplified translation, focusing on clarity and key concepts. **中文翻译 (Simplified Chinese Translation):** **使用 eSignatures MCP 服务器创建保密协议 (NDA) 的教程** **概述:** 本教程介绍如何使用 eSignatures MCP 服务器创建保密协议 (NDA)。具体步骤取决于您的配置和服务器功能。 **一般流程:** 1. **准备 NDA 文件:** 2. **配置 eSignatures MCP 服务器:** 3. **发起签署流程:** 4. **签署 NDA:** 5. **验证和存储:** **详细步骤:** **1. 准备 NDA 文件:** * **创建 NDA:** 使用文字处理软件 (如 Microsoft Word, Google Docs, LibreOffice) 创建 NDA 文件。确保包含所有必要条款，例如： * **涉及方:** 明确标识披露方和接收方。 * **保密信息定义:** 明确定义什么是保密信息 (例如，商业秘密、客户名单、财务数据等)。 * **接收方的义务:** 概述使用和披露保密信息的限制。 * **排除项:** 说明哪些信息*不*被视为保密信息 (例如，已公开的信息)。 * **期限:** 定义 NDA 的有效期。 * **适用法律:** 指定管辖协议的司法管辖区。 * **签名:** 留出签名和日期的空间。 * **保存为 PDF:** 将 NDA 文件保存为 PDF 文件。这是电子签名的标准格式。 PDF/A 格式通常更适合长期存档。 **2. 配置 eSignatures MCP 服务器:** * **访问 MCP 服务器管理界面:** 登录到 eSignatures MCP 服务器管理面板。 URL 和登录凭据由您的系统管理员提供。 * **配置用户/收件人:** * **添加用户:** 确保所有潜在的签署人 (内部和外部) 都注册为 MCP 服务器中的用户。这可能涉及创建用户帐户或与现有目录服务 (例如，Active Directory, LDAP) 集成。 * **定义角色 (可选):** 如果您的工作流程需要不同的访问级别或审批，请在系统中定义角色。 * **配置签名证书 (如果适用):** * **内部签署人:** 如果内部用户将使用数字证书进行签名，请确保他们的证书已在 MCP 服务器中正确配置。这可能涉及导入证书或与证书颁发机构 (CA) 集成。 * **外部签署人:** 对于外部签署人，您可能需要提供选项让他们获取或使用数字证书，或使用其他签名方法 (例如，点击签名、OTP)。 * **配置工作流程 (如果适用):** * **定义签署顺序:** 如果 NDA 需要由多个方按特定顺序签署，请配置工作流程以强制执行此顺序。 * **设置提醒:** 配置自动提醒，发送给尚未完成签署流程的签署人。 * **定义升级规则:** 设置升级规则，以便在文档未在特定时间内签署时通知管理员。 * **配置品牌 (可选):** 使用您的公司徽标和品牌自定义签名界面的外观。 * **配置安全设置:** 审查和调整安全设置，以确保已签署文档的保密性和完整性。这可能包括加密设置、访问控制和审计日志记录。 **3. 发起签署流程:** * **上传 NDA 文件:** 将 PDF 版本的 NDA 上传到 eSignatures MCP 服务器。 * **指定收件人:** 将收件人 (签署人) 添加到文档。您通常需要提供他们的姓名和电子邮件地址。 * **定义签名字段:** 使用 MCP 服务器的工具在文档中定义签名字段。这指定了每个签署人需要放置其签名的位置。您还可以添加其他字段，例如日期字段、文本字段或复选框。 * **设置签名选项:** 为每个收件人选择签名方法 (例如，数字证书、点击签名、OTP)。 * **发送文档进行签署:** 发起签署流程。 MCP 服务器将向收件人发送电子邮件通知，其中包含有关如何签署文档的说明。 **4. 签署 NDA:** * **收件人收到通知:** 收件人收到一封电子邮件通知，其中包含指向文档的链接。 * **收件人访问文档:** 收件人单击链接，并被定向到 eSignatures MCP 服务器界面。 * **收件人审查文档:** 收件人仔细审查 NDA 文档。 * **收件人签署文档:** 收件人按照说明签署文档。这可能涉及： * **数字证书:** 选择他们的数字证书并输入他们的 PIN 码。 * **点击签名:** 单击按钮以表示他们的同意。 * **OTP (一次性密码):** 输入发送到他们的电子邮件或手机的代码。 * **应用签名:** 收件人的签名 (或其签名的电子表示) 应用于文档中指定的签名字段。 * **文档被密封:** eSignatures MCP 服务器密封文档以防止篡改。这通常涉及将数字签名应用于整个文档。 **5. 验证和存储:** * **验证:** eSignatures MCP 服务器提供工具来验证已签署文档的真实性和完整性。这使您可以确认文档自签署以来未被篡改。 * **存储:** 已签署的 NDA 安全地存储在 eSignatures MCP 服务器中。您通常可以配置存储位置和保留策略。 * **审计跟踪:** eSignatures MCP 服务器维护与文档相关的所有操作的审计跟踪，包括谁签署了文档、何时签署了文档以及任何其他相关事件。 * **下载:** 授权用户可以下载 PDF 格式的已签署 NDA 文档。 **重要注意事项:** * **法律合规性:** 确保您对电子签名的使用符合您所在司法管辖区的所有适用法律和法规。 * **安全性:** 实施强大的安全措施，以保护已签署文档的保密性和完整性。 * **用户培训:** 为用户提供充分的培训，使其了解如何使用 eSignatures MCP 服务器以及如何以电子方式签署文档。 * **集成:** 考虑将 eSignatures MCP 服务器与您的其他业务系统 (例如，CRM, ERP) 集成，以简化您的工作流程。 * **备份和灾难恢复:** 实施强大的备份和灾难恢复计划，以保护您的已签署文档免受数据丢失。 * **特定 MCP 服务器功能:** 有关可用特定功能和配置选项的详细信息，请参阅 eSignatures MCP 服务器文档。具体步骤可能因服务器的版本和配置而异。 **示例场景 (简化):** 1. **准备 NDA:** 在 Word 中创建 NDA 并将其保存为 `NDA.pdf`。 2. **登录到 MCP 服务器:** 访问 MCP 服务器管理界面。 3. **添加用户:** 添加 "john.doe@example.com" 和 "jane.smith@example.com" 作为用户。 4. **上传 NDA:** 上传 `NDA.pdf`。 5. **添加收件人:** 添加 John Doe 和 Jane Smith 作为收件人。 6. **定义签名字段:** 使用拖放界面为 John Doe 和 Jane Smith 放置签名字段。 7. **发送进行签署:** 发起签署流程。 8. **John 和 Jane 收到电子邮件:** 他们收到包含签署 NDA 链接的电子邮件。 9. **John 和 Jane 签署:** 他们单击链接，审查 NDA，然后单击“签署”按钮。 10. **已签署的 NDA 存储:** 已签署的 NDA 存储在 MCP 服务器中，并创建审计跟踪。 **免责声明:** 这是一个通用教程，可能未涵盖使用 eSignatures MCP 服务器的所有方面。有关具体说明和指导，请参阅官方文档和您的系统管理员。我不是法律专业人士，此信息不应被视为法律建议。始终咨询律师，以确保您的 NDA 和电子签名流程符合所有适用法律和法规。 --- This translation aims to be clear and understandable. Remember to consult with a professional translator for legally binding documents. Good luck!