MCP Toolbox for Databases is an open source MCP server for databases.
C-Rank Grade: A (Welcoming) - 59/100
External PR Merge Rate: 66%
Response Time: 2d
First Timer Success: 57%
googleapis/mcp-toolbox has a recorded first-timer success rate of 57.1%. Repositories ranked A typically provide actionable feedback during code reviews and actively nurture new community contributors.
Maintainers in googleapis/mcp-toolbox respond to incoming external pull requests in approximately 55.1 hours on average. Keeping PRs focused on single tasks and ensuring tests pass helps maintainers review faster.
The C-Rank™ system evaluates GitHub projects on a 0–100 scale using real data: PR merge rates, review turnaround time, active maintainer presence, and first-time contributor success. A score of 58.6 places googleapis/mcp-toolbox in the A tier.
The external contributor pull request merge rate for googleapis/mcp-toolbox is 65.7%, based on public PR activity from non-core contributors.
googleapis/mcp-toolbox currently has 1 active issue(s) tagged with beginner-friendly labels like "good first issue", "beginner", or "up-for-grabs".
Rigorous architecture standards (83% critical review signals). Ensure PRs strictly follow guidelines before requesting review in googleapis/mcp-toolbox.
Average Response Latency
Tracks hours until a maintainer leaves a review, comment, or PR response.
External Acceptance Rate
Percentage of community pull requests successfully merged into main.
First PR Conversion
Rate at which developers submitting their first repository PR succeed.
Show contributors that your repository actively reviews and merges external pull requests.
[](https://getmerged.abhishekco.de/googleapis/mcp-toolbox?utm_source=github&utm_medium=badge)
Historical health & responsiveness evolution
External PR acceptance
First PR success rate
50% receive response in
90% receive response in
Maintainer review activity heatmap & prime window prediction
Calculating local time...
Calculating local time...
Detected: UTC
Maintainers are most responsive around 20:00 UTC (20:00 UTC in your timezone). Recommended submission window is Tuesday - Thursday from 20:00 to 00:00 UTC (20:00 - 00:00 UTC local).
Maintainer Strategy: Maintainer Sweet Spot: PRs under 150 lines merge in ~36 hours (82% approval). Large PRs (>500 lines) take ~265 hours (30% approval). Keep your diff compact for rapid review.
Prerequisites Search the current open issues Question Issue Description Environment Details Tool: MCP Toolbox Version: v1.2.0 Connector/Database: BigQuery Feature: Telemetry (Tracing) Problem Description After enabling the telemetry feature in mcp-toolbox (v1.2.0) while using the BigQuery tool, the system repeatedly issues span write requests to Google Cloud Trace (google.devtools.cloudtrace.v2.TraceService/BatchWriteSpans) approximately every 5 seconds. This high-frequency export interval introduces unnecessary network and processing overhead, and leads to unexpected Cloud Trace ingestion costs—especially in idle or low-traffic environments. Currently, is there granular control available to adjust the trace batch export interval or to disable specific trace exporters while keeping standard metrics/logging enabled. Code No response Additional Details No response
Prerequisites Search the current open issues What are you trying to do that currently feels hard or impossible? Navigating to the base URL of an integration, such as https://mcp-toolbox.dev/integrations/alloydb/, currently results in a dead end. Users clicking on the top-level integration name (e.g., AlloyDB PostgreSQL) expect to see an overview or the main configuration page, but instead hit a page with no content. Expected behavior The base path for any integration (e.g., /integrations/<integration_name>/) should automatically redirect users to its corresponding /source endpoint (e.g., /integrations/<integration_name>/source/). Suggested Solution(s) Implement an automatic redirect rule in the documentation site's routing configuration so that whenever a user navigates to an integration's root directory, they are seamlessly redirected to the source documentation page. For example: https://mcp-toolbox.dev/integrations/alloydb/ ➡️ https://mcp-toolbox.dev/integrations/alloydb/sour
Update gemini.md to add instruction for agent to check for security vulnerabilities.
Prerequisites Search the current open issues Closest matches found: #3543 (structural config validation) and #3634 (SQL-statement validation) cover validation timing; #2086 is about missing env vars in the Gemini CLI extension packaging. None address interpolation semantics for set-but-empty variables, which is a distinct gap. What are you trying to do that currently feels hard or impossible? Express "this optional field should only exist when its env var has a non-empty value" in tools.yaml — and more generally, get fail-fast behavior when a variable is set but empty. Current behavior in ConfigParser.parseEnv (cmd/internal/config.go): State of VAR ${VAR} ${VAR:default} unset ✅ startup error ("environment variable not found") uses default set to "" silently interpolates "" silently interpolates "" set to value interpolates value interpolates value The set-but-empty row is the trap, because in containerized deployments (Cloud Run, Kubernetes, Compose) a declared env
Rate what actually matters after opening a pull request here.
Rate your first-hand PR experience (review speed, maintainer responsiveness, and onboarding ease) to help other contributors.
When evaluating whether to contribute to googleapis/mcp-toolbox, response velocity and maintainer engagement are crucial. GetMerged continuously tracks pull request trajectories, first-comment latency, and code review rounds to help developers avoid submitting pull requests to backlogged repositories.
Currently, maintainers of googleapis/mcp-toolbox acknowledge new external contributions in approximately 2 days+. Out of all submitted pull requests from non-core authors in the last 180-day window, 65.7% were successfully merged into the primary branch.
googleapis/mcp-toolbox has a recorded first-timer success rate of 57.1%. Repositories ranked Welcoming typically provide actionable feedback during code reviews and actively nurture new community contributors.
The initial maintainer response time averages ~2 days+. Keeping PRs scoped to single concerns and ensuring CI checks succeed will optimize review turnaround.
The C-Rank™ index scores repositories on a 0 to 100 scale using an objective formula: external PR merge rates, initial response speed, active maintainer count, and first-time contributor retention. A score of 58.6 places googleapis/mcp-toolbox in the Welcoming tier.
The external pull request merge rate is 65.7%. GetMerged isolates non-core community contributions so external developers get an accurate benchmark of PR acceptance probability.
Yes, googleapis/mcp-toolbox currently has 1 active issue(s) tagged with beginner-friendly labels. You can inspect these directly from the repository issues tab.
All metrics displayed for googleapis/mcp-toolbox are automatically retrieved via the public GitHub API and recalculated daily. Insider pull requests submitted by repository owners or organization members are excluded from merge rate calculations to preserve objective external contributor statistics.