mcpbeat Sign in

mlab.sh MCP Server

answering

mlab.sh is answering right now. Last checked 11 min ago. Last commit 31 Oct 2026.

Threat intelligence: enrich IOCs (IP, domain, URL, hash), search CVEs and actors, scan SBOMs.

Uptime history 64 days of history · worst day 79%
64 days agonow
97.8%
Uptime 24h
89 of 91 checks
—
Tools
hidden behind auth
246 ms
Response time
average over 24h
2
Stars
last commit 31 Oct 2026

mlab.sh missed 2 checks this week

Everything else answered, so this is steady rather than shaky. We check every 15 minutes, which is how a one-off gets told apart from the start of a pattern, and how you hear about the next one within the hour instead of from your users.

Three servers free · no card

Connect this server

Endpoint below is the one we actually reach during checks — not the one copied from a README. Last verified 11 min ago.

run in your terminal
claude mcp add mcp --transport sse https://mlab.sh/mcp
Settings → Connectors → Add custom connector, then paste this address
https://mlab.sh/mcp
~/.codex/config.toml
[mcp_servers.mcp]
url = "https://mlab.sh/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "mcp": {
      "url": "https://mlab.sh/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "mcp": {
      "type": "sse",
      "url": "https://mlab.sh/mcp"
    }
  }
}

This endpoint answered with an authorization challenge. The server is running, and it signs you in through your browser: there is no API key to paste.

Endpoints

URLTransportStateLatencyChecked
https://mlab.sh/mcp sse sign-in 146 ms 11 min ago

Alternatives to mlab.sh

same job, measured the same way
isMalicious threat intelligence for AI agents
by ismalicious

Reputation for IPs, domains, URLs, hashes, emails, phones; CVEs; injection and email scans

624 installs/wk 12 tools answering
Intelthreadlinqs MCP
by threadlinqs-cmd

Threadlinqs threat-intelligence MCP — 49 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs

88 installs/wk local only
Intelthreadlinqs MCP
by threadlinqs

Threadlinqs threat-intelligence MCP — 73 tools: threats, detections, IOCs, actors, C2, MITRE, CVEs

local only
Crimson Crawler
by crimsoncrawler

Enrich, search, assess, and manage threat intelligence through 80+ typed MCP tools.

answering
Otx
by w0h1v

MCP server for AlienVault OTX threat intelligence: indicators, pulses, search, and users.

79 installs/wk local only
Pulsedive
by pipeworx-io

Pulsedive MCP — threat-intelligence IOC enrichment (pulsedive.com)

214 installs/wk 46 tools answering
VulnCheck
by vulncheck-oss

VulnCheck exploit intelligence — CVE research, exploit data, advisories, and threat analysis.

local only
Golem Security
by golem

Threat-intelligence verdicts on a URL, domain or IP before a coding agent connects to it.

answering

mlab.sh — questions

Answers built from our own checks of this server.

Why is there no tool list for mlab.sh?
The server answered our handshake with an authorization challenge, so it is running — but it will not describe its tools to an anonymous client. To see them you need to connect with your own credentials. We record it as alive, not as broken: 97.8% of checks in the last 24 hours got a reply.
Is mlab.sh working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 89 of 91 checks got a reply (97.8%), average response time 246 ms. The bar chart above shows every period we have measured.
How do I connect mlab.sh?
Copy the ready config from this page. We generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each in the form that client actually reads. It is a remote server, so there is nothing to install — the client connects to the address. You sign in through your browser once and the client keeps the session: no key to copy, and it refuses anonymous clients.
How do you sign in to mlab.sh?
No API key is involved. mlab.sh answers our knock with an OAuth challenge, so you authorise it once in your browser and the client keeps the session. That is also why we see no tool list: it will not describe itself to an anonymous client, and that is the server working as intended, not a fault.
How fast is mlab.sh?
It answers our handshake in 246 ms on average, which is faster than 58% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.
Is mlab.sh open source?
The code is open source: it is published under the MIT licence and 2 stars on GitHub. The licence covers the code in the repository, not the hosted service at mlab.sh, which runs on its operator's own terms.