Skip to main content
Glama
JoodasCode

SlopWatch MCP Server

by JoodasCode
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript

Related Servers

Alternatives to SlopWatch MCP Server

No user-submitted related servers found.

    Related Servers

    • Warranted

      yqi96
      A
      license
      Not graded
      quality
      A
      maintenance
      Makes AI research agents accountable by giving every conclusion a traceable argument graph. Provides a persistent argument graph where claims require grounds and warrants for auditable, verifiable reasoning.
      2
      MIT

    • casuallayer-mcp

      smq9sn5jck-coder
      A
      license
      Not graded
      quality
      C
      maintenance
      Deterministic AI liability attribution engine. Scores fault across AI supply-chain participants (deployer, developer, vendor) with tamper-evident certificates and weekly cryptographic anchoring.’
      56 npm
      2
      Apache 2.0

    • Rework

      Santhosh-Stalin
      A
      license
      Not graded
      quality
      A
      maintenance
      Enables AI agents to replace self-reported done checkboxes with verified, evidence-based completion tracking, using automated FAIL_TO_PASS/PASS_TO_PASS tests, mandatory mutation checking, and explicit human/AI reviews when automated proof is impossible.
      1
      MIT

    • sigmodx-mcp

      Sigmodx
      A
      license
      A
      quality
      D
      maintenance
      Audit infrastructure for AI agents to log consequential decisions (invoice, GL, anomaly) and verify attestations via MCP tools.
      6
      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

    B3.3/5.0

    Scored across 3 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose with no overlap: one handles claim registration and verification, another generates configuration files, and the third retrieves status metrics. The descriptions make it easy to differentiate their functions, eliminating any risk of misselection.

    Naming Consistency5/5

    All tool names follow a consistent 'slopwatch_verb_noun' pattern (e.g., slopwatch_claim_and_verify, slopwatch_setup_rules, slopwatch_status). This uniformity makes the set predictable and easy to navigate, with no deviations in style or structure.

    Tool Count4/5

    With 3 tools, the count is slightly low but reasonable for a server focused on AI accountability and slop scoring. Each tool serves a distinct, essential function, though the scope might feel thin if more operations are expected in this domain.

    Completeness4/5

    The tools cover core workflows: setup (rules generation), claim handling (registration and verification), and monitoring (status retrieval). Minor gaps might exist, such as tools for updating rules or detailed analytics, but the surface supports basic operations without dead ends.

    Maintenance

    ActivityInactive
    ResponsivenessNo issues

    Resources