Skip to main content
Glama
0xddneto

AI Proof of Us MCP Server

by 0xddneto
OverviewSchemaSourceRelated ServersDiscussionsAdmin
TypeScript
Remote

Related Servers

Alternatives to AI Proof of Us MCP Server

No user-submitted related servers found.

    Related Servers

    • @sequesign/mcp

      Sequesign
      A
      license
      A
      quality
      B
      maintenance
      Enables AI agents to create cryptographically verifiable receipts of their delegated work, with capabilities for multi-party approval and offline verification.
      11
      47 npm
      Apache 2.0

    • LedgerProof LAIN

      vsdawkins-creator
      F
      license
      Not graded
      quality
      C
      maintenance
      Cryptographically anchored, tamper-evident evidence receipts for AI agents — verified run receipts, existence-at-time proofs, and cited answers from an anchored public record. Remote MCP with proof-gated settlement; attests existence and integrity, never truth.
      -

    • Finch MCP

      finchagentic
      A
      license
      A
      quality
      B
      maintenance
      Enables AI assistants to retain persistent, searchable memory and versioned vaults, spawn and recall named agents with state and audit history, run automations, monitors, and deep research, and execute on-chain and web tasks across sessions. It can be installed alongside Claude Code, Cursor, Windsurf, Zed, Hermes, and other MCP clients, with vault and memory optionally run entirely on the user's machine.
      45
      131 npm
      MIT

    • AgentLens

      agentkitai
      A
      license
      A
      quality
      C
      maintenance
      AI-agent observability server whose distinguishing feature is a SHA-256 hash-chained, tamper-evident audit log with chain verification and signed export. Works with Claude Desktop, Cursor, and any MCP client.
      22
      2 npm
      23
      MIT

    • mcp-context-receipts

      DARREN-2000
      A
      license
      B
      quality
      B
      maintenance
      Privacy-first, tamper-evident receipts for MCP tool calls. It hashes and signs arguments/results so you can verify what ran, when, without storing raw payloads.
      2
      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

    A4.6/5.0

    Scored across 11 tools

    Disambiguation5/5

    Each tool has a distinct, clearly defined role: task lifecycle (begin, complete, estimate), settlement (settle one batch vs all), linking (Paybox vs Technocore), and read/utility (status, contract, identity, export). No two tools could be easily confused; even the two settlement tools are explicitly differentiated by scope and usage conditions.

    Naming Consistency5/5

    All tool names follow a consistent verb_noun pattern with clear, domain-specific verbs (begin, complete, estimate, export, create, settle, get) and nouns (ai_task, ai_reward, paybox_work_link, aipou_status). The only slight variation is 'settle_all_ai_rewards' vs 'settle_ai_rewards', which is logical and still follows the pattern.

    Tool Count5/5

    With 11 tools, the set is well-scoped and neither sparse nor bloated. Each tool covers a meaningful operation in the AI task farming and settlement workflow, from task initiation to reward claiming, without redundancy.

    Completeness5/5

    The domain of AI proof-of-work reward management is fully covered: task creation, completion, estimation, settlement (both single-batch and all), receipt export, external linking, and read-only status/contract/identity queries. There are no obvious missing operations; the lifecycle is closed from start to finish.

    Maintenance

    ActivityActive
    ResponsivenessWithin a week

    Resources