Skip to main content
Glama
AMohammadzadeh

PeerDB MCP

by AMohammadzadeh
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Remote

Related Servers

Alternatives to PeerDB MCP

No user-submitted related servers found.

    Related Servers

    • vybeflow-mcp

      never00miss
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables AI assistants to securely connect to a vybeflow tenant for multi-channel messaging operations such as reading inbox tickets, looking up contacts, checking campaign progress, and sending messages under scoped permissions.
      MIT

    • Safe DB Gateway

      Chantichalla
      A
      license
      A
      quality
      A
      maintenance
      Enables AI agents to query PostgreSQL databases securely with read-only defaults, PII masking, rate limiting, and human-approved, expiring mutation tokens.
      9
      1
      Apache 2.0

    • pgwarden

      B0yko
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI assistants to query Postgres as the signed-in person through OAuth 2.1/OIDC, with database-enforced read-only queries, PII masking, human-approved writes, and a tamper-evident audit log.
      Apache 2.0

    • QuestLLens

      DMDuFresne
      A
      license
      Not graded
      quality
      B
      maintenance
      Gives AI agents read-only access to any QuestDB instance, enabling schema discovery, time-series querying, and monitoring of partitions, WAL state, symbols, and ingestion health through MCP.
      Apache 2.0

    • @flowmaster-io/mcp

      flow-master-io
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables AI assistants to connect to a Flow Master workspace and perform project, task, ticket, board, relationship, tag, and comment operations under the user's own account and permissions.
      4 npm
      ISC
    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.7/5.0

    Scored across 13 tools

    Disambiguation5/5

    Each tool targets a distinct action or resource: lifecycle (create/pause/resume/update), listing (pipelines/peers), status/diagnostics (status/errors/batches/slots/diagnose/validate), and version. Overlap is minimal; diagnose_pipeline is composite but clearly distinct from raw status by including heuristic troubleshooting.

    Naming Consistency5/5

    All 13 tools use snake_case with a verb_noun pattern (e.g., get_peerdb_version, list_pipelines, create_pipeline). The convention is consistent throughout, with no deviations in style or case.

    Tool Count5/5

    13 tools is well-scoped for a pipeline management server, covering connectivity, inventory, lifecycle, diagnostics, and validation. No tool appears redundant or superfluous.

    Completeness3/5

    Core pipeline lifecycle is covered (create, read, update, pause/resume), but there is no delete_pipeline operation to remove a pipeline. Peer management is read-only (list_peers), and QRep pipelines lack dedicated diagnostic tools (get_pipeline_batches explicitly excludes QRep). These gaps may force agents to work around missing operations.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources