mcpbeat Sign in

QueryBear MCP Server

by spencerpauly Your server? Claim it
answering

QueryBear is answering right now. Last checked 13 min ago.

Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.

Uptime history 47 days of history · worst day 98%
47 days agonow
100.0%
Uptime 24h
91 of 91 checks
Tools
hidden behind auth
314 ms
Response time
average over 24h
API key
Access
streamable-http

Nothing serious here today

Today is the operative word: we check QueryBear 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 13 min ago.

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

This endpoint answered with an authorization challenge. The server is running, but you need an API key from its owner to call it.

Endpoints

URLTransportStateLatencyChecked
https://mcp.querybear.com/mcp streamable-http needs key 289 ms 13 min ago

Alternatives to QueryBear

same job, measured the same way
SafeSelect MCP
by antonillos

Fail-closed, read-only PostgreSQL and MongoDB access for AI agents over MCP.

local only
Quarry
by wangggym

Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default.

166 installs/wk local only
C
Data
by thinair

PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.

answering
Dbridge MCP
by ugurcl

Query SQLite, PostgreSQL, and MySQL in plain language - read-only, with column masking and limits.

34 installs/wk local only
A2db
by agentic-eng

Safe, read-only database access for AI agents. 5 databases, batch queries, SQLGlot.

102 installs/wk local only
JDBC MCP Server
by igorolv

Read-only PostgreSQL, Oracle and SQL Server access for AI agents: SQL, plans, schema, index stats

local only
pgops
by arzharch

Safe, audited PostgreSQL operations for AI agents: queries, migrations, EXPLAIN, containers

972 installs/wk local only
QueryPilot
by nickklos10

Safe SQL gateway for AI agents: SELECT-only validation, access policies, masking, audit trail, evals

39 installs/wk local only

QueryBear — questions

Answers built from our own checks of this server.

Why is there no tool list for QueryBear?
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 QueryBear working right now?
We send a real MCP handshake every 15 minutes. Over the last 24 hours 91 of 91 checks got a reply (100.0%), average response time 314 ms. The bar chart above shows every period we have measured.
How do I connect QueryBear?
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 will need your own key: it refuses anonymous clients.
Does QueryBear need an API key?
Yes. Every time we knock, QueryBear answers with an authorization challenge instead of its tool list — that is how we know it is running and gated rather than broken. Bring your own credentials and it will talk.
How fast is QueryBear?
It answers our handshake in 314 ms on average, which is faster than 48% of all working MCP servers we measure. The comparison comes from our own checks across the whole registry, every 15 minutes.