{"id":"lijianlong123-dbc-mcp-server","name":"dbc-mcp-server","homepage":null,"repo_url":"https://github.com/lijianlong123/dbc-mcp-server","category":"ai-ml","subcategories":[],"tags":["mcp","spring-boot","database","metadata","schema-introspection","ai-tools","jdbc","postgresql","mysql","sqlite","sql-server"],"what_it_does":"DBC-MCP-Server is a Spring Boot service that exposes a Model Context Protocol (MCP) interface for database connection management and AI-assisted database metadata querying. It supports multiple SQL databases (e.g., MySQL, PostgreSQL, SQL Server, SQLite) via dynamic datasource switching and provides MCP “tool functions” for schema/introspection (tables, columns, foreign keys, indexes, engine) plus SQL execution and row count/statistics.","use_cases":["AI agents that need to understand database schema (tables/columns/foreign keys/indexes)","Natural-language to SQL workflows where an agent fetches metadata then runs queries","Cross-database introspection across multiple configured datasources","Database-driven code generation workflows (e.g., generate queries or mappings from schema)","Operational exploration of table sizes (row counts) and storage engine details"],"not_for":["Production environments requiring strong governance/least-privilege controls without additional hardening","Use cases that require a public, unauthenticated endpoint (not indicated as such in the README)","Workloads that must guarantee safety from arbitrary SQL execution (since an executeSql tool is described)"],"best_when":"You have a controlled environment where an AI agent can connect to known database instances and you want structured schema tooling through MCP for iterative query building.","avoid_when":"You cannot restrict/validate tool inputs (especially for executeSql) or you need strong compliance controls not addressed by the provided documentation.","alternatives":["OpenAPI/REST-based database schema discovery services","LangChain/Spring AI tools that directly introspect database schemas without an intermediate MCP server","Using database-native introspection plus an LLM-side SQL planner/executor with strict parameterization","Dedicated data catalog solutions (e.g., schema registry/catalog) integrated with LLM tool calling"],"af_score":40.8,"security_score":25.8,"reliability_score":16.2,"package_type":"mcp_server","discovery_source":["github"],"priority":"low","status":"evaluated","version_evaluated":null,"last_evaluated":"2026-04-04T19:41:28.832773+00:00","interface":{"has_rest_api":false,"has_graphql":false,"has_grpc":false,"has_mcp_server":true,"mcp_server_url":"http://localhost:8081/sse","has_sdk":false,"sdk_languages":[],"openapi_spec_url":null,"webhooks":false},"auth":{"methods":["Not specified in README"],"oauth":false,"scopes":false,"notes":"The README shows only database connection credentials in application.properties and an MCP SSE URL configuration. It does not document any MCP/API authentication mechanism, authorization, or tool-level permissions."},"pricing":{"model":null,"free_tier_exists":false,"free_tier_limits":null,"paid_tiers":[],"requires_credit_card":false,"estimated_workload_costs":null,"notes":"No pricing information present (typical for self-hosted open source)."},"requirements":{"requires_signup":false,"requires_credit_card":false,"domain_verification":false,"data_residency":[],"compliance":[],"min_contract":null},"agent_readiness":{"af_score":40.8,"security_score":25.8,"reliability_score":16.2,"mcp_server_quality":62.0,"documentation_accuracy":55.0,"error_message_quality":0.0,"error_message_notes":null,"auth_complexity":35.0,"rate_limit_clarity":10.0,"tls_enforcement":20.0,"auth_strength":20.0,"scope_granularity":10.0,"dependency_hygiene":45.0,"secret_handling":40.0,"security_notes":"Security posture is unclear from the provided README. It includes database credentials in application.properties but does not describe secret management practices (env vars/vault), transport security (TLS) for the MCP SSE endpoint, or authentication/authorization for MCP tools. The presence of an executeSql tool increases risk of SQL injection or unintended data access/modification unless the server enforces strict allowlists/parameterization and least-privilege DB accounts. Dependency versions are listed but no vulnerability/CVE hygiene or security hardening guidance is provided.","uptime_documented":0.0,"version_stability":45.0,"breaking_changes_history":0.0,"error_recovery":20.0,"idempotency_support":"false","idempotency_notes":"No idempotency guarantees are documented for tools; executeSql can be non-idempotent depending on the SQL provided.","pagination_style":"none","retry_guidance_documented":false,"known_agent_gotchas":["executeSql is powerful; agents may attempt data-modifying statements—ensure the tool is constrained/validated in your environment.","No documented rate limits; agents may need to self-throttle to avoid exhausting DB connections/limits.","No documented auth/authorization; if deployed beyond localhost, add network controls/auth at the MCP layer.","Schema tools may require correct datasource selection; ensure the agent knows which datasource nick/name to use (e.g., jys/studyinfo/springai)."]}}