Skip to main content
Glama
jordanburke

DuckPond MCP Server

by jordanburke
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to DuckPond MCP Server

No user-submitted related servers found.

    Related Servers

    • CentralMind/Gateway

      centralmind
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP-Server from your Database optimized for LLMs and AI-Agents. Supports PostgreSQL, MySQL, ClickHouse, Snowflake, MSSQL, BigQuery, Oracle Database, SQLite, ElasticSearch, DuckDB
      550
      Apache 2.0

    • Multi Database MCP Server

      FreePeak
      A
      license
      Not graded
      quality
      A
      maintenance
      The Multi DB MCP Server is a high-performance implementation of the Database Model Context Protocol designed to revolutionize how AI agents interact with databases. Currently supporting MySQL and PostgreSQL databases.
      431
      MIT

    • ilma

      Brotal-LLC
      A
      license
      Not graded
      quality
      C
      maintenance
      Framework-agnostic MCP server for agent memory with Postgres + pgvector, enabling persistent memory, recall, and task management across sessions.
      MIT

    • Legion Database MCP Server

      fastmcp-me
      A
      license
      Not graded
      quality
      D
      maintenance
      A unified MCP server for querying and managing multiple database types (PostgreSQL, MySQL, SQL Server, etc.) via natural language through AI assistants.
      GPL 3.0

    • mnemos

      ncz-os
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server providing persistent memory, semantic search, versioned storage, webhook fanout, and unified LLM routing for AI agents via FastAPI runtime with multiple backend options.
      34
      Apache 2.0
    Deploy Server
    One endpoint for every MCP toolRayrun runs every MCP server behind one URL and holds the credentials. Each call is decided per client, tool, and argument, then recorded.ray.runAd

    TDQS

    B3.4/5.0

    Scored across 6 tools

    Disambiguation4/5

    query and execute both run SQL but are clearly differentiated by whether results are returned, while the remaining tools have distinct management purposes. isAttached, getUserStats, and listUsers target different aspects of user database state. Only query/execute could potentially be confused, but the descriptions resolve the boundary.

    Naming Consistency2/5

    Tool names mix lowercase single-word verbs like query and execute with camelCase compound names like getUserStats and detachUser. isAttached also follows a different predicate-style pattern rather than verb_noun. The naming style is inconsistent across the set.

    Tool Count5/5

    Six tools is a well-scoped size for this server's purpose. Each tool covers a distinct need: SQL execution, user statistics, cache status, cache eviction, and user listing. No tool feels redundant or extraneous.

    Completeness4/5

    The tool surface covers the core workflow of querying and executing SQL, inspecting user state, and managing cached database attachment. A manual attach tool is missing, but automatic attachment on first use likely makes it unnecessary. Overall the domain is well covered with only minor optional gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessSyncing

    Resources