SafeSelect MCP runs on your own machine — the client starts it, so there is no endpoint to ping. Last commit 15 Oct 2026.
Fail-closed, read-only PostgreSQL and MongoDB access for AI agents over MCP.
We read the source, 22 h ago · rules ccca72095570
Things with no honest explanation: a promise that contradicts the code, code that runs at install time while hiding what it does, data leaving the machine.
return subprocess.check_output(args, text=True, **kwargs).strip()
What this server is able to do. For an MCP server this is often the job itself — a terminal server runs commands because that is what it is for. Listed so you know what you are plugging in, not as an accusation.
return subprocess.check_output(args, text=True, **kwargs).strip()
cp safeselect "${installed_binary}"
chmod +x "${installed_binary}"
Is this your server and something here is wrong? Tell us — corrections are free and do not require a plan.
Code changes quietly between releases, and nobody reads the diff of a dependency. We do, on every release — watch SafeSelect MCP and you get told the day something new turns up.
PostgreSQL, MySQL, and SQL Server in one session. 26 read-only MCP tools for AI agents.
Safe, read-only Postgres and MySQL access for AI agents. Audit log + column-level controls.
Read-only, guarded SQL access for AI agents: PostgreSQL, MySQL, ClickHouse, Oracle, SQL Server, Db2
Safety-railed database access for agents: Postgres, MySQL, Redis. Read-only by default.
Safe, read-only-by-default MySQL, PostgreSQL & SQLite access for AI agents. TOON output.
Read-only SQL, plans, schema for AI agents: PostgreSQL, Oracle, SQL Server, Firebird, SQLite, JDBC
MCP server for Oracle, MSSQL, PostgreSQL, MySQL, SQLite, MongoDB, and Qdrant vector search access.
RLS/tenant-aware Postgres for AI agents — schema, read-only SQL, NL→SQL with safety rails.
Answers built from our own checks of this server.