$ loading_
Run safe read-only SQL queries on PostgreSQL and ClickHouse with managed results.
This tool claims to provide read-only SQL access to PostgreSQL and ClickHouse with no extra secrets and no declared remote endpoints. Based on the provided material, there are no clear high-risk red flags, but its local execution and database data access still warrant caution. Open-source MIT licensing is a positive signal, though low adoption and unknown maintenance reduce supply-chain confidence.
The material explicitly states there are no required secrets or environment variables, and no extra token or third-party credential requirement is disclosed. However, actual database connectivity may still rely on external DB connection settings, and the documentation is insufficient to fully confirm credential handling details.
No remote endpoint host is declared, and there is no indication of data being sent to unrelated third-party services. However, its stated function inherently involves connecting to PostgreSQL/ClickHouse databases, so query content will be sent to the configured database service, which is normal network behavior for this tool class.
The system checks indicate that this tool executes code, meaning it runs a local process/program. The provided material does not show requests for unusual system privileges, nor execution capabilities beyond its database-access purpose, so this aligns with normal MCP local execution risk.
The tool claims to provide read-only SQL access to PostgreSQL and ClickHouse and mentions 'managed result files,' indicating it can at least read database contents and may manage query result files locally. Although it claims read-only enforcement and timeouts, it may still access sensitive business data, and the exact local file handling scope is not described.
There is a public GitHub repository and an MIT open-source license, which is better than closed source for auditability. However, the source is only listed via a third-party registry, community adoption is 0 stars, maintenance status is unknown, and the missing README limits assessment of implementation details and dependency risk, so caution is warranted.
Copy the install command and let the AI configure it · recommended for beginners
No copy-paste install info for "mcp-read-only-sql" yet — see the docs or source repo.
Connect to PostgreSQL and run a read-only query for daily new users and paid conversion rate over the last 30 days, sorted by date ascending.
A structured result table with date, new users, and paid conversion rate for analysis.
In ClickHouse, run a read-only query to find the top 20 API endpoints with the most error logs in the past 7 days, including path and error count.
A ranked list of endpoints by error count to help identify frequent failure sources.
Run a read-only SQL query on PostgreSQL to summarize monthly order revenue for this year and save the output as a downloadable result file.
A monthly revenue summary with a managed result file for download or sharing.
Safely inspect PostgreSQL schemas and run read-only queries for analysis.
Securely inspect schema and run read-only queries on one MySQL database.
Safely query SQL Server data and inspect tables and schemas read-only.
Safely query read-only PostgreSQL data and inspect schemas for analysis.
Let AI query multiple SQL databases read-only and export results.
Lets AI safely explore SQL schemas and run read-only database queries.