mcpbeat Sign in

Nexlab MCP Server

answering

Nexlab MCP is answering right now. Last checked 5 min ago.

28 MCP servers behind one endpoint: earth, sky, policy, records and research

Uptime history 5 days of history · worst day 99%
5 days agonow
100.0%
Uptime 24h
92 of 92 checks
Tools
hidden behind auth
1186 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nexlab MCP does not always answer

Over the last week it answered 99.8% of our checks. We check every 15 minutes, so you hear about the next outage within the hour — not 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 5 min ago.

run in your terminal
claude mcp add nexlab-mcp --transport http https://mcp.nexlab.net/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "nexlab-mcp": {
      "url": "https://mcp.nexlab.net/mcp"
    }
  }
}
~/.codex/config.toml
[mcp_servers.nexlab-mcp]
url = "https://mcp.nexlab.net/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "nexlab-mcp": {
      "url": "https://mcp.nexlab.net/mcp"
    }
  }
}
.vscode/mcp.json
{
  "mcpServers": {
    "nexlab-mcp": {
      "url": "https://mcp.nexlab.net/mcp"
    }
  }
}

This endpoint answered with an authorization challenge — the server is running, but you need an API key or OAuth to use it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.nexlab.net/mcp streamable-http needs key 440 ms 5 min ago

Alternatives to Nexlab MCP

same job, measured the same way
Manifold
by nonchan7720

MCP gateway aggregating MCP servers and OpenAPI/Swagger REST APIs behind one MCP endpoint

local only
Recipe Signal
by absharma9796

Search and compare attributed recipe records through a public read-only remote MCP endpoint.

4 tools answering
Action1
by wyre-ai

Action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API.

local only
Action1
by wyre-technology

Action1 MCP server — endpoint inventory, patch visibility, and policy automation via REST API.

local only
AISIX AI Gateway
by api7

Self-hosted AI gateway that governs MCP servers, LLM traffic, and A2A agents behind one endpoint

local only
GlobalSource Partners MCP Server
by globalsourcepartners

Search expert emerging-markets research on economics, politics, policy and sovereign risk.

4 tools answering
Genefoundry
by berntpopp

MCP gateway federating 22 biomedical MCP servers behind one endpoint: gnomAD, ClinVar, HPO, VEP.

answering
C
MCP Aggregation Gateway — 22k+ MCP search & call
by pianam-mcp

One AI endpoint to search and call 22k+ MCP servers; 50+ hosted tools work instantly, no key.

3 tools answering

Nexlab MCP — questions

Answers built from our own checks of this server.

Why is there no tool list for Nexlab MCP?
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: 100.0% of checks in the last 24 hours got a reply.
Is Nexlab MCP working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 92 of 92 checks got a reply (100.0%), average response time 1186 ms. The bar chart above shows every period we have measured.
How do I connect Nexlab MCP?
Copy the ready config from this page — we generate it for Claude Code, Claude Desktop, Codex, Cursor and VS Code, each with the file path 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 Nexlab MCP?
No API key is involved. Nexlab MCP 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 Nexlab MCP?
It answers our handshake in 1186 ms on average, which is faster than 4% of all working MCP servers we measure. That is on the slow side — worth knowing if the tool sits inside an interactive loop. The comparison comes from our own checks across the whole registry, every 15 minutes.