Skip to main content
Glama
zovo-one

mcp-checklist

by zovo-one
OverviewSchemaSourceRelated ServersDiscussionsAdmin
JavaScript
Local

Related Servers

Alternatives to mcp-checklist

No user-submitted related servers found.

    Related Servers

    • mcp-purchase-requisition

      zovo-one
      A
      license
      A
      quality
      B
      maintenance
      Enables users to create reusable purchase requisition checklists, run them against individual orders, record step-by-step pass/fail/NA results with attributions, and sign off to freeze a dated, auditable approval record.
      16
      0
      MIT

    • loopgrid-mcp

      loopgridio
      A
      license
      A
      quality
      B
      maintenance
      Enables MCP-compatible hosts to record, retrieve, and verify LoopGrid decision evidence through tools for decisions, reviews, actions, outcomes, and verification.
      6
      18 PyPI
      Apache 2.0

    • onboarding

      zovo-one
      A
      license
      A
      quality
      B
      maintenance
      Enables HR and managers to create role-based task templates, turn them into dated checklists per new hire, track task owners and due dates, and sign off with a preserved record.
      9
      0
      MIT
    • OpenProof by twinforgelabs

      OpenProofofficial

      twinforgelabs
      A
      license
      Not graded
      quality
      B
      maintenance
      Enables agents to turn written acceptance requirements into explicit browser-check plans, inspect web apps for supported locators and assertions, and run deterministic checks that capture evidence reports. Each requirement is linked to observed pass/fail/unverified evidence, with write actions and target origins restricted unless explicitly allowed.
      MIT
    Deploy Server
    Pay for results, not tokens.Fund a bounty. Let AI agents compete and collaborate to solve your problems.agentbounties.appAd

    TDQS

    A4.2/5.0

    Scored across 16 tools

    Disambiguation4/5

    Checklist management tools (create, item_add/remove/show/list/delete) and run tools (start/check/show/list/sign_off/status/report/delete) are clearly separated by prefix. Minor potential confusion between run_show and run_report, but their descriptions clarify different purposes (run_show is a detailed view, run_report a printable export).

    Naming Consistency5/5

    All tools follow a clear verb_form pattern: license_status/activate, checklist_create/item_add/remove/show/list/delete, run_start/check/show/list/sign_off/status/report/delete. Naming is consistent, predictable, and uses actions that align with the resource lifecycle.

    Tool Count5/5

    16 tools is well-scoped for a checklist management server covering both template lifecycle and run lifecycle. Each tool has a distinct role, with no redundancy; the count is appropriate for the domain complexity.

    Completeness5/5

    The server provides complete coverage: create, read, update (via item_add/remove), delete for checklists; start, check, show, list, sign-off, status change, report, delete for runs. Edge cases like abandoning runs and handling signed-off runs are addressed, leaving no obvious gaps in the workflow.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources