Data · Remote MCP server
mlab.sh
Threat intelligence: enrich IOCs (IP, domain, URL, hash), search CVEs and actors, scan SBOMs.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
sh.mlab/mcp- Version
- 1.0.0
- Status
- Active
- Category
- data
- Transport
- Streamable HTTP, SSE (HTTP + Server-Sent Events)
- Published
- 2026-08-31
- Updated
- 2026-08-31
- Publisher
- sh.mlab
- Namespace
- Namespace verified by the MCP Registry via the domain mlab.sh · how
- Website
- mlab.sh
- Repository
- github.com/mlab-sh/mcp
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mlab.sh/mcp | Authorization (secret) |
| SSE (HTTP + Server-Sent Events) | https://mlab.sh/mcp | None |
Live check
This directory connected to each remote endpoint and asked for its list of tools. The check connects and lists tools only; it doesn't run tools, sign in or test security.
- Endpoint
https://mlab.sh/mcp(HTTP)- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
- Endpoint
https://mlab.sh/mcp(SSE)- Reachable
- Yes (HTTP 401)
- SSE stream
- Not opened: sign-in required
- Sign-in required
- Yes - HTTP 401; OAuth advertised (the answer points to its authorization metadata)
- Checked on
- 2026-10-05
How to connect mlab.sh
mlab.sh is a remote MCP server: there is nothing to install. Its endpoint is https://mlab.sh/mcp, served over Streamable HTTP. In an assistant that accepts remote MCP servers (often under a setting named connectors, integrations or tools), add a new server and give it this URL; in a client configured by file, add it as a remote (HTTP) server with the same URL.
It also lists an endpoint on the older SSE transport https://mlab.sh/mcp. Clients that support remote servers generally still accept SSE endpoints, though the protocol now favours Streamable HTTP.
The registry entry declares an HTTP header for the connection: Authorization (secret). A secret header usually carries an API key or token issued by the service; clients that accept custom headers set it with the server's URL.
Derived from the registry entry; the live check above only shows whether the endpoint answered. What the server does, and on what terms, is set by its publisher; check its repository or website before giving it access to your accounts or files. How to add an MCP server to an assistant · Before you connect
More data servers
| Server | Runs |
|---|---|
| MisoReal-time electricity data for MISO, the grid operator for 15 US states from Louisiana to… | Remote · HTTPLive check: ✓ handshake |
| MitosisMitosis agent-memory platform: pricing, docs search, platform status, agent skills. No auth. | Remote · HTTPLive check: ✓ handshake |
| Mitre Attack MCPSearch the MITRE ATT&CK enterprise knowledge base for adversary techniques and tactics. | Local · stdio |
| Mixcloud MCPSearch Mixcloud cloudcasts and read user profiles. No key required. | Local · stdio |
| Mnema - AI Memory LayerPersonal knowledge graph as an AI memory layer over MCP - read, save, and link your memories. | Remote · HTTPLive check: sign-in required |
| Mnemo MCPPersistent AI memory with hybrid search and embedded sync. Open, free, unlimited. | Local · stdio |
| MobbinSearch real-world UI & UX design references for mobile apps, web apps, and websites with Mobbin. | Remote · HTTPLive check: sign-in required |
| MockmcpHosted MCP endpoint with realistic fake data for prototyping agents. 12 tools, no setup. | Remote · HTTPLive check: ✗ no handshake |