Skip to main content
Glama
mcp-server-starter-sample

mcp-server-starter-sample

by DingXinPro

Related Servers

Alternatives to mcp-server-starter-sample

No user-submitted related servers found.

    Related Servers

    • F
      license
      Not graded
      quality
      B
      maintenance
      Enables read-only discovery and retrieval of allowlisted catalog datasets with host-assigned roles, strict tool validation, SQLite read-only enforcement, and audit hash chaining. It supports querying bounded daily aggregates while preventing arbitrary SQL, file access, shell commands, credential use, or role escalation.
      -
    • A
      license
      B
      quality
      B
      maintenance
      Enables AI assistants and MCP clients to safely inspect allow-listed SQLite databases by listing tables, describing schemas, running capped read-only queries, sampling rows, and exporting CSV, with writes blocked unless explicitly enabled.
      7
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI agents and other MCP clients to run read-only, policy-checked SQL queries against SQLite databases, with table and column allowlists, PII restrictions, audit logging, and time and row budgets.
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      Enables exploring and querying a SQLite database loaded into memory through validated read-only SELECT/WITH statements, with enforced limits on database size, rows, result bytes, cells, and parameters.
      MIT
    • A
      license
      A
      quality
      B
      maintenance
      Enables secure, read-only PostgreSQL queries, sandboxed file reads within a confined directory tree, and host CPU, memory, and disk metrics over stdio. It exposes these capabilities through narrowly scoped tools with strict validation and fail-closed guardrails.
      1
      MIT

    TDQS

    B3.4/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct purposes: running a SQLite SELECT versus fetching an allowlisted URL. There is no realistic overlap or misselection risk between them.

    Naming Consistency3/5

    Both names use snake_case, but the patterns differ: sqlite_query is resource_action while fetch_url is verb_noun. The names remain readable, but there is no consistent verb-first convention.

    Tool Count3/5

    Two tools is thin even for a starter sample server. The scope is understandable, but the surface feels more like a minimal demo than a well-rounded tool set.

    Completeness3/5

    The SQLite tool is read-only and the URL tool only fetches, so write and broader lifecycle operations are absent. For a starter sample this may be intentional, but agents needing mutation or schema inspection would hit gaps.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues