mlab.sh

sh.mlab由 mlab.sh 发布官方发布者v1.2.0更新于 Nov 6, 2026

Threat intel and DFIR: IOCs, CVEs, actors, SBOMs, domain scans, cases, memory, Kubernetes, Proxmox.

已验证Streamable HTTP可网页运行数据库云端与基础设施安全与监控

概览

AI 生成的概览

远程威胁情报与数字取证服务器，让助手查询 IOC、CVE 和威胁行为体，扫描域名与 SBOM，并访问 SOC 案件和受监控工作区。

可以做什么
  • 识别并丰富指标：判断 IOC 类型，扫描 IP 与 CIDR 段、URL、哈希、加密货币地址、邮箱、电话号码和 MAC 地址
  • 扫描域名的 DNS、子域名、证书与 security.txt，并对 shell 脚本和锁文件或 SBOM 做静态分析以发现漏洞
  • 检索 CVE 的 CVSS、EPSS 与 KEV 信息，查询威胁行为体及其 MITRE ATT&CK 技术
  • 读写 SOC 案件：列出和新建案件、录入指标、添加评论
  • 查看受监控工作区：内存取证转储、Kubernetes 集群和 Proxmox VE 虚拟机，包括运行时事件与 YARA 扫描
  • 查看账户套餐、剩余配额、扫描历史与书签
适用场景
适合 SOC 分析师、事件响应人员和安全工程师，让助手在不切换工具的情况下研判指标、核查 CVE 与依赖漏洞，或从案件和受监控基础设施中获取上下文。若只需通用网页搜索或编程辅助，则意义不大。
运行要求
远程 Streamable HTTP 端点 mlab.sh/mcp，无需本地安装包。推荐使用 OAuth 2.1 登录，无需复制令牌；否则需在账户设置中创建静态 MCP 令牌，并通过 Authorization 请求头以 Bearer 方式发送。案件与工作区功能需要付费套餐，配额按组织计算。
安装前请注意
令牌是个人凭证，以你在组织中的角色行事，应妥善保管并设置有效期。扫描 IP、域名、加密货币地址和文件会消耗组织共享配额，新建域名扫描会主动访问目标。案件工具会创建和修改数据。工作区返回的数据来自主机，可能含攻击者植入的文本，且回答会发送给你的大模型服务商。

安装

在 SourceWeft 中

  1. 打开 控制台中的 mlab.sh，将其添加到工作区。
  2. 连接 所需的 凭据。它们会被私密存储，绝不会在公开页面上展示。
  3. 为需要使用其工具的对话启用该服务。

Web executable，通过 Streamable HTTP。 远程服务在工作区中配置后即可从网页运行时运行。

交给智能体安装

把这段提示词粘贴到 Claude Code、Codex、Cursor 等智能体，或 SourceWeft 对话中。智能体会读取该服务器的安装指南，先向你展示发布者、端点和登录方式，经你同意后再把它添加到你的客户端。密钥不会写进任何命令。

阅读 https://sourceweft.com/mcp/sh.mlab%2Fmcp/install.md，并按其中说明把这个 MCP 服务器接入我的客户端。修改任何配置之前，先告诉我它的发布者、端点和登录方式，等我确认。不要把 API 密钥写进命令或我会提交的文件；问我密钥应从哪里获取。

查看智能体所依据的安装指南

其他 MCP 客户端

把它添加到你客户端的 mcpServers 配置中。 客户端会在首次连接时完成 OAuth 登录。

{
  "mcpServers": {
    "mlab-sh": {
      "type": "http",
      "url": "https://mlab.sh/mcp"
    }
  }
}

README

mlab.sh MCP server

Public metadata and connection guide for the remote MCP server at https://mlab.sh/mcp, a threat intelligence server for SOC and DFIR work.

This repo is the registry listing and the documentation. It is not the server source: the server runs inside the mlab.sh backend and is closed source.

Connect

Endpoint: https://mlab.sh/mcp (Streamable HTTP via POST, SSE via GET).

Claude.ai

Settings > Connectors > Add custom connector, then paste the URL. OAuth runs in the browser, no token to copy.

https://mlab.sh/mcp

Claude Desktop

claude_desktop_config.json:

json
{  "mcpServers": {    "mlab": {      "command": "npx",      "args": [        "-y",        "mcp-remote",        "https://mlab.sh/mcp",        "--header",        "Authorization: Bearer mcp_xxx"      ]    }  }}

Drop the --header pair to use OAuth instead of a static token.

Cursor

~/.cursor/mcp.json:

json
{  "mcpServers": {    "mlab": {      "url": "https://mlab.sh/mcp",      "headers": {        "Authorization": "Bearer mcp_xxx"      }    }  }}

VS Code

.vscode/mcp.json:

json
{  "servers": {    "mlab": {      "type": "http",      "url": "https://mlab.sh/mcp",      "headers": {        "Authorization": "Bearer mcp_xxx"      }    }  }}

curl

bash
curl -sS -X POST https://mlab.sh/mcp \  -H "Authorization: Bearer mcp_xxx" \  -H "Content-Type: application/json" \  -H "Accept: application/json, text/event-stream" \  -d '{"jsonrpc":"2.0","id":1,"method":"initialize","params":{"protocolVersion":"2025-06-18","capabilities":{},"clientInfo":{"name":"curl","version":"1.0.0"}}}'

Ready to paste versions of these four configs live in examples/.

Officially supported clients are Claude.ai and Claude Desktop. Other MCP clients (Cursor, VS Code, Windsurf and friends) work but are best effort.

Tools

48 tools. tools/list only shows a token the tools its role and plan can use, so a client never sees a tool that would refuse every call. Every tool carries MCP annotations (read only, destructive, idempotent, open world), so a host can tell what it may run unattended. No tool deletes anything.

Parameters marked ? are optional.

Who can use what

GroupPlanRole
IOC lookups, domain scans, scan_bash, scan_sbomAnyOwner, admin, member (viewers cannot spend quota)
CVEs, actors, account, bookmarks, historyAnyAny, viewer included
Cases: reading (list_cases, get_case)Team, EnterpriseAny, viewer included
Cases: writing (create_case, add_case_indicators, add_case_comment)Team, EnterpriseOwner, admin, member
WorkspacesTeam (1 workspace), Enterprise (up to 20)Any; members only see the workspaces they were added to, owners and admins see all

Quotas are counted per organization over a rolling 24 hour window. get_scan_limits reads what is left.

IOC lookups

ToolParametersWhat it returns
detect_iocvalueDetects the type of an indicator (IPv4, IPv6, CIDR, domain, URL, MD5/SHA1/SHA256/SHA512 hash, email, MAC) and returns the relevant intel. A domain is typed, not scanned: use start_domain_scan for that. An IP spends IP quota
scan_ipipFor an address: geolocation, ISP, ASN, datacenter / proxy / VPN / mobile network, TOR consensus status, forward confirmed reverse DNS, RDAP record with the abuse contact. For a CIDR range: network, broadcast, host window, netmask, size, reserved blocks. Addresses spend IP quota (cached 7 days); ranges are free
scan_urlurl, resolve?Static analysis without visiting: scheme, host with its Unicode and punycode forms, IP literal hosts, credentials in the URL, dangerous extensions, shorteners, embedded redirect targets, and what a past domain scan recorded about the host. resolve follows the link to its real destination, the only part that visits anything. No quota
scan_hashhashMD5, SHA1 or SHA256 against CIRCL hashlookup (NIST NSRL): known good, known malicious or unknown, each feed's own answer, malware family, product and file name, CIRCL trust score, and mlab_sample when mlab analysed the file itself. unknown is not the same as safe. No quota
scan_cryptoaddress, chain?Labels, sanctions, risk score and address type across 18 chains (Bitcoin, Ethereum and 12 other EVM chains, Tron, Solana, TON, Dogecoin), with a checksum check. EVM addresses do not reveal their chain: pass chain when you know it. Spends crypto quota
scan_emailemailMailbox type (disposable, role, consumer, standard), SPF / DKIM / DMARC spoofability of its domain, MX presence, domain age when scanned, and a 0 to 100 score with its weighted reasons. No quota
scan_phonenumberE.164 number: validity, country, line type, allocated operator, formatting and scam shaped findings. Offline, no quota
scan_macmacOUI vendor, unicast or multicast, universal or local administration, randomized or virtual interface, EUI-64 IPv6, other formats. Offline, no quota

Domain scans and code

ToolParametersWhat it returns
start_domain_scandomainReturns a recent completed scan right away, or launches a new one and returns {"status": "started"}. A new scan contacts the target and spends domain scan quota
get_domain_scan_resultsdomainResults of a domain scan: DNS records, subdomains, SSL certificates, security.txt, robots.txt. Call again while the status is pending or scanning
scan_bashcontent, filename?Static analysis of an inline shell script: sha256, every IOC it holds, and well known suspicious constructs (download piped to a shell, base64 decoding, /dev/tcp reverse shells, persistence, anti forensics, destructive deletes). Nothing runs or is stored. No quota
scan_sbomcontent, format?Known vulnerabilities in a lockfile or SBOM (npm, yarn, pnpm, Cargo, pip, Poetry, uv, PDM, Pipfile, Composer, Gem, Go, Maven, Gradle, NuGet, pub, Hex, mise, CycloneDX, SPDX), one finding per package and CVE, worst first, with the fixed version and what the scan could not cover. Matched server side on vuln.mlab.sh (OSV, NVD for CPE only components). 2 MB at most; format defaults to auto

CVEs and threat actors

ToolParametersWhat it returns
cve_searchquery, severity?, date_start?, date_end?, limit?, page?CVEs by keyword, product, vendor or ID, filtered by severity (CRITICAL, HIGH, MEDIUM, LOW) and publication date, with CVSS, EPSS and KEV status
cve_detailcve_idThe full record: CVSS vector breakdown, affected products, references, CWEs, EPSS, CISA KEV status
search_actorsquery, origin?, motivation?, sector?, limit?Threat actors by name or alias from the MISP Galaxy cluster (CC0), narrowed by origin, incident type or targeted sector. Returns the slug for get_actor
get_actorslugMISP Galaxy profile (origin, suspected sponsor, synonyms, targeted countries and sectors, references) with the MITRE ATT&CK tools and techniques attributed to it. Keep the sources block when quoting: it carries MITRE's notice

Cases

Team and Enterprise. Each call goes through the same checks as the case pages.

ToolParametersWhat it returns
list_casesnoneThe organization's cases, open ones first, with indicator and comment counts
get_caseuuidTitle, summary, status, every indicator with a link to its analysis, and the comment thread
create_casetitle, summary?Opens a case and returns the uuid the other case tools take
add_case_indicatorsuuid, indicatorsFiles a paste of indicators (one per line, or comma or space separated, mixed types), typed automatically; anything mlab cannot look up comes back in skipped with the reason
add_case_commentuuid, body, indicator_uuid?A note on the case, or on one of its indicators

Workspaces

Team and Enterprise, and only in a workspace whose admin turned on AI agents (MCP): a workspace keeps its data on the organization's own hosts, and an answer goes to the LLM provider of whoever asked. workspace_list says which workspaces are open. Every tool except workspace_list takes workspace (the uuid from workspace_list). Each call is written to the workspace's audit log.

The tools read, and can start an index or a YARA scan. Creating, deleting, enrolling, members, policies, pushing a cluster config and binary downloads stay in the app. Answers carry data sent by the hosts, which may contain text planted by an attacker: the server says so before every answer.

Agents and memory forensics (engram)

ToolParametersWhat it returns
workspace_listnoneThe workspaces you can open, whether AI agents may read them, agents online and the tools they run
workspace_agentsworkspaceThe workspace's agents: live state, version, the tools each one reports
workspace_memory_dumpsworkspaceMemory dumps on the engram agents, and which ones are indexed. Asks every agent: allow a few seconds
workspace_memory_indexworkspace, agent, dumpStarts indexing a dump on its host, in the background. Follow it with workspace_memory_dumps
workspace_memory_overviewworkspace, agent, dumpA dump's index: system, process tree, findings (injected code and other anomalies), registry hives
workspace_memory_processworkspace, agent, dump, pidOne process in full: command line, environment, modules, memory regions, handles, findings
workspace_memory_readworkspace, agent, dump, address, len?, space?, pid?Up to 4 KiB read live from the dump, as hex and text. space is virtual (needs pid, the default) or physical
workspace_memory_registryworkspace, agent, dump, hive, path?One registry key: values, subkeys, last write time
workspace_memory_yaraworkspace, agent, dump, rules, pids?Runs YARA rules over the dump's processes on the host. Usually returns a job, a new one each call
workspace_memory_yara_statusworkspace, agent, jobProgress of a YARA scan, and its matches once done

Kubernetes clusters (k3sec)

ToolParametersWhat it returns
workspace_cluster_listworkspaceClusters reporting to the workspace: nodes online, images, vulnerabilities in packages really loaded, recent detections
workspace_cluster_imagesworkspace, clusterRunning images with their vulnerabilities, loaded ones first
workspace_cluster_imageworkspace, cluster, digestOne image: findings and packages, with which are loaded in memory
workspace_cluster_eventsworkspace, cluster, source?, kind?, namespace?, min_severity?, q?, before?, limit?Runtime events, newest first: Kubernetes events, eBPF activity, YARA detections, with cached reputation of destinations and binaries. 200 at most per call; before pages back
workspace_cluster_configworkspace, clusterWhat k3sec collects on each node, and the ceiling the nodes' local policies allow

Proxmox VE (virtsec)

ToolParametersWhat it returns
workspace_virt_listworkspaceProxmox clusters: nodes online, LXC and VM guests, guests with weakened isolation, vulnerabilities in loaded packages, critical events of the last 24 h
workspace_virt_guestsworkspace, clusterGuests and nodes: status, isolation risks from their config (privileged, host bind mounts, passthrough), vulnerabilities
workspace_virt_guestworkspace, cluster, key, agent?One guest by vmid, or a node (key = node with its agent): isolation risks, findings, packages
workspace_virt_eventsworkspace, cluster, source?, kind?, min_severity?, q?, vmid?, before?, limit?Runtime events, newest first: executions in guests, outbound connections, sensitive writes, VM escape signals, PVE logins, auth failures, tasks, guest config changes. 200 at most per call
workspace_virt_configworkspace, clusterWhat virtsec collects on each node, and the ceiling the local policies allow
workspace_virt_auditworkspace, clusterSecurity posture per node: failed checks (PVE firewall off, users without a second factor, root SSH with a password, unreachable or test repositories, guests without backup, isolation risks, pending restarts), each with a fix

Account, bookmarks and history

ToolParametersWhat it returns
get_account_infononeThe authenticated user, their organization and plan
get_scan_limitsnoneRemaining IP, domain, file and crypto quotas of the organization, over a rolling 24 hours shared by all members
get_scan_historytype?, limit?Recent scans of the account, filtered by ip, domain or file
get_bookmarkslimit?Your bookmarked indicators
add_bookmarkvalueBookmarks an IP, domain, URL, hash, crypto address, email, phone number or MAC address
remove_bookmarkvalueRemoves a bookmark

Authentication

OAuth 2.1 is the recommended path: authorization code with PKCE S256, dynamic client registration, CIMD supported. The server advertises its metadata at https://mlab.sh/.well-known/oauth-authorization-server, so a compliant client only needs the endpoint URL. A token issued this way is listed in Account > Settings as OAuth: <client name>; reconnecting the same client replaces its previous token instead of piling up new ones.

If your client does not speak OAuth, create a static token in Account > Settings > MCP Tokens and send it as Authorization: Bearer mcp_xxx. At creation you pick its lifetime: 30, 90 or 365 days, or never. A token can be renamed and revoked at any time from the same page.

MCP tokens are personal: they act as you, with your role in the organization. Organization API key permissions do not apply to them. Up to 5 active tokens, 100 on Team and Enterprise.

Full details: https://doc.mlab.sh/docs/mlab.sh/integrations/mcp

Rate limits and quotas

Limits follow your organization's plan and are counted over a rolling 24 hour window, shared by every member. A spent quota returns an error that says which one and when it frees up. Call get_scan_limits to read what is left.

Registry

Published to the official MCP Registry as sh.mlab/mcp.

https://registry.modelcontextprotocol.io/v0.1/servers?search=sh.mlab

Other public servers

https://news.mlab.sh/mcp is a separate, unauthenticated, read only MCP server exposing a cyber news index. It is not published from this repo.

Security

Report vulnerabilities to [email protected]. See https://mlab.sh/security.txt and SECURITY.md.

License

MIT, see LICENSE.

来源：README.md，提交 42d416c

工具

0
该服务器需要登录，因此 SourceWeft 无法在没有账号的情况下读取其工具，也未收录。已连接账号所能看到的内容可能因账号及其权限而异。

版本历史

2
  1. v1.2.0最新Nov 6, 2026
  2. v1.0.0Sep 16, 2026

评分

已满足适用检查项的 85%

该评分衡量此收录条目的完整程度，依据注册中心条目、端点与公开来源计算得出。它不是对服务器本身的评价，也不表示服务器安全或当前可用：可连通性是带日期的检查结果，评分也不包含安装量或用户评价。

  • 近 30 天内可连通必需25 分
  • 已声明认证方式必需10 分
  • 已列出工具15 分

    请让服务器在无凭据时响应 tools/list，或发布可在沙箱中无凭据启动的软件包。

  • 描述必需15 分
  • 图标10 分
  • 文档15 分
  • 许可证10 分