Developer · Remote MCP server
QueryBear
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
What the MCP Registry states
The entry as published to the official MCP Registry (read 2026-10-04), latest version.
- Registry name
io.github.spencerpauly/querybear- Version
- 1.0.0
- Status
- Active
- Category
- developer
- Transport
- Streamable HTTP
- Published
- 2026-05-02
- Updated
- 2026-05-02
- Publisher
- spencerpauly (GitHub)
- Namespace
- Namespace verified by the MCP Registry via GitHub (github.com/spencerpauly) · how
- Listed under
- PostgreSQL MCP servers, MySQL MCP servers
- Website
- querybear.com
- Source
- Registry API entry
Remote endpoints
| Transport | URL | Headers declared |
|---|---|---|
| Streamable HTTP | https://mcp.querybear.com/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.
- Reachable
- Yes (HTTP 401)
- Handshake
- Not completed: sign-in required
- Sign-in required
- Yes - HTTP 401; a Bearer token is asked for
- Checked on
- 2026-10-05
How to connect QueryBear
QueryBear is a remote MCP server: there is nothing to install. Its endpoint is https://mcp.querybear.com/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.
No headers are declared in the registry entry. If the server needs you to sign in, a client that supports MCP authorization opens the service's own sign-in page when it first connects.
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 developer servers
| Server | Runs |
|---|---|
| Quantoracle73 deterministic quant tools for AI agents. LLMs drift on Black-Scholes; these are exact math. | Local · stdio |
| Quantumguard MCPPost-quantum cryptography security scanner. Detect ECDSA/RSA vulnerabilities, NIST compliance. | Local · stdio |
| QuarrySafety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default. | Local · stdio |
| Quash - Mobile App AutomationDrive Android & iOS mobile-app automation from your AI agent on locally connected devices. | Local · stdio |
| QueryPilotSafe SQL gateway for AI agents: SELECT-only validation, access policies, masking, audit trail, evals. | Local · stdio |
| QueryshieldSecure SQL proxy for AI agents - NL→SQL, AST safety, per-agent RLS, audit log. | Local · stdio |
| QueryWeaverAn MCP server for Text2SQL: transforms natural language into SQL using graph schema understanding. | Local · HTTP |
| QuestDB Web Console MCP ServerConnects coding agents to a running QuestDB Web Console: notebook cells, SQL queries, and charts. | Local · stdio |