Skip to main content
Glama
kishanraj41

Polygraph MCP Server

by kishanraj41
OverviewSchemaSourceRelated ServersDiscussionsAdmin
Python
Local

Related Servers

Alternatives to Polygraph MCP Server

No user-submitted related servers found.

    Related Servers

    • SQAI by thyn-ai

      SQAIofficial

      thyn-ai
      A
      license
      A
      quality
      B
      maintenance
      Official SQAI MCP server: governed structured data access powered by Mojo kernels. 3 stdio tools: listSources (discovery), queryData (deterministic read-only queries + compute with provenance), explainQuery (dry-run validation). Introspection needs no credentials; execution requires a one-time free sqai login. npm: @thyn-ai/sqai-mcp. Source: packages/mcp. Registry: io.github.thyn-ai/sqai.
      4
      Apache 2.0

    • io.github.fabienfrfr/pbix

      fabienfrfr
      A
      license
      Not graded
      quality
      B
      maintenance
      Provides full lineage graph analysis for Power BI .pbix files, enabling source-to-visual-field traversal. Exposes REST and MCP endpoints for building, searching, and exporting lineage graphs.
      50 PyPI
      MIT

    • 事件知識圖譜 MCP Server

      ianchu32123
      A
      license
      Not graded
      quality
      D
      maintenance
      Provides an incident-centric knowledge graph via MCP stdio, enabling storage and query of incidents, systems, signatures, and their causal relationships, with tools for creating, linking, and tracing incidents.
      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.7/5.0

    Scored across 6 tools

    Disambiguation4/5

    Most tools are clearly distinct: list_undeclared_sources and list_phantom_edges target different finding types, and get_incident_report and explain_verdict_semantics are self-contained. However, can_i_trust and get_integrity_score both address lineage trust at different granularities (asset verdict vs job score), which could cause an agent to misselect without careful reading.

    Naming Consistency4/5

    Five of six tools follow a consistent snake_case verb_noun pattern (get_integrity_score, list_*, get_incident_report, explain_verdict_semantics). can_i_trust is also snake_case but is a question phrase rather than verb_noun, a minor deviation.

    Tool Count5/5

    Six tools are well-scoped for a specialized lineage integrity server: they cover the core questions without redundancy. No unnecessary bloat or missing essential operation.

    Completeness4/5

    The surface covers the main analysis workflow: trust verdict, integrity score with components, undeclared sources, phantom edges, incident reports, and verdict semantics. Minor gaps remain (e.g., retrieving raw declared/observed edges for manual comparison), but agents can work around them via existing tools.

    Maintenance

    ActivityStale
    ResponsivenessNo issues

    Resources