Skip to main content
Glama

Related Servers

Alternatives to CSV Contract Preflight MCP

No user-submitted related servers found.

    Related Servers

    • A
      license
      B
      quality
      B
      maintenance
      Contributors: dengyier & Tim Shing(成孝添) Check what an AI agent was authorized to do and what its signed evidence supports. Includes reference SOC alert review and a separately enabled Codex preview-directory Guard; installing MCP does not activate Guard.
      32
      97 PyPI
      261
      Apache 2.0
    • A
      license
      Not graded
      quality
      D
      maintenance
      MCP server providing 17 keyless, pay-per-use web-data tools with signed-provenance receipts, enabling AI agents to autonomously fetch, extract, and verify web content on Base mainnet.
      MIT
    • A
      license
      Not graded
      quality
      D
      maintenance
      Enables AI assistants such as Claude and Cursor to discover and verify agents, negotiate offers, execute conditional settlements, and verify receipts and complete multi-agent workflows through eight MCP tools.
      29 PyPI
      1
      MIT
    • A
      license
      Not graded
      quality
      C
      maintenance
      A sovereign, MIT-licensed MCP server for professional-service workflows, providing offline-capable, Ed25519-signed tools for autonomous agents and human developers.
      MIT

    TDQS

    B3.4/5.0

    Scored across 11 tools

    Disambiguation4/5

    The draft lifecycle (prepare/review/get/accept/export) and template list/get pairs are cleanly separated, and the descriptions clearly delimit paid vs free operations. Two near-duplicate pairs create mild ambiguity: start_validation vs start_validation_from_draft, and get_validation vs get_validation_summary, where an agent must read carefully to pick the right read path.

    Naming Consistency5/5

    All tools use snake_case verb_noun form with a small, stable verb set (start, get, prepare, review, accept, export, list). Multi-word objects like contract_draft and validation are applied consistently across the lifecycle.

    Tool Count4/5

    Eleven tools is well within a reasonable range for a two-phase workflow (draft creation then paid validation). There is some redundancy in maintaining parallel start_validation/start_validation_from_draft and get_validation/get_validation_summary paths, but each earns a distinct role.

    Completeness3/5

    CRUD-ish coverage exists for drafts (prepare, review, get, accept, export) and validation (start, get, summary, start-from-draft), but there is no way to list existing drafts or validations, so an agent must already know IDs. There is also no cancel/abort or delete operation for drafts or runs, leaving cleanup and discovery as dead ends.

    Maintenance

    ActivityMaintained
    ResponsivenessNo recent community issues