Skip to main content
Glama
clevertech-os

VeriLock MCP

by clevertech-os
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Hybrid

Related Servers

Alternatives to VeriLock MCP

No user-submitted related servers found.

    Related Servers

    • @integraledger/lcp-mcp-server by IntegraLedger

      @integraledger/lcp-mcp-serverofficial

      IntegraLedger
      A
      license
      Not graded
      quality
      C
      maintenance
      Read-only Model Context Protocol server exposing LCP tools to an AI agent — verify before pay, compute an atrHash, extract and place references across ten commerce protocols.
      Apache 2.0

    • memory-bank-mcp

      axrbarsic
      A
      license
      B
      quality
      B
      maintenance
      Provides a read-only MCP interface to query and retrieve verifiable evidence from a local memory bank, supporting search, dossier, chronology, source, and evidence tools.
      6
      BSD Zero Clause

    • proofrelay

      GENESISRE
      A
      license
      A
      quality
      F
      maintenance
      Read-only ProofRelay MCP verifier for non-confidential evidence bundles. Exposes 22 public-safe tools, 11 resources, and 11 prompts for bundle integrity checks, receipt-chain review, checkpoint recommendations, MCP risk metadata review, and real-estate closing proof-pack readiness.
      5
      MIT

    • property-inventory

      Anneo22
      A
      license
      Not graded
      quality
      A
      maintenance
      Provides a local-first, evidence-backed ledger for physical property, enabling agents to search inventory, prepare capture reviews, and inspect proposals through MCP. Enforces strict boundaries: scoped reads by default, with private write access limited to preparing, not applying, mutations.
      MIT

    • SQL MCP Server Demo

      kamaleshayyala-0608
      F
      license
      Not graded
      quality
      C
      maintenance
      Provides read-only access to SQL Server databases via Data API Builder, with tools to describe entities, read records, and aggregate data through the Model Context Protocol.
      -
    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.8/5.0

    Scored across 8 tools

    Disambiguation4/5

    Most tools have clearly distinct purposes—list, get, verify, and the various evidence artifact retrievals are well separated. There is minor overlap between get_document's signing information and get_signing_status's signing summary, which could cause occasional misselection.

    Naming Consistency5/5

    All tool names follow a consistent snake_case verb_noun pattern: list_documents, get_document, verify_document_hash, get_audit_events, and so on. The pattern is predictable and makes the group easy to navigate.

    Tool Count5/5

    Eight tools is well within the ideal range for a document verification/evidence server. Each tool covers a distinct operation needed for verification workflows without being bloated or thin.

    Completeness4/5

    The server covers the core read-side workflow: listing, retrieving, hash verification, audit events, evidence manifests, certificates, chain attestation, and signing status. A minor gap is the absence of a direct signature or document-binary verification behavior, though the hash-only approach may be intentional.

    Maintenance

    ActivityMaintained
    ResponsivenessNo issues

    Resources