Skip to main content
Glama
Helm-Protocol

OpenTTT-MCP

by Helm-Protocol
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to OpenTTT-MCP

No user-submitted related servers found.

    Related Servers

    • @unfakable/mcp

      unfakable
      A
      license
      A
      quality
      D
      maintenance
      Document verification MCP server enabling AI agents to verify file authenticity by computing SHA-256 fingerprints locally and checking Bitcoin-anchored proofs via OpenTimestamps.
      5
      5 npm
      MIT

    • aip-identity

      The-Nexus-Guard
      A
      license
      A
      quality
      D
      maintenance
      MCP server for AI agent identity — verify agents with Ed25519 signatures, check trust scores, sign and verify content, exchange encrypted messages. Built on the Agent Identity Protocol (AIP).
      8
      MIT

    • agent-guardrail

      rudimentall1
      A
      license
      A
      quality
      A
      maintenance
      MCP server for AI agent guardrails — validates and signs agent decisions (OAA tokens) so third parties can verify them without server access
      3
      24 PyPI
      1
      MIT

    • OpenTimeStamps MCP Server

      getAlby
      A
      license
      B
      quality
      D
      maintenance
      A Model Context Protocol (MCP) server that enables AI models to timestamp files and verify proofs on the Bitcoin blockchain using OpenTimeStamps.
      7
      5 npm
      MIT

    • RIGForge

      mrodgersjs-web
      A
      license
      Not graded
      quality
      B
      maintenance
      MCP server enabling AI coding agents to seal work into cryptographically signed ProofPackets and verify them, catching forged completion claims and enforcing spec-bound acceptance criteria.
      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.6/5.0

    Scored across 5 tools

    Disambiguation5/5

    Each tool has a clearly distinct purpose: generate creates a new Proof of Time, health checks system status, query retrieves history, stats provides analytics, and verify validates existing proofs. There is no overlap or ambiguity between these functions.

    Naming Consistency5/5

    All tools follow a consistent 'pot_' prefix with descriptive action suffixes (generate, health, query, stats, verify), using snake_case uniformly. This pattern is predictable and enhances readability.

    Tool Count5/5

    With 5 tools, this server is well-scoped for managing Proof of Time operations. Each tool serves a specific, necessary function without redundancy, fitting a typical range for a focused domain.

    Completeness5/5

    The toolset provides complete coverage for the Proof of Time domain: creation (generate), verification (verify), monitoring (health), historical access (query), and analytics (stats). There are no obvious gaps, supporting full lifecycle management.

    Maintenance

    ActivityMaintained
    ResponsivenessUnresponsive

    Resources