Skip to main content
Glama
yunosuke-github

secure-mcp-database-crud

by yunosuke-github
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Hybrid

Related Servers

Alternatives to secure-mcp-database-crud

No user-submitted related servers found.

    Related Servers

    • mcp-task-server

      antropovanikolitf
      A
      license
      Not graded
      quality
      C
      maintenance
      A security-focused Model Context Protocol server for task management over stdio, backed by SQLite. It exposes tools to create, list, complete, delete, and search tasks with strict validation, parameterized SQL, confirmation for deletes, and full audit logging.
      5 npm
      MIT

    • MCP Local Database Server

      manojprabhuoffl-ghub
      F
      license
      Not graded
      quality
      D
      maintenance
      Enables task management through a local MySQL database, supporting full CRUD operations and automated tracking of status transitions. Users can create, search, and update tasks while maintaining a detailed progress history for all activities.
      -

    • Tareas MCP Server

      Luis9007
      F
      license
      Not graded
      quality
      C
      maintenance
      Enables task management through MCP, including creation, retrieval, update, deletion, and filtering tasks by completion status using a MySQL-backed server.
      -

    • To Do List MCP

      Wesley-Blake
      F
      license
      D
      quality
      C
      maintenance
      Enables users to manage a personal to-do list backed by SQLite, adding single or multiple tasks, listing incomplete tasks, renaming or updating task status, and marking tasks complete. All state persists in a local database created automatically on first run.
      4
      -
    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

    A3.9/5.0

    Scored across 6 tools

    Disambiguation5/5

    Each tool targets a distinct operation: create, get, list, update, and a two-step delete with prepare and confirm. There is no functional overlap.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern (e.g., create_task, update_task, prepare_delete_task). The naming is clear and predictable.

    Tool Count5/5

    With 6 tools, the server is well-scoped for task CRUD operations. The count is neither excessive nor insufficient for the domain.

    Completeness5/5

    The tool set covers full CRUD functionality plus a secure two-step delete. No obvious missing operations for the stated purpose of secure task management.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources