Skip to main content
Glama
Sign In
kychee-com

run402-mcp

by kychee-com
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Local

Related Servers

Alternatives to run402-mcp

No user-submitted related servers found.

    Related Servers

    • postgres-mcp

      dkbearsong
      F
      license
      Not graded
      quality
      D
      maintenance
      A secure PostgreSQL MCP server allowing AI models to read, write, update, and delete database records with parameterized queries, transactional dry-runs, disposable testing, and automated backups.
      -

    • postgres2mcp

      Railcode-HQ
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables connecting Postgres databases to MCP clients with built-in query and inspection tools, custom parametrized SQL tools, scoped API keys, group permissions, and audit logging.
      6
      MIT

    • postgres-mcp-server

      abdulsammad-lgtm
      A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants to securely interact with PostgreSQL databases through a standardized MCP interface, supporting SQL queries, schema inspection, and database management.
      MIT

    • pg-mcp

      sr9000
      A
      license
      Not graded
      quality
      C
      maintenance
      Enables MCP clients to inspect and query PostgreSQL databases through per-endpoint bearer-token authentication, SQL guarding, and comprehensive audit logging, while a web UI manages connections, endpoints, roles, and audit records.
      MIT

    • PgGuard Agent

      vk-ai
      A
      license
      A
      quality
      A
      maintenance
      Enables governed access to corporate Postgres databases via MCP, supporting read-only queries, confirmed data and schema changes, query explanation, audit trail retrieval, and role-based policies with optional Vault secret integration.
      10
      MIT
    Deploy Server
    Shareable, User-Owned Context BackendPeople, applications, and agents read, write, and coordinate together in one context lake. Reach it over MCP, a CLI, a Python SDK, or REST.fulcradynamics.comAd

    TDQS

    A3.7/5.0

    Scored across 8 tools

    Disambiguation3/5

    Deploy and up both perform deployments, differing only in whether setup is auto-completed, so an agent must read carefully to pick between them. Status, whoami, and doctor are also three overlapping read-only state views (local wallet vs remote principal vs diagnostics), and all of them plus most other operations are reachable through run, creating multiple routes to the same result. Descriptions do draw the lines explicitly, which keeps it from being worse.

    Naming Consistency2/5

    Names mix bare verbs (deploy, run), bare nouns (status, whoami, doctor, docs), an adverb-ish workflow name (up), and one snake_case compound (expand_result). Individual names are readable, but there is no predictable convention an agent could extrapolate from.

    Tool Count4/5

    Eight tools is a healthy scope for a deployment platform and nothing feels padded. The only quibble is that status, whoami, and doctor are thin convenience wrappers that run/docs already cover, so a couple of slots are low-value rather than bloated.

    Completeness4/5

    Core lifecycle is covered: plan/setup (up), apply (deploy), inspect (status/whoami/doctor), reference (docs), and an arbitrary SDK escape hatch (run) plus pagination (expand_result). Rollback, release listing, and secret management are not first-class tools, but the run snippet surface plus CLI pointers make them reachable, so gaps are workable rather than blocking.

    Maintenance

    ActivityActive
    ResponsivenessResponsive

    Resources