mcpbeat Sign in

btlabs Core MCP Server

answering

btlabs Core is answering right now. Last checked 10 min ago.

btlabs Core MCP endpoint: site content and brand data for AI agents. OAuth or API key.

Uptime history 51 days of history · worst day 97%
51 days agonow
98.9%
Uptime 24h
90 of 91 checks
—
Tools
hidden behind auth
199 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

btlabs Core missed one check 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 10 min ago.

run in your terminal
claude mcp add core --transport http https://btlabs.dev/api/mcp
Settings → Connectors → Add custom connector, then paste this address
https://btlabs.dev/api/mcp
~/.codex/config.toml
[mcp_servers.core]
url = "https://btlabs.dev/api/mcp"
.cursor/mcp.json
{
  "mcpServers": {
    "core": {
      "url": "https://btlabs.dev/api/mcp"
    }
  }
}
.vscode/mcp.json
{
  "servers": {
    "core": {
      "type": "http",
      "url": "https://btlabs.dev/api/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://btlabs.dev/api/mcp streamable-http sign-in 117 ms 10 min ago

Alternatives to btlabs Core

same job, measured the same way
DCC-MCP Core
by dcc-mcp

Agent control plane for DCC and engine hosts: one MCP endpoint, one tool contract.

8 464 installs/wk local only
Hail
by hail-hq

Phone, SMS and email for AI agents. One remote MCP endpoint, OAuth login, zero install.

40 tools answering
TikTok MCP by TokConnect
by tokconnect

TikTok search demand, videos, creators, comments and captions for AI agents. OAuth or API key.

answering
Scala AI OS
by alessandro114

S.C.A.L.A. AI OS and Score: company data, CRM and SARA tools for AI agents via MCP.

local only
Execute api-key-load-balancer-mcp
by evozim

Premium agentic endpoint for api-key-load-balancer-mcp.

1 tools answering
AdminKit
by netbasecorp

Network, DNS, mail-auth and MCP endpoint security checks for AI agents, backed by adminkit.net.

2 485 installs/wk local only
Execute breach-of-contract-mcp
by evozim

Premium agentic endpoint for breach-of-contract-mcp.

1 tools answering
Execute bio-data-parser-mcp
by evozim

Premium agentic endpoint for bio-data-parser-mcp.

1 tools answering

btlabs Core — questions

Answers built from our own checks of this server.

Why is there no tool list for btlabs Core?
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: 98.9% of checks in the last 24 hours got a reply.
Is btlabs Core working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 90 of 91 checks got a reply (98.9%), average response time 199 ms. The bar chart above shows every period we have measured.
How do I connect btlabs Core?
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 btlabs Core?
No API key is involved. btlabs Core 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 btlabs Core?
It answers our handshake in 199 ms on average, which is faster than 73% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.