mcpbeat Sign in

btlabs Core MCP Server

answering

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

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

Uptime history 19 hours of history
19 hours agonow
100.0%
Uptime 24h
70 of 70 checks
Tools
hidden behind auth
192 ms
Response time
average over 24h
OAuth sign-in
Access
streamable-http

Nothing serious here today

Today is the operative word: we check btlabs Core every 15 minutes and re-read its code on every release. Watch it and you find out the day that stops being true.

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 7 min ago.

run in your terminal
claude mcp add core --transport http https://btlabs.dev/api/mcp
~/Library/Application Support/Claude/claude_desktop_config.json
{
  "mcpServers": {
    "core": {
      "url": "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
{
  "mcpServers": {
    "core": {
      "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 110 ms 7 min ago

Alternatives to btlabs Core

same job, measured the same way
Webshift
by annibale-x

Rust MCP server for denoised web search — fetch, clean, and rerank web content for AI agents.

local only
Webshift
by x-hannibal

Rust MCP server for denoised web search — fetch, clean, and rerank web content for AI agents.

local only
Webshift
by x-monk

Rust MCP server for denoised web search — fetch, clean, and rerank web content for AI agents.

local only
RoxyAPI Docs MCP Server (keyless, for coding agents)
by roxyapi

Keyless docs search so coding agents wire up RoxyAPI: every endpoint, param and SDK call.

1 tools answering
x-use
by ihuzaifashoukat

Browser-native AI agents for X (Twitter): multi-account, MCP-ready, no X API key required.

112 installs/wk local only
Fidacy MCP
by lucaslubi

AI Agent Firewall. Enforce signed authority before consequential actions. Free API key required.

585 installs/wk local only
Datris
by datris

The data control plane for AI agents — acquire, validate, land, and query data over MCP.

3 352 installs/wk local only
Locus
by paywithlocus

Pay-per-use APIs for agents: web research, data lookups, and metered endpoints billed to credits.

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: 100.0% 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 70 of 70 checks got a reply (100.0%), average response time 192 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 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 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 192 ms on average, which is faster than 68% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.