Skip to main content
Glama
Louis75011

mcp-relances-postgres

by Louis75011
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to mcp-relances-postgres

No user-submitted related servers found.

    Related Servers

    • Miinta Pipedrive MCP

      alvarolloret
      A
      license
      A
      quality
      C
      maintenance
      Read-only MCP server for Pipedrive that provides a digest-ready sales queue with overdue follow-ups, due today activities, and deals missing next action.
      4
      28 npm
      MIT

    • django-mcp-sql

      thepapermen
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides a read-only PostgreSQL SQL surface for LLM agents via MCP, with defense-in-depth security layers for safe database queries.
      369 PyPI
      4
      MIT

    • Uniware Vtiger MCP Server

      Srimathi-8502
      F
      license
      Not graded
      quality
      B
      maintenance
      Read-only MCP server connecting Claude to Vtiger CRM for leads, deals, and overdue follow-ups.
      -
    • MCP DB Gateway by altsys

      MCP DB Gatewayofficial

      altsys
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides governed, read-only PostgreSQL access for AI agents via MCP. Enforces schema/table allowlists, query limits, and audit events.
      1
      MIT

    • mcp-sql-metrics

      JuanPinilla198
      A
      license
      Not graded
      quality
      C
      maintenance
      Exposes read-only PostgreSQL queries as typed MCP tools, enabling natural-language data analysis while keeping raw tables hidden and enforcing safety limits.
      MIT
    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.6/5.0

    Scored across 2 tools

    Disambiguation5/5

    The two tools have clearly distinct outputs: relances_dues returns a detailed ordered list of overdue reminders, while resume_relances returns aggregated counts by channel. An agent can easily choose the right one based on whether it needs rows or summary counts.

    Naming Consistency4/5

    Both names are French snake_case and readable, but they follow slightly different patterns: relances_dues is a noun phrase while resume_relances is verb+noun. This is a minor inconsistency rather than a confusing mix of conventions.

    Tool Count3/5

    Two tools is thin for a server surface, even a narrowly read-only one. The tools are well scoped, but the overall offering feels minimal and borderline underpowered.

    Completeness3/5

    The surface covers listing overdue reminders and summarizing counts by channel, which fits a read-only reporting purpose. However, there are notable gaps: no retrieval by client/reminder id, no filtering options, and no history or period-based reporting beyond a single date.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources